Skip to content

Conversation

@quinngrier
Copy link

The basic setup is with Docker Compose, and Terraform is added on top for doing a public cloud setup. Each component is given its own Compose and Terraform setup. HTTP-only can be used for private setups, and HTTPS with automatic certificate renewal can be used for public cloud setups.

The code is structured to allow support for multiple cloud providers. This pull request only adds support for Amazon AWS as a starting point.

The directory gets packaged as divviup-bring-your-own.tar.gz and added to the release artifacts via the existing GitHub Actions workflow. The Docker image versions for divviup* and janus* sit on :latest in the repository, but get pinned in the release artifact.

There is also a companion pull request for the divviup/public-docs repository with documentation on how to use divviup-bring-your-own.tar.gz, which I'll link in a comment after I create that pull request as well.

The basic setup is with Docker Compose, and Terraform is added on top
for doing a public cloud setup. Each component is given its own Compose
and Terraform setup. HTTP-only can be used for private setups, and HTTPS
with automatic certificate renewal can be used for public cloud setups.

The code is structured to allow support for multiple cloud providers.
This commit only adds support for Amazon AWS as a starting point.

The directory gets packaged as divviup-bring-your-own.tar.gz and added
to the release artifacts via the existing GitHub Actions workflow. The
Docker image versions for divviup* and janus* sit on :latest in the
repository, but get pinned in the release artifact.

There is also a companion commit for the divviup/public-docs repository
with documentation on how to use divviup-bring-your-own.tar.gz.
@quinngrier
Copy link
Author

The pull request for the documentation is at divviup/public-docs#124.

@jcjones
Copy link
Contributor

jcjones commented Feb 4, 2025

Hi Quinn,

While I see the utility for these two PRs, we don’t have the capacity to maintain them here. Based on our experience with ENPA, truly flexible Infrastructure-as-Code repositories take a lot of work, and problems can easily crop up in configurations that we aren’t testing ourselves. I’d rather that these deployment tools live in a different repository, and we point there. That gives us the opportunity to make updates easier without being in lockstep with Janus versioning.

If you are interested in starting one and committing this code and documentation there, we can begin with linking to it from the Divvi Up API and Docs, and see where that takes us. Thank you for your interest in the Divvi Up project!

@quinngrier
Copy link
Author

Hi J.C.,

Thanks for responding! Restructuring these two PRs into a separate, fresh repository sounds like a good idea. I'll ping again when I have that ready, and we can go from there.

@quinngrier
Copy link
Author

I've finished restructuring the two PRs. The new repository is at https://github.com/stealthsoftwareinc/pollux, and the documentation is at https://stealthsoftwareinc.github.io/pollux/.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants