Documentation and code related to laconic self-hosting
Go to file
Thomas E Lackey e4690d4742 Split act-runner into its own pod. (#71)
```
$ laconic-so --stack act-runner deploy init --output act-runner.yml

$ laconic-so --stack act-runner deploy create --spec-file act-runner.yml --deployment-dir ~/opt/deployments/act-runner-1
$ echo "CERC_GITEA_RUNNER_REGISTRATION_TOKEN=FOO" >> ~/opt/deployments/act-runner-1/config.env
$ laconic-so deployment --dir ~/opt/deployments/act-runner-1 up
```

Reviewed-on: #71
Co-authored-by: Thomas E Lackey <telackey@bozemanpass.com>
Co-committed-by: Thomas E Lackey <telackey@bozemanpass.com>
2023-10-27 18:58:57 +00:00
act-runner Split act-runner into its own pod. (#71) 2023-10-27 18:58:57 +00:00
gitea Split act-runner into its own pod. (#71) 2023-10-27 18:58:57 +00:00
tls-proxy Fix http proxy config 2023-05-01 15:51:20 -06:00
README.md Initial Readme 2022-10-14 12:44:25 -06:00

Laconic Hosting

Documentation and code related to self-hosting laconic network development and build services.

Goals

  1. Bootstrap development services for Laconic including source code repository, CI/CD pipeline, package registries.
  2. Achieve #1 relying only on the following prerequisites:
    • General purpose computer hardware
    • Popular Linux distributions
    • Base software construction tools: compilers and so on
    • Docker (->Podman?)
    • Internet connectivity
    • Public DNS
    • A set of "seed" git repositories, hosted at an existing Laconic deployment, or GitHub for first-generation seed.
  3. Do not require any of the following (although they may be used if desired):
    • Commercial cloud hosting services
    • Public package registries
    • Public container repositories
    • Closed source software