-
Notifications
You must be signed in to change notification settings - Fork 1
CI_SETUP
GitHub Actions Bot edited this page May 3, 2026
·
4 revisions
To enable the CI/CD workflows, you need to configure the following secrets in your GitHub repository settings:
Required for publishing Docker images to Docker Hub.
- DOCKERHUB_USERNAME: Your Docker Hub username
- DOCKERHUB_TOKEN: Docker Hub access token (not password)
- Log in to Docker Hub
- Go to Account Settings → Security
- Click "New Access Token"
- Give it a descriptive name (e.g., "GitHub Actions")
- Copy the token (you won't see it again)
- Go to your repository on GitHub
- Navigate to Settings → Secrets and variables → Actions
- Click "New repository secret"
- Add each secret:
- Name:
DOCKERHUB_USERNAME - Value: Your Docker Hub username
- Click "Add secret"
- Name:
DOCKERHUB_TOKEN - Value: The access token you created
- Click "Add secret"
The repository includes three main workflow files:
- Builds and publishes multi-arch Docker images
- Triggers on:
- Push to main/master branch
- Version tags (v*)
- Manual workflow dispatch
- Publishes to:
- Docker Hub:
nself/admin - GitHub Container Registry:
ghcr.io/nself-org/admin
- Configuration for multi-architecture builds
- Supports: linux/amd64, linux/arm64, linux/arm/v7
- Syncs documentation to GitHub Wiki
- Triggers when docs/ folder changes
- No additional secrets required (uses GITHUB_TOKEN)
After adding the secrets:
- Go to Actions tab in your repository
- Run "Docker Build and Publish" workflow manually
- Check the logs for successful authentication
- Verify DOCKERHUB_USERNAME and DOCKERHUB_TOKEN are set correctly
- Ensure the token has push permissions
- This uses the built-in GITHUB_TOKEN
- Ensure Actions have write permissions in Settings → Actions → General
- QEMU setup is automatic
- May take longer on first build due to emulation
Version: 1.0.0 | Updated: 2026-09-16 11:21 UTC | GitHub