feat: oneliner deployment setup for Linux and Mac #451
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR re-introduces the oneliner deployment bootstrap script, utilizing Conduit CLI.
It makes use of plain
sh
and generally attempts to be compatible across different shell setups.Works for Linux and Mac, on both arm64 and amd64, performing the following:
conduit deploy setup --config
Once merged, installing CLI and setting up a deployment on Linux/Mac should be as simple as:
sh <(curl -s https://getconduit.dev/bootstrap)
Notes:
Conduit CLI is currently installed under
~/conduit/bin/conduit
.On Linux we should respect Freedesktop XDG standards and use$HOME/.local/bin
instead.I'll update this PR addressing the latter.
Upon further consideration, the above could prove troublesome, as even though the majority of distros adhere to freedesktop standards and respect the XDG for their bash environment, explicit zsh installations don't seem to come with
$HOME/.local/bin
as part of the default $PATH.Seeing as changing this one down the road is not gonna result in any significant trouble for us or the users I'm just gonna ignore this for now(?) so as not to further clutter the installation script.
This oneliner does not raise any warnings regarding missing Docker or Docker compose.That should ideally be internally handled by CLI.
Addressed in ConduitPlatform/CLI#36
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
The PR fulfills these requirements:
main
branchfix #xxx
, where "xxx" is the issue number)If adding a new feature, the PR's description includes: