0
0
Fork 0
mirror of https://codeberg.org/forgejo/docs.git synced 2025-03-13 09:58:07 -04:00

docs: developer: document the Octopuce hardware entrypoints

# Conflicts:
#	developer/infrastructure.md
This commit is contained in:
Loïc Dachary 2023-05-04 14:57:54 +02:00 committed by Caesar Schinas
parent bcb326a3c9
commit ff4dabd77a
No known key found for this signature in database
GPG key ID: AE9108461BEA5ACF
3 changed files with 51 additions and 25 deletions

View file

@ -17,28 +17,3 @@ To make these repositories easier to find, the following push mirrors are in pla
- https://code.forgejo.org/forgejo/runner => https://codeberg.org/forgejo/runner
- https://code.forgejo.org/forgejo/act => https://codeberg.org/forgejo/act
## Infrastructure
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](https://enough-community.readthedocs.io):
```shell
$ 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:
```shell
$ 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:
```shell
enough --domain code.forgejo.org ssh bind-host
```

View file

@ -17,5 +17,6 @@ their needs.
- [code.forgejo.org](code-forgejo-org)
- [Forgejo runner implementation notes](forgejo-runner)
- For maintainers
- [Hardware infrastructure](infrastructure)
- [Release management](RELEASE)
- [Secrets](SECRETS)

View file

@ -0,0 +1,50 @@
---
layout: '~/layouts/Markdown.astro'
title: Hardware infrastructure
license: 'CC-BY-SA-4.0'
---
## Octopuce
[Octopuce provides hardware](https://codeberg.org/forgejo/sustainability) managed by [the devops team](https://codeberg.org/forgejo/governance/src/branch/main/TEAMS.md#devops). 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](https://enough-community.readthedocs.io):
```shell
$ 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](https://enough-community.readthedocs.io):
```shell
$ 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](https://enough-community.readthedocs.io):
```shell
$ 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:
```shell
$ 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:
```shell
enough --domain code.forgejo.org ssh bind-host
```