Commit Graph

14 Commits

Author SHA1 Message Date
13c844458b Pouint record at ts ip. 2024-08-24 11:07:29 -05:00
4d045744ff Deploy chat to mattermost in awful.club. 2024-05-30 17:54:03 -05:00
ece64af0ed Test mattermost.
- Add new DO records
- Create TF for provisioning mm virtual machine inside bikeshed
- write basic ansible play for deploying single node chat cluster.
2024-05-26 15:47:32 -05:00
7982871e25 Add calibre to mediaserver stack.
Investigating using calibre-web insteado of the full desktop
app. hopefully this works out well with using readarr as the primary
management interface.
2024-01-01 18:47:40 -06:00
c0a7ec54bf Remov unneeded arg, change IP to priv. 2024-01-01 15:05:10 -06:00
d4953760ed Repoint DNS from old hatchery cname to new highsea.
Also, remove some unneeded services that just didn't work out.
2023-12-31 23:23:56 -06:00
e45a5b7989 Create TF for highsea deploy. 2023-12-31 23:18:46 -06:00
5b0eb9d8a0 Misc tf changes; lock update. 2023-12-23 00:00:44 -06:00
d41e565feb Update old dns, create pms record. 2023-12-23 00:00:11 -06:00
e253cf9898 Add cluster nodes to ansible inventory, add DNS records. 2023-08-13 09:12:27 -05:00
f2bc058e20 Rename to make even easier to track. 2023-08-09 09:10:33 -05:00
ace9806e76 Split out record files to be domain specific, remove jitsi domain.
This doesn't solve my API limit problem but makes editing and viewing
current state in terraform much easier.
2023-08-09 09:08:43 -05:00
f83ec22eb8 Move to using DO:Spaces as state backend.
- Update provider.tf to include details about the backend
- Include AWS PROFILE export in env creds
- Update readme.
2023-08-06 20:41:36 -05:00
9046da30d9 Manage DO domains in Terraform!!
This is a nice step forward, for me. But there are some challenges
here I need to fix.

The first, and biggest one, is that DO rate limits API requests per
minute to ~250. If I'm doing even a small amount of changes and
iterating a lot I will run into issues with that just due to recrods;
each record pull appears to be its OWN CALL. God.

With that in mind, an easy next step seems like splitting the domain
management into their own submodules to prevent unnecessary calls.

For now, i'm just happy to have this managed in code :).
2023-07-30 09:37:11 -05:00