# Changes to PkgServers storage backend

**URL:** <https://discourse.julialang.org/t/changes-to-pkgservers-storage-backend/112378>\
**Category:** Community\
**Created:** [April 1, 2024, 4:02pm UTC](https://discourse.julialang.org/t/changes-to-pkgservers-storage-backend/112378 "2024-04-01T16:02:03Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [May 29, 2024, 11:30am UTC](https://discourse.julialang.org/t/changes-to-pkgservers-storage-backend/112378/21 "2024-05-29T11:30:49Z")

</div>

Agree. Asking to open up all of GitHub is too much.

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [May 29, 2024, 11:49pm UTC](https://discourse.julialang.org/t/changes-to-pkgservers-storage-backend/112378/22 "2024-05-29T23:49:56Z")

</div>

> [@dilumaluthge](#):
>
> Okay, so as far as I can tell, when you first install Juliaup, it downloads the Juliaup binaries from a URL of the form `https://github.com/JuliaLang/juliaup/releases/latest/download/*`.

That is not correct. Juliaup downloads everything from either [https://julialang-s3.julialang.org](https://julialang-s3.julialang.org) or [https://julialangnightlies-s3.julialang.org](https://julialangnightlies-s3.julialang.org) (if one installs the `nightly` channel). The only other domain involved for Juliaup is [https://install.julialang.org](https://install.julialang.org) for initial user-initiated installs of Juliaup itself.

---

<div class="post-metadata">

**Author:** ![dilumaluthge](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dilumaluthge/32/29283_2.png) [@dilumaluthge](https://discourse.julialang.org/u/dilumaluthge)\
**Post date:** [May 29, 2024, 11:51pm UTC](https://discourse.julialang.org/t/changes-to-pkgservers-storage-backend/112378/23 "2024-05-29T23:51:07Z")

</div>

Hmmm. Then what’s happening on [this line (line 84)](https://github.com/JuliaLang/juliaup/blob/13fa656f43c2feb9d85882def899eeda968537b9/deploy/shellscript/juliaup-init.cmd#L84)?

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [May 29, 2024, 11:52pm UTC](https://discourse.julialang.org/t/changes-to-pkgservers-storage-backend/112378/24 "2024-05-29T23:52:20Z")

</div>

> [@jling](#):
>
> if one is using JuliaUp, at least it tried to grab something from Github the other day when launched for the first time.

Do you have more details? How did that manifest itself? Juliaup should definitely _not_ do any such thing, and I can’t think of anything that would trigger that 🙂

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [May 29, 2024, 11:55pm UTC](https://discourse.julialang.org/t/changes-to-pkgservers-storage-backend/112378/25 "2024-05-29T23:55:30Z")

</div>

> [@dilumaluthge](#):
>
> Then what’s happening on [this line (line 84)](https://github.com/JuliaLang/juliaup/blob/13fa656f43c2feb9d85882def899eeda968537b9/deploy/shellscript/juliaup-init.cmd#L84)?

That code is never used anywhere. I copied the shell scripts that do the initial setup from rustup, and they had one for Mac/Linux and one for Windows. The file you refer to is the Windows one. But we don’t support that kind of setup on Windows with Juliaup. I’m just keeping the file around, in case we change our mind down the road so that we have a starting point, we could also just delete the file for now.

The relevant (equivalent) location for the (used) Linux/Mac shell script is [juliaup/deploy/shellscript/juliaup-init.sh at ce87fbdb02ee15ef14713a10e7e5aed8cca023ca · JuliaLang/juliaup · GitHub](https://github.com/JuliaLang/juliaup/blob/ce87fbdb02ee15ef14713a10e7e5aed8cca023ca/deploy/shellscript/juliaup-init.sh#L33).

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [May 30, 2024, 3:23pm UTC](https://discourse.julialang.org/t/changes-to-pkgservers-storage-backend/112378/26 "2024-05-30T15:23:26Z")

</div>

> [@davidanthoff](#):
>
> I’m just keeping the file around, in case we change our mind down the road so that we have a starting point, we could also just delete the file for now.

This seems like what version control is for. Having unused code in a repo is quite confusing. Similar with large blocks of commented out code. `git log -G` is your friend when you want to find it later.

[Previous page](https://discourse.julialang.org/t/changes-to-pkgservers-storage-backend/112378.md?page=1)