Files

84 lines
1.8 KiB
Markdown

# BaGet
## Overview
BaGet is the private NuGet package server for Silver Solutions.
URL:
```text
https://nuget.silveressence.net
```
Status:
```text
Running
```
Public HTTPS access is routed through Nginx Proxy Manager. The BaGet container is connected to the external `proxy` Docker network.
NuGet v3 feed:
```text
https://nuget.silveressence.net/v3/index.json
```
## Configuration
Current configuration is stored directly in the Docker Compose file.
Location:
```text
/srv/docker/baget/docker-compose.yml
```
Current configuration includes:
* ApiKey
* Storage configuration
* Database configuration
* Search configuration
## Data Storage
```text
/srv/docker/baget/data
```
This directory contains the SQLite database and hosted NuGet packages and should be included in backups.
## Reverse Proxy
| Setting | Value |
| ---------------- | ----------------------------------- |
| Public URL | `https://nuget.silveressence.net` |
| Target container | `baget` |
| Target port | `80` |
| Docker network | `proxy` |
## Gitea Actions Integration
The Silver 2.0 workflow at `.gitea/workflows/package.yml` publishes packages to this feed through the global `silverlinux-runner`.
Publishing requires the repository Actions secret:
```text
BAGET_API_KEY
```
It is stored under **Repository Settings -> Actions -> Secrets** and must never be committed to a repository.
The end-to-end Gitea Actions to BaGet publishing pipeline is operational.
### Secret Management
BaGet runtime secrets should be managed through:
```text
Infisical
```
This keeps BaGet aligned with the standard SilverLinux `slcompose` deployment pattern. The repository must not contain the real BaGet API key.