496d3cbd68
Added deploy directory for spinning up container via docker-compose Added publish directory for publishing arm/amd images to docker hub Various tweeks to the source scripts Added test directory for easier testing of scripts and images |
||
|---|---|---|
| .. | ||
| conf | ||
| docker-compose.yaml | ||
| example.env | ||
| logs | ||
| readme.md | ||
| restart | ||
| run | ||
| scrub | ||
| start | ||
| stop | ||
| term | ||
| upgrade | ||
readme.md
use this deploy directory to deploy your uci caddy image to a container on a target machine.
requires docker-compose to be installed copy example.env to .env and edit accordingly decide if you want to bind mount the data and settings directories if so uncomment them in the compose file in the conf/ directory put your conf file and a caddy.pkgs file if needed and either edit the Caddyfile therein or create a .conf file with caddyfile settings
As to the image used it will either come from a repository (i.e. docker hub) or must be built on this machine.
If the former then the suggested approach is to copy this directory deploy onto the target machine to run caddy and rename it to caddy. This means you created a caddy image using this repository (and uci-docker-build) on another machine. See the readme.md. You'll need to use the "publish" script.
Otherwise you'll need to clone the uci-docker-build repository and install it to this machine first. Then you will need to build a local image. Then use that name in your .env file. This also means instead of running the upgrade command you'll need to run the build command and then restart the container.
copy example.env to .env and edit accordingly decide if you want to bind mount the data and settings directories if so uncomment them in the compose file in the conf/ directory put your conf file and a caddy.pkgs file if needed and either edit the Caddyfile therein or create a .conf file with caddyfile settings Set the correct IMAGE= for the image you'll be using, either locally build or from a repo.