noun

  a device that holds a piece of work and guides the tool operating on it.

The package is both experimental AND unstable

New features likely will break existing setups unless both client and server are not in sync

Installation is done in two steps:

1. Server setup: Run a startup script on the server to pull all relevant images and take off
2. Client setup: Download a client and get authentication ready

Docker is a prerequisite, so ensure docker is available and running on your server

curl -fsSL https://deploywithjig.askh.at/init.sh | bash

This will load traefik, jig, ask you for an email, jwt signing key, launch everything and spit out a command to run on your machine to login

Login command will look something like jig login loooooong+code keep it for later

Any node package manager is a prerequisite

curl -fsSL https://deploywithjig.askh.at/install.sh | bash

Plug in your login command you got in previous steps with

jig login <loooooong+code>

Then initiate a project and create a config in your project directory with

jig init

Deploy your project with a single command. Jig will pack the project, send it to the server and build it remotely

jig deploy

Or build it locally using docker and deploy the image to the server. This is useful for CI and to save resources on the server

jig deploy -l

Let Traefik fetch certificates if you deploy with TLS enabled and you're done

• Manage multiple servers 🌿
• Check docker container resource consumption 💸
• Fetch container logs (forgor to implement 💀), maybe attahcing to the container even 🤔
• Deployment rollbacks!
• DNS management (? maybe)
• Improve CLI outputs
• Complex deployments