-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: spaceship #103
Merged
Merged
feat: spaceship #103
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Conflicts: # tools/debug/go.mod # tools/debug/go.sum # tools/debug/main.go
# Conflicts: # tools/debug/go.mod # tools/debug/go.sum # tools/debug/main.go
julienrbrt
previously approved these changes
Aug 1, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK!
Are you able to upload multiple chains via spaceship?
I think to get most of this (as in this form this is like a wrapper for scp
) we should pre-setup docker or systemd services.
julienrbrt
approved these changes
Aug 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Spaceship offers several ways to connect to your SSH server:
Each time you run this command, the binary is built, and the chain home folder is created based on the chain configuration.
The app then connects to the server via SSH, creates workspaces, transfers the binary, and runs it using a runner script.
The workspaces are created in
$HOME/workspace/<chain-id>
and consist of the following elements:$HOME/workspace/<chain-id>/bin
- The directory containing the chain binary.$HOME/workspace/<chain-id>/home
- The chain home folder.$HOME/workspace/<chain-id>/log
- Logs of the running chain.$HOME/workspace/<chain-id>/run.sh
- Runner script to run the binary in the background using nohup.$HOME/workspace/<chain-id>/spaceship.pid
- The PID of the currently running chain.To check the status of your chain, use:
ignite spaceship status root@127.0.0.1 --key $HOME/.ssh/id_rsa
To view the chain logs, use:
ignite spaceship log root@127.0.0.1 --key $HOME/.ssh/id_rsa
To stop the running chain, use:
ignite spaceship stop root@127.0.0.1 --key $HOME/.ssh/id_rsa
If you need to redeploy the chain on the same server, the home folder will not be overwritten. To reinitialize the chain, use the
--init-chain
flag.