Static download URL

[bbockelm]

Currently, our "short" form of installing Pelican is something like this:

mkdir -p ~/.local/bin
pushd ~/.local/bin
curl -Ls https://github.com/PelicanPlatform/pelican/releases/download/v7.9.3/pelican_Linux_x86_64.tar.gz | tar zx --strip-components=1 pelican-7.9.3/pelican
popd
export PATH=~/.local/bin:$PATH

That is, well, not particularly short.

Two ideas:

1. In the GitHub Actions that build the website, we should determine the latest release and setup a redirect so a fixed URL can be used to get the latest version. Something like https://get.pelicanplatform.org/Linux_x86_64.tar.gz; no need to include the version number of the fact it is Pelican.
2. We should have a curl | sh version of the install that does all the above steps. Something like curl https://get.pelicanplatform.org | sh (which could do platform detection in the script and otherwise refer to the latest version as above).

[matyasselmeci]

This might go well with SOFTWARE-5966 (serving the Pelican artifacts from our own webserver).

[CannonLock]

@matyasselmeci @bbockelm This is assigned to Mat in Jira and me here. Who is responsible for its implementation?

[CannonLock]

Just talked to @brianhlin and since I just mucked a bunch with NGINX I figured I would take this.

[CannonLock]

@bbockelm How do you feel about splitting this into two services?

I put complete point 1 by moving this site to releases.pelicanplatform.org.

I complete point 2 by adding a redirect for get.pelicanplatform.org to a sh script that we place in the pelican repository.

I suggest this because I want the root of the release server to be able to list out the current offerings, but that is incompatible with the root being used to host the sh script to download the product.

[CannonLock]

https://pelican-release-server.chtc.wisc.edu

Going to close this as part 1 is done in production and create another ticket for part two.

#1663