0
0
Fork 0
mirror of https://codeberg.org/forgejo/docs.git synced 2024-11-28 18:42:51 -05:00
forgejo-docs/developer/infrastructure.md
Earl Warren dddc40622b
docs: update the Forgejo infrastructure documentation
It is made simpler with just a single domain. Part of the hosts have
internal IPs (10.x.x.x) that are only routed when connected with the
VPN.
2023-08-13 13:45:53 +01:00

1.5 KiB

layout title license
~/layouts/Markdown.astro Hardware infrastructure CC-BY-SA-4.0

Octopuce

Octopuce provides hardware managed by the devops team. It can be accessed via a VPN which provides a DNS for the octopuce.forgejo.org internal domain.

The VPN is deployed and upgraded using the following Enough command line:

$ mkdir -p ~/.enough
$ git clone https://forgejo.octopuce.forgejo.org/forgejo/enough ~/.enough/octopuce.forgejo.org
$ enough --domain octopuce.forgejo.org service create openvpn

OVH

https://code.forgejo.org runs on an OVH virtual machine using the same OVH account used for the forgejo.org domain name and mails.

It is deployed and upgraded using the following Enough command line:

$ mkdir -p ~/.enough
$ git clone https://code.forgejo.org/forgejo/<secret repository> ~/.enough/code.forgejo.org
$ enough --domain code.forgejo.org service create --host bind-host forgejo

Upgrading only Forgejo:

$ enough --domain code.forgejo.org playbook -- --limit bind-host,localhost --private-key ~/.enough/code.forgejo.org/infrastructure_key venv/share/enough/playbooks/forgejo/forgejo-playbook.yml

Login in the machine hosting the Forgejo instance for debugging purposes:

enough --domain code.forgejo.org ssh bind-host