gomods / athens

A Go module datastore and proxy
https://docs.gomods.io
MIT License
4.41k stars 497 forks source link

Should we create new repositories in the gomods organization for deployment artifacts? #726

Open arschles opened 5 years ago

arschles commented 5 years ago

Is your feature request related to a problem? Please describe.

We discussed in the September 27, 2018 dev meeting that folks are starting to work on Terraform configuration to deploy Athens. When this is done, the gomods/athens repository will have helm charts and terraform configuration.

Describe the solution you'd like

I wonder if we should create separate repositories inside the gomods GitHub organization to house artifacts for each different deployment/configuration system?

Describe alternatives you've considered

We could put all the deployment artifacts into the gomods/athens repository?

Additional context

We discussed this in the September 27, 2018 Athens dev meeting, and I think @timraymond mentioned the terraform configs.

ghost commented 5 years ago

I like the idea of having another repository.

Maybe something like gomods/deployments with subdirectories for each? It would be neater than having one for every option but would also require a user to clone more than they need when using the configurations.

That alternative might look like:

DrPsychick commented 1 year ago

step one is done: https://github.com/gomods/athens-charts