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
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:
To view the chain logs, use:
To stop the running chain, use:
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.