Build packages, maybe?
This commit is contained in:
parent
7f423652e3
commit
8937182cab
4 changed files with 122 additions and 4 deletions
|
@ -5,7 +5,7 @@ This guide explains how to set up and use Podcastrr with Forgejo for CI/CD and c
|
|||
## Prerequisites
|
||||
|
||||
- A Forgejo instance with:
|
||||
- CI/CD capabilities (Drone integration)
|
||||
- Forgejo Actions enabled (preferred) or CI/CD capabilities (Drone integration)
|
||||
- Container registry enabled
|
||||
- Docker and Docker Compose installed on your local machine
|
||||
- Git installed on your local machine
|
||||
|
@ -28,19 +28,48 @@ This guide explains how to set up and use Podcastrr with Forgejo for CI/CD and c
|
|||
|
||||
In your Forgejo repository settings, add the following secrets:
|
||||
|
||||
#### For Forgejo Actions (Recommended)
|
||||
Navigate to your repository settings, then Actions, then Secrets:
|
||||
|
||||
- `FORGEJO_REGISTRY`: Your Forgejo container registry URL (e.g., `registry.your-forgejo-instance.com`)
|
||||
- `FORGEJO_USERNAME`: Your Forgejo username
|
||||
- `FORGEJO_PASSWORD`: Your Forgejo password
|
||||
|
||||
#### For Drone CI (Legacy)
|
||||
Navigate to your repository settings, then Secrets:
|
||||
|
||||
- `docker_username`: Your Forgejo username or container registry username
|
||||
- `docker_password`: Your Forgejo password or container registry password
|
||||
- `webhook_url` (optional): URL for build notifications
|
||||
|
||||
### 3. Environment Variables
|
||||
|
||||
#### For Drone CI (Legacy)
|
||||
Configure the following environment variables in your Forgejo CI/CD settings:
|
||||
|
||||
- `DRONE_REGISTRY`: Your Forgejo container registry URL (e.g., `registry.your-forgejo-instance.com`)
|
||||
|
||||
## CI/CD Pipeline
|
||||
|
||||
The included `.drone.yml` file defines a CI/CD pipeline that:
|
||||
### Forgejo Actions (Recommended)
|
||||
|
||||
The project includes Forgejo Actions workflows in the `.forgejo/workflows/` directory:
|
||||
|
||||
1. **Demo Workflow** (`.forgejo/workflows/demo.yaml`): A simple example workflow that runs on every push.
|
||||
|
||||
2. **Build and Publish Workflow** (`.forgejo/workflows/build.yml`): A comprehensive CI/CD pipeline that:
|
||||
- Runs tests on every push and pull request
|
||||
- Builds and pushes a Docker image to your container registry on pushes to the main branch or tags
|
||||
- Provides build status notifications
|
||||
|
||||
To use Forgejo Actions:
|
||||
1. Ensure "Enable Repository Actions" is checked in your repository settings
|
||||
2. The workflows will automatically run when you push to the repository
|
||||
3. View results in the Actions tab of your repository
|
||||
|
||||
### Drone CI (Legacy)
|
||||
|
||||
The included `.drone.yml` file defines a legacy CI/CD pipeline that:
|
||||
|
||||
1. Runs tests on every push and pull request
|
||||
2. Builds and pushes a Docker image to your container registry on pushes to the main branch
|
||||
|
@ -103,4 +132,4 @@ docker build -t podcastrr:local .
|
|||
|
||||
- [Forgejo Documentation](https://forgejo.org/docs/)
|
||||
- [Drone CI Documentation](https://docs.drone.io/)
|
||||
- [Docker Documentation](https://docs.docker.com/)
|
||||
- [Docker Documentation](https://docs.docker.com/)
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue