development docker image
Build LinkLog Development Image / development-image (push) Failing after 49s

This commit is contained in:
Olaf
2026-08-25 21:09:58 +02:00
parent 442a28e741
commit d38db06c30
2 changed files with 37 additions and 0 deletions
+35
View File
@@ -0,0 +1,35 @@
name: Build LinkLog Development Image
on:
push:
branches:
- main
workflow_dispatch:
env:
IMAGE_NAME: git.kolkman.org/olaf/link-log
jobs:
development-image:
runs-on: ubuntu-latest
steps:
- name: Check out main
uses: actions/checkout@v4
- name: Log in to Gitea container registry
uses: docker/login-action@v3
with:
registry: git.kolkman.org
username: ${{ secrets.REGISTRY_USERNAME }}
password: ${{ secrets.REGISTRY_PASSWORD }}
- name: Build and publish development image
uses: docker/build-push-action@v6
with:
context: .
push: true
tags: ${{ env.IMAGE_NAME }}:development
labels: |
org.opencontainers.image.source=https://git.kolkman.org/olaf/Link-Log
org.opencontainers.image.revision=${{ gitea.sha }}
org.opencontainers.image.version=development
+2
View File
@@ -114,6 +114,8 @@ The extension's `update_url` points at the stable raw repository URL `https://gi
The workflow requires Gitea Actions secrets named `REGISTRY_USERNAME`, `REGISTRY_PASSWORD`, and `GITEA_TOKEN`. The token needs permission to create releases and upload release assets; the registry credentials need permission to push the image. The workflow requires Gitea Actions secrets named `REGISTRY_USERNAME`, `REGISTRY_PASSWORD`, and `GITEA_TOKEN`. The token needs permission to create releases and upload release assets; the registry credentials need permission to push the image.
Every push to `main` also runs `.gitea/workflows/development.yml` and publishes the current Docker image as `git.kolkman.org/olaf/link-log:development`. The workflow uses the same `REGISTRY_USERNAME` and `REGISTRY_PASSWORD` secrets and can also be started manually from Gitea Actions.
Appending a username to the root URL, such as `/alice`, opens that user's public feed and profile information. Appending a username to the root URL, such as `/alice`, opens that user's public feed and profile information.
Configuration APIs require a bearer token returned by the login endpoint. User configuration uses the identity in that token. Plugin administration additionally requires an administrator account; the development `alice` account is seeded as an administrator, while `bob` is a standard user. Configuration APIs require a bearer token returned by the login endpoint. User configuration uses the identity in that token. Plugin administration additionally requires an administrator account; the development `alice` account is seeded as an administrator, while `bob` is a standard user.