CLI app for managing bitswan automation server and workspace deployments

• bitswan-workspaces
• Features
• Contribute

• Automatically set up independent bitswan workspaces deployments.
• Deployments can either connect to the bitswan.space SaaS, use the on prem bitswan management tools or operate completely independently

LATEST_VERSION=$(curl -s https://api.github.com/repos/bitswan-space/bitswan-workspaces/releases/latest | grep -Po '"tag_name": "\K.*?(?=")')
curl -L "https://github.com/bitswan-space/bitswan-workspaces/releases/download/${LATEST_VERSION}/bitswan-workspaces_${LATEST_VERSION}_linux_amd64.tar.gz" | tar -xz

LATEST_VERSION=$(curl -s https://api.github.com/repos/bitswan-space/bitswan-workspaces/releases/latest | grep -Po '"tag_name": "\K.*?(?=")')
curl -L "https://github.com/bitswan-space/bitswan-workspaces/releases/download/${LATEST_VERSION}/bitswan-workspaces_${LATEST_VERSION}_darwin_arm64.tar.gz" | tar -xz

LATEST_VERSION=$(curl -s https://api.github.com/repos/bitswan-space/bitswan-workspaces/releases/latest | grep -Po '"tag_name": "\K.*?(?=")')
curl -L "https://github.com/bitswan-space/bitswan-workspaces/releases/download/${LATEST_VERSION}/bitswan-workspaces_${LATEST_VERSION}_darwin_amd64.tar.gz" | tar -xz

Move the binary to a directory in your PATH

sudo mv bitswan /usr/local/bin/

Alternatively, if you don't have sudo access or prefer a local installation:

mkdir -p ~/bin
mv bitswan ~/bin/
#Add to PATH if using ~/bin (add this to your ~/.bashrc or ~/.zshrc)
export PATH="$HOME/bin:$PATH"

bitswan workspace init my-workspace

bitswan workspace init --domain=my-workspace.bitswan.io my-workspace

Note:

Before you initialize your workspace with an internal domain, make sure you have generated certificate for sub domain of workspace, e.g. *.my-workspace.my-domain.local. You have to specify path to the certificate and private key in init command. Certificate and private key must be in a format full-chain.pem and private-key.pem.

bitswan workspace init --domain=my-workspace.my-domain.local --certs-dir=/etc/certs my-workspace

This is for setting up a workspace locally without first setting up a domain name or connecting to the SaaS.

Create some certs for these domains using a certificate authority you setup for yourself.

mkcert --install

Add the CA certificate to Chrome by:

1. Navigate to chrome://settings/certificates
2. Go to "Authorities" tab
3. Click "Import" and select the ca.crt file
4. Check all trust settings and click "OK"

And finally setup the workspace.

bitswan workspace init --domain=bitswan.localhost --mkcerts dev-workspace

You should be able to access the editor in chrome via https://dev-workspace-editor.bitswan.localhost.

You can get the password to the editor using the command:

bitswan workspace list --long --passwords

If you wanna connect and persist your pipelines and GitOps configuration in remote git repository you can use --remote flag to specify your repository. main branch will be used to store pipelines code and each workspace will create it's own branch (e.g. my-workspace) to store their configurations.

bitswan workspace --remote=git@github.com:<your-name>/<your-repo>.git my-workspace

If you find issues in that setup or have some nice features / improvements, I would welcome an issue or a PR :)