rswafford/obico-images
Watch
1
0
Fork
You've already forked obico-images
 0
Code Issues Pull requests Projects Releases Packages 2 Wiki Activity Actions
Forgejo Actions workflows for building Obico images from the mirrored obico-server repository
5 commits 1 branch 0 tags 12 KiB
Find a file
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Ricky Swafford 92109d7d9d remove unsupported forgejo workflow permissions
2026-08-01 09:12:37 -05:00
.forgejo/workflows remove unsupported forgejo workflow permissions 2026-08-01 09:12:37 -05:00
compose add obico deployment env example 2026-08-01 08:40:30 -05:00
README.md add obico deployment env example 2026-08-01 08:40:30 -05:00

README.md

obico-images

Forgejo Actions workflow for building Obico Docker images from the mirrored rswafford/obico-server repository.

Repositories

  • rswafford/obico-server: mirror of upstream Obico source.
  • rswafford/obico-images: this repo; owns the build workflow and compose examples.

Images

The workflow publishes these images to the Forgejo container registry:

  • git.atomic-homelab.com/rswafford/obico-web
  • git.atomic-homelab.com/rswafford/obico-ml-api

Each image receives these tags:

  • latest
  • release
  • YYYY.MM.DD
  • sha-<short-sha>

The web and tasks services both use obico-web, matching upstream docker-compose.yml. The ml_api service uses obico-ml-api. Redis remains the upstream redis:7.2-alpine image.

Running A Build

Open the Actions tab for this repo in Forgejo and run Build Obico Images manually. It is also scheduled daily.

Deployment Compose

compose/docker-compose.pull.yml is a pull-only compose file based on upstream Obico's compose file, with build: replaced by the Forgejo registry images. It also uses named volumes for SQLite data and uploaded media because the pull-only image must not bind-mount over /app.

Copy compose/.env.example to compose/.env on the Docker host and fill in the values for your site before starting the stack.