updated with Action Runner
This commit is contained in:
@@ -24,6 +24,8 @@ Public IP: 51.255.83.140
|
||||
* Jitsi Meet
|
||||
* Portainer
|
||||
* Nginx Proxy Manager
|
||||
* BaGet
|
||||
* Gitea Actions Runner (`silverlinux-runner`)
|
||||
|
||||
## Domains
|
||||
|
||||
@@ -35,6 +37,8 @@ meet.silveressence.net -> Jitsi
|
||||
|
||||
portainer.silveressence.net -> Portainer
|
||||
|
||||
nuget.silveressence.net -> BaGet (through Nginx Proxy Manager)
|
||||
|
||||
## Secrets
|
||||
|
||||
Secrets are stored in:
|
||||
@@ -55,6 +59,16 @@ internal
|
||||
Gitea:
|
||||
|
||||
* Local accounts
|
||||
|
||||
## CI/CD
|
||||
|
||||
Gitea Actions is enabled globally.
|
||||
|
||||
The global self-hosted runner is operational at `/srv/docker/gitea-runner` with the name `silverlinux-runner`.
|
||||
|
||||
Silver 2.0 uses `.gitea/workflows/package.yml` to publish NuGet packages to BaGet when a push to `net-8-version` has a commit message containing `[Package]`.
|
||||
|
||||
The runner registration token is stored in `/srv/secrets/company.env`. The BaGet publishing key is stored as the repository Actions secret `BAGET_API_KEY`.
|
||||
* OpenID disabled
|
||||
* Google OAuth planned
|
||||
* GitHub OAuth planned
|
||||
@@ -78,3 +92,5 @@ and the README.md of each service folder before making infrastructure recommenda
|
||||
* Centralized secrets implemented
|
||||
* Nginx Proxy Manager selected
|
||||
* PostgreSQL selected as shared database platform
|
||||
* BaGet deployed at nuget.silveressence.net through Nginx Proxy Manager
|
||||
* Gitea Actions and a global self-hosted runner selected for package publishing
|
||||
|
||||
@@ -156,6 +156,46 @@ Medium
|
||||
|
||||
---
|
||||
|
||||
#### BaGet Data
|
||||
|
||||
Location:
|
||||
|
||||
```text
|
||||
/srv/docker/baget/data
|
||||
```
|
||||
|
||||
Contains:
|
||||
|
||||
* Hosted NuGet packages
|
||||
* SQLite database
|
||||
|
||||
Importance:
|
||||
|
||||
Medium
|
||||
|
||||
---
|
||||
|
||||
#### Gitea Actions Runner Configuration
|
||||
|
||||
Location:
|
||||
|
||||
```text
|
||||
/srv/docker/gitea-runner
|
||||
```
|
||||
|
||||
Contains:
|
||||
|
||||
* Runner deployment configuration
|
||||
* Runner state
|
||||
|
||||
The registration token is stored separately in `/srv/secrets/company.env`.
|
||||
|
||||
Importance:
|
||||
|
||||
Medium
|
||||
|
||||
---
|
||||
|
||||
## Backup Storage
|
||||
|
||||
Current Location:
|
||||
@@ -214,6 +254,8 @@ Restore order:
|
||||
5. OpenProject
|
||||
6. Portainer
|
||||
7. Jitsi
|
||||
8. BaGet
|
||||
9. Gitea Actions Runner
|
||||
|
||||
---
|
||||
|
||||
|
||||
+98
-185
@@ -2,246 +2,159 @@
|
||||
|
||||
## Overview
|
||||
|
||||
The goal of SilverLinux is to become the central deployment platform for Silver Solutions applications.
|
||||
|
||||
Source code is managed through Gitea and future deployments should be automated through CI/CD pipelines.
|
||||
SilverLinux provides CI/CD through globally enabled Gitea Actions and a self-hosted runner. Package publishing is operational; application deployment to Windows IIS and Linux targets remains future work.
|
||||
|
||||
---
|
||||
|
||||
## Current Situation
|
||||
## Gitea Actions
|
||||
|
||||
Application deployments are currently performed manually.
|
||||
|
||||
Typical process:
|
||||
|
||||
1. Developer commits code.
|
||||
2. Developer publishes application.
|
||||
3. Files are deployed manually.
|
||||
4. IIS application is restarted if necessary.
|
||||
Gitea Actions is enabled in Gitea's `app.ini` and is available globally.
|
||||
|
||||
Status:
|
||||
|
||||
```text
|
||||
Manual
|
||||
Operational
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Future Goal
|
||||
## Self-Hosted Runner
|
||||
|
||||
Automate deployments from Gitea repositories to target servers.
|
||||
| Property | Value |
|
||||
| --- | --- |
|
||||
| Location | `/srv/docker/gitea-runner` |
|
||||
| Image | `gitea/act_runner:latest` |
|
||||
| Runner name | `silverlinux-runner` |
|
||||
| Runner type | Global Runner |
|
||||
| Status | Operational |
|
||||
|
||||
Examples:
|
||||
Runner labels:
|
||||
|
||||
* Windows IIS servers
|
||||
* Application servers
|
||||
* Test environments
|
||||
* Future Linux deployments
|
||||
* `ubuntu-latest`
|
||||
* `ubuntu-24.04`
|
||||
* `ubuntu-22.04`
|
||||
|
||||
The global runner can execute Actions workflows for repositories hosted by the SilverLinux Gitea instance.
|
||||
|
||||
---
|
||||
|
||||
## Planned Architecture
|
||||
## Silver 2.0 Package Publishing
|
||||
|
||||
Workflow:
|
||||
|
||||
```text
|
||||
Developer
|
||||
↓
|
||||
Git Commit
|
||||
↓
|
||||
Gitea
|
||||
↓
|
||||
Gitea Actions
|
||||
↓
|
||||
Build
|
||||
↓
|
||||
Test
|
||||
↓
|
||||
Deploy
|
||||
↓
|
||||
Target Server
|
||||
.gitea/workflows/package.yml
|
||||
```
|
||||
|
||||
The workflow runs when both conditions are satisfied:
|
||||
|
||||
1. Code is pushed to the `net-8-version` branch.
|
||||
2. The commit message contains `[Package]`.
|
||||
|
||||
Example commit message:
|
||||
|
||||
```text
|
||||
Package Silver 2.0 libraries [Package]
|
||||
```
|
||||
|
||||
Pipeline steps:
|
||||
|
||||
1. Check out the repository.
|
||||
2. Install the .NET 8 SDK.
|
||||
3. Restore the solution.
|
||||
4. Build the solution using the `Deploy` configuration.
|
||||
5. Pack the NuGet packages.
|
||||
6. Push the packages to BaGet.
|
||||
|
||||
NuGet feed:
|
||||
|
||||
```text
|
||||
https://nuget.silveressence.net/v3/index.json
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Deployment Targets
|
||||
## Operational Flow
|
||||
|
||||
```text
|
||||
Git push
|
||||
-> Gitea Actions
|
||||
-> silverlinux-runner
|
||||
-> dotnet restore
|
||||
-> dotnet build
|
||||
-> dotnet pack
|
||||
-> BaGet package publish
|
||||
```
|
||||
|
||||
The complete workflow has been tested successfully and is operational.
|
||||
|
||||
---
|
||||
|
||||
## Secrets
|
||||
|
||||
Runner registration token:
|
||||
|
||||
```text
|
||||
/srv/secrets/company.env
|
||||
GITEA_RUNNER_REGISTRATION_TOKEN
|
||||
```
|
||||
|
||||
BaGet publishing credential:
|
||||
|
||||
```text
|
||||
Repository Settings -> Actions -> Secrets
|
||||
BAGET_API_KEY
|
||||
```
|
||||
|
||||
No credentials are stored in repositories. Infrastructure-level secrets belong in `company.env`; repository workflow secrets belong in Gitea Actions Secrets.
|
||||
|
||||
---
|
||||
|
||||
## Future Deployment Targets
|
||||
|
||||
### Windows IIS
|
||||
|
||||
Purpose:
|
||||
|
||||
Deploy:
|
||||
|
||||
* ASP.NET Core
|
||||
* Blazor Server
|
||||
* Blazor Web App
|
||||
|
||||
Method:
|
||||
Planned targets include ASP.NET Core, Blazor Server and Blazor Web App deployments.
|
||||
|
||||
```text
|
||||
Publish
|
||||
→ Copy Files
|
||||
→ Restart IIS Site
|
||||
Publish -> Copy files -> Restart IIS site
|
||||
```
|
||||
|
||||
Status:
|
||||
|
||||
Planned
|
||||
|
||||
---
|
||||
Status: Planned
|
||||
|
||||
### Linux Containers
|
||||
|
||||
Purpose:
|
||||
|
||||
Future Docker deployments.
|
||||
|
||||
Method:
|
||||
|
||||
```text
|
||||
Build Docker Image
|
||||
→ Push Image
|
||||
→ Deploy Stack
|
||||
Build image -> Push image -> Deploy stack
|
||||
```
|
||||
|
||||
Status:
|
||||
|
||||
Future
|
||||
|
||||
---
|
||||
|
||||
## Planned Tooling
|
||||
|
||||
### Gitea Actions
|
||||
|
||||
Purpose:
|
||||
|
||||
* Build automation
|
||||
* Testing
|
||||
* Deployment automation
|
||||
|
||||
Status:
|
||||
|
||||
Planned
|
||||
|
||||
---
|
||||
|
||||
### Self-Hosted Runner
|
||||
|
||||
Purpose:
|
||||
|
||||
Execute build pipelines.
|
||||
|
||||
Potential Location:
|
||||
|
||||
```text
|
||||
SilverLinux
|
||||
```
|
||||
|
||||
Status:
|
||||
|
||||
Planned
|
||||
|
||||
---
|
||||
|
||||
## Pipeline Stages
|
||||
|
||||
### Build
|
||||
|
||||
Examples:
|
||||
|
||||
* Restore NuGet packages
|
||||
* Build solution
|
||||
* Publish application
|
||||
|
||||
---
|
||||
|
||||
### Test
|
||||
|
||||
Examples:
|
||||
|
||||
* Unit tests
|
||||
* Integration tests
|
||||
* Build validation
|
||||
|
||||
---
|
||||
|
||||
### Deploy
|
||||
|
||||
Examples:
|
||||
|
||||
* IIS deployment
|
||||
* Docker deployment
|
||||
* Environment updates
|
||||
|
||||
---
|
||||
|
||||
## Notifications
|
||||
|
||||
Future CI/CD notifications should use:
|
||||
|
||||
```text
|
||||
noreply@silveressence.net
|
||||
```
|
||||
|
||||
Examples:
|
||||
|
||||
* Build succeeded
|
||||
* Build failed
|
||||
* Deployment completed
|
||||
* Deployment failed
|
||||
|
||||
---
|
||||
|
||||
## Security
|
||||
|
||||
Deployment credentials should never be stored in repositories.
|
||||
|
||||
Store credentials in:
|
||||
|
||||
```text
|
||||
/ srv/secrets/company.env
|
||||
```
|
||||
|
||||
or platform-specific secret stores.
|
||||
|
||||
---
|
||||
|
||||
## Initial Target
|
||||
|
||||
First automated deployment target:
|
||||
|
||||
```text
|
||||
Gitea
|
||||
→
|
||||
Windows Server IIS
|
||||
→
|
||||
Blazor Applications
|
||||
```
|
||||
|
||||
This provides the highest immediate value.
|
||||
Status: Future
|
||||
|
||||
---
|
||||
|
||||
## Future Enhancements
|
||||
|
||||
* Automatic testing
|
||||
* Automatic deployment
|
||||
* Automated tests
|
||||
* Automated Windows IIS deployment
|
||||
* Linux container deployment
|
||||
* Release pipelines
|
||||
* Docker image registry
|
||||
* BaGet integration
|
||||
* Multi-environment deployments
|
||||
* Package publishing for additional repositories
|
||||
|
||||
---
|
||||
|
||||
## Related Services
|
||||
|
||||
* Gitea
|
||||
* Gitea Actions Runner
|
||||
* BaGet
|
||||
* Portainer
|
||||
* Nginx Proxy Manager
|
||||
|
||||
---
|
||||
|
||||
## Related Documentation
|
||||
|
||||
* gitea/README.md
|
||||
* baget/README.md
|
||||
* docs/server.md
|
||||
* docs/security.md
|
||||
* docs/secrets.md
|
||||
|
||||
@@ -228,6 +228,52 @@ Implemented
|
||||
|
||||
---
|
||||
|
||||
## 2026-06-21 - Adopt Gitea Actions + Self-Hosted Runner for Package Publishing
|
||||
|
||||
Decision:
|
||||
|
||||
* Replace GitHub Actions with self-hosted Gitea Actions.
|
||||
* Execute package publishing on SilverLinux using the global `silverlinux-runner`.
|
||||
* Publish internal NuGet packages to BaGet.
|
||||
* Store the runner registration token in `/srv/secrets/company.env` and publishing credentials in Gitea Actions Secrets.
|
||||
* Use `[Package]` in commit messages to request commit-driven package publishing.
|
||||
|
||||
Reason:
|
||||
|
||||
* Keep source control, build execution and package hosting inside SilverLinux.
|
||||
* Avoid storing credentials in repositories.
|
||||
* Provide a simple, explicit package-release convention.
|
||||
|
||||
Status:
|
||||
|
||||
```text
|
||||
Accepted
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 2026-06-21 - BaGet Secret Storage
|
||||
|
||||
Decision:
|
||||
|
||||
The BaGet API key is currently stored directly in the BaGet Docker Compose configuration.
|
||||
|
||||
Reason:
|
||||
|
||||
* Simplicity during initial deployment.
|
||||
|
||||
Future Plan:
|
||||
|
||||
Move the API key into the centralized SilverLinux secrets management system located at:
|
||||
|
||||
```text
|
||||
/srv/secrets/company.env
|
||||
```
|
||||
|
||||
when additional services begin consuming the same secret management approach.
|
||||
|
||||
---
|
||||
|
||||
## Future Decisions
|
||||
|
||||
Document future decisions using the following template:
|
||||
|
||||
+13
-3
@@ -113,8 +113,6 @@ portainer
|
||||
|
||||
---
|
||||
|
||||
## Planned Domains
|
||||
|
||||
### BaGet
|
||||
|
||||
Domain:
|
||||
@@ -127,10 +125,22 @@ Purpose:
|
||||
|
||||
* Private NuGet package hosting
|
||||
|
||||
Container:
|
||||
|
||||
```text
|
||||
baget
|
||||
```
|
||||
|
||||
Routing:
|
||||
|
||||
```text
|
||||
Nginx Proxy Manager -> baget:80
|
||||
```
|
||||
|
||||
Status:
|
||||
|
||||
```text
|
||||
Planned
|
||||
Active
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
@@ -79,6 +79,21 @@ Used by:
|
||||
|
||||
---
|
||||
|
||||
### Gitea Actions Runner
|
||||
|
||||
```text
|
||||
GITEA_RUNNER_REGISTRATION_TOKEN
|
||||
```
|
||||
|
||||
Used by:
|
||||
|
||||
* The global `silverlinux-runner`
|
||||
* Runner registration and reconnection
|
||||
|
||||
Repository workflow credentials, including `BAGET_API_KEY`, are stored in Gitea under **Repository Settings -> Actions -> Secrets** and are not stored in repositories.
|
||||
|
||||
---
|
||||
|
||||
### Jitsi
|
||||
|
||||
```text
|
||||
|
||||
@@ -104,6 +104,8 @@ Examples:
|
||||
* Jitsi Meet
|
||||
* Portainer
|
||||
* Nginx Proxy Manager
|
||||
* BaGet
|
||||
* Gitea Actions Runner
|
||||
|
||||
---
|
||||
|
||||
@@ -124,6 +126,8 @@ Contains:
|
||||
/srv/docker/jitsi
|
||||
/srv/docker/portainer
|
||||
/srv/docker/nginx-proxy-manager
|
||||
/srv/docker/baget
|
||||
/srv/docker/gitea-runner
|
||||
```
|
||||
|
||||
---
|
||||
@@ -202,6 +206,28 @@ Suggested structure:
|
||||
|
||||
---
|
||||
|
||||
### BaGet
|
||||
|
||||
```text
|
||||
/srv/docker/baget/data
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Gitea Actions Runner
|
||||
|
||||
```text
|
||||
/srv/docker/gitea-runner
|
||||
```
|
||||
|
||||
Runner:
|
||||
|
||||
```text
|
||||
silverlinux-runner
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## SSH Access
|
||||
|
||||
Primary user:
|
||||
|
||||
+67
-22
@@ -135,6 +135,73 @@ Running
|
||||
|
||||
---
|
||||
|
||||
### BaGet
|
||||
|
||||
URL:
|
||||
|
||||
```text
|
||||
https://nuget.silveressence.net
|
||||
```
|
||||
|
||||
Purpose:
|
||||
|
||||
* Private NuGet repository
|
||||
* Internal Silver.* package distribution
|
||||
* Package source for CI/CD
|
||||
* Package source for team development
|
||||
|
||||
Access:
|
||||
|
||||
* Routed through Nginx Proxy Manager
|
||||
|
||||
Status:
|
||||
|
||||
```text
|
||||
Running
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Gitea Actions Runner
|
||||
|
||||
Location:
|
||||
|
||||
```text
|
||||
/srv/docker/gitea-runner
|
||||
```
|
||||
|
||||
Image:
|
||||
|
||||
```text
|
||||
gitea/act_runner:latest
|
||||
```
|
||||
|
||||
Runner Name:
|
||||
|
||||
```text
|
||||
silverlinux-runner
|
||||
```
|
||||
|
||||
Type:
|
||||
|
||||
```text
|
||||
Global Runner
|
||||
```
|
||||
|
||||
Labels:
|
||||
|
||||
* `ubuntu-latest`
|
||||
* `ubuntu-24.04`
|
||||
* `ubuntu-22.04`
|
||||
|
||||
Status:
|
||||
|
||||
```text
|
||||
Operational
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Shared Infrastructure
|
||||
|
||||
### Docker
|
||||
@@ -188,28 +255,6 @@ Active
|
||||
|
||||
---
|
||||
|
||||
## Planned Services
|
||||
|
||||
### BaGet
|
||||
|
||||
URL:
|
||||
|
||||
```text
|
||||
https://nuget.silveressence.net
|
||||
```
|
||||
|
||||
Purpose:
|
||||
|
||||
* Private NuGet package hosting
|
||||
|
||||
Status:
|
||||
|
||||
```text
|
||||
Planned
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Removed Services
|
||||
|
||||
### Plane.so
|
||||
|
||||
Reference in New Issue
Block a user