- Go 96.2%
- Shell 3.8%
| .vscode | ||
| assets | ||
| cli | ||
| dozzle_data | ||
| scripts | ||
| .enc.cli-deploy.env | ||
| .enc.env | ||
| .env.example | ||
| .gitignore | ||
| .sops.yaml | ||
| docker-compose.yml | ||
| dockiy.manifest.yml | ||
| LICENSE | ||
| README.md | ||
DockIY
Own your infrastructure and CI/CD. DockIY is a self-hosted Docker setup for deploying multiple web apps to one server.
Documentation
Read the full documentation at dockiy.com:
- Installation
- Get started
- Managing servers
- Deploying applications
- CLI reference
- React template
- VitePress template
- Nuxt template
- Nuxt Better Auth template
Get started
This guide sets up one server and deploys one application. Complete the installation guide first to install Docker, SOPS, and rsync.
1. Connect DockIY to a server
dockiy setup
The command will walk you through setting up your server. You will need an SSH
connection string like user@56.213.224.182.
2. Set up DockIY services
dockiy server init
This creates a server repository, encrypted secrets, and dashboard logins, then deploys the services to your server. The initializer asks for an ACME email, hostnames, and login details for Umami, Dozzle, and Beszel. See Managing servers for details.
3. Create an application
dockiy app init
This asks for an application name, creates a repository with that directory
name, and writes the name to dockiy.yml. Available templates are react,
vitepress, nuxt, and nuxt-betterauth. You can also pass a Git URL of your
own.
Edit dockiy.yml, set the deployment hostnames, then commit the configuration:
git add .
git commit -m "feat: configure application"
4. Deploy the application
For an application with one default environment:
dockiy app deploy --version v0.1.0
For an application with staging and production environments:
dockiy app deploy staging
dockiy app deploy production --version v0.1.0
After deploying, check the server record and running containers:
dockiy app list
dockiy app status my-app default
Replace default with the environment name for staging or production. See
Deploying applications for
manifests, versions, retries, and rollbacks.