Add the rtm-astro-recipe repo as a submodule #14

Merged
moosemower merged 2 commits from astro-submodule into main 2026-04-26 23:53:04 +00:00
4 changed files with 40 additions and 2 deletions

5
.gitignore vendored
View File

@ -1,4 +1,5 @@
*~
abra/catalogue
abra/recipes
abra/logs
abra/recipes/*
!abra/recipes/rtm-astro-recipe
abra/logs

3
.gitmodules vendored Normal file
View File

@ -0,0 +1,3 @@
[submodule "abra/recipes/rtm-astro-recipe"]
path = abra/recipes/rtm-astro-recipe
url = https://git.coopcloud.tech/RTM/rtm-astro-recipe

33
README.md Normal file
View File

@ -0,0 +1,33 @@
## Setup
Members of RTM: check out the "RTM Reference" collective on our nextcloud for information on how to set up tailscale, ssh access, and user accounts on our servers. Without this, you won't be able to do operations.
Once you have network access, install abra. Read the "Install" and "Quick start"/"New operators tutorial" sections of https://docs.coopcloud.tech/abra/, which will guide you through `wget`ting abra.
Then, run:
```
$ git clone --recurse-submodules https://git.coopcloud.tech/RTM/rtm-config.git
$ cd rtm-config
$ abra server add laylotta.resisttechmonopolies.online
$ abra server add mango.resisttechmonmopolies.online
$ abra server add sootie.resisttechmonopolies.online
```
If you skipped the `--recurse-submodules` flag, you can still do `git submodule update --init` later to get the rtm-astro-recipe recipe.
## Usage
Once you've got this repo cloned and abra installed, you can run abra commands. To test:
```
$ abra app logs resisttechmonopolies.online
```
Should give a list of logs for our website! Other abra commands will work here.
From here, use `abra` to make changes (and reach out to a member of our infra/member-services working group for a tutorial if you would like!). Then, contribute your git changes back to this repository so everyone else sees what you've done and doesn't clobber your changes.
## Dev environment
Sootie is our dev server. If you would like to experiment with changes and fuck around there, use sootie! The implication here is that sootie has a greater chance of having uncommitted changes in its environment than other servers, and that these changes are safe to clobber over.