Skip to content

install.sh: installs superfluid, the server basert serve runs, beside basert - #69

Open
IsuraManchanayake wants to merge 1 commit into
basecompute:mainfrom
IsuraManchanayake:install-superfluid
Open

IsuraManchanayake wants to merge 1 commit into
basecompute:mainfrom
IsuraManchanayake:install-superfluid

Conversation

@IsuraManchanayake

Copy link
Copy Markdown

What changed

After unpacking the bundle, the installer runs basert superfluid install, the installed basert's own installer for superfluid, the server basert serve runs from 0.4.0 on: it downloads the superfluid release that basert was tested with, checks its SHA-256 against the one the release publishes, and puts it beside basert, where basert serve looks first. The step is skipped for a release whose basert has no such command (0.3.x and earlier) and is not fatal when the download fails: basert serve installs superfluid at its first start, and the command to run by hand is printed. The "Try it" lines gain basert serve.

Why

baseRT 0.4.0 ships no server of its own: basert serve runs superfluid (https://github.com/basecompute/superfluid), which is not bundled with basert. The script is where most users get basert, so it is where superfluid should arrive too, without a second implementation of the download: the pin, the platform and the checksum live in basert.

How it was tested

  • sh -n install.sh.
  • The command it calls, basert superfluid install, is exercised in baseRT-internal's launcher PR (basecompute/baseRT-internal#722): against a fake release in the tests, and against a real superfluid build laid out as a release.
  • Not run: the script end to end against a published 0.4.0 bundle and the v0.1.3 superfluid tag, neither of which exists yet; until 0.4.0 is released the new step is skipped on every install, since no released basert has the command.

… basert

basert 0.4.0 does not bundle superfluid: after unpacking, the script runs
the installed basert's own installer, which downloads the release that
basert was tested with, checks its SHA-256 against the published one and
puts it beside basert. The step is skipped for a release without the
command and is not fatal: basert serve installs superfluid at its first
start, and basert superfluid install does it by hand.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant