New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a demo / testing deployment #1497
Comments
We have the funds, so hosting on DO/GCP/AWS/Linode/Hetzner/some other provider is probably the way to go. Just need to finalise the spending policy (though infra spending is very uncontroversial) |
We actually do not require the container images to exist in order to maker this work. Using the ansible role for libretime would also make it work smoothly ! |
Should we have a dedicated repository for the testing/demo deployment files or should we use the main repository ? |
This requires a few subdomains too, I would go for |
@hairmare will need to organise that |
Probably a new repo that has a deployment pipeline triggered by commits to this repo |
Sorry to bother @hairmare, but we really need you on this one. |
@paddatrapper We could buy |
Yeah, happy to do that |
Funding request for the infrastructure to do this: libretime/organization#8 |
Let's annoy @hairmare some more and see if we can get in touch though twitter. |
That makes sense :) As noted in libretime/organization#7 i'm trying to get you a zone transfer and will update asap once i have one. If you already know the records for |
This issue has been automatically marked as stale because it has not had activity in the last 5 months. It will be closed if no activity occurs in the next month. |
In order to have direct feedback of the current state of the code living in master, I propose that we continuously build and deploy Libretime on a demo / testing deployment.
In my opinion this would require the project to have:
The question is who can host this ? Do we want to put money in a Linode/Digital Ocean/Hetzner/[insert any other provider...] to run this ?
The text was updated successfully, but these errors were encountered: