forgejo working
This commit is contained in:
parent
f439eec43e
commit
2c9a70f0fd
3 changed files with 37 additions and 5 deletions
|
|
@ -102,3 +102,24 @@ Vaultwarden is a credentials manager.
|
|||
* Stop Vaultwarden.
|
||||
* Overwrite the data folder with one of the backups.
|
||||
* Start it up again.
|
||||
|
||||
## Forgejo
|
||||
|
||||
Forgejo is a git server.
|
||||
|
||||
### Deploy
|
||||
|
||||
* Decide what subdomain you want to serve Forgejo on and add it to `services/forgejo/forgejo_vars.yml` on the `forgejo_subdomain`.
|
||||
* Note that you will have to add a DNS entry to point to the VPS public IP.
|
||||
* Run the deployment playbook: `ansible-playbook -i inventory.ini services/forgejo/deploy_forgejo_playbook.yml`.
|
||||
|
||||
### Configure
|
||||
|
||||
* Forgejo will be available for you to create a user on first start. Do that and store the creds safely.
|
||||
* Default behaviour after that is not allow for registrations.
|
||||
* You can tweak more settings from that point on.
|
||||
* SSH cloning should work out of the box (after you've set up your SSH pub key in Forgejo, that is).
|
||||
|
||||
### Backups
|
||||
|
||||
No explicit backups. It's assumed that important repos will be in Lapy, and that perhaps you might even backup lapy as well.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue