0
0
Fork 0
mirror of https://codeberg.org/forgejo/docs.git synced 2025-01-13 01:09:42 -05:00
forgejo-docs/developer/infrastructure.md
Loïc Dachary ff4dabd77a
docs: developer: document the Octopuce hardware entrypoints
# Conflicts:
#	developer/infrastructure.md
2023-08-13 13:45:51 +01:00

1.8 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.lan internal domain.

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

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

The Forgejo instance internal to the VPN is deployed and upgraded using the following Enough command line:

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

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