Skip to content
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

Open
jooola opened this issue Jan 8, 2022 · 13 comments
Open

Create a demo / testing deployment #1497

jooola opened this issue Jan 8, 2022 · 13 comments
Assignees
Labels
is: feature-request is: proposal status: pinned This issue or pull request won't stale

Comments

@jooola
Copy link
Contributor

jooola commented Jan 8, 2022

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:

  • container images for each app, so we build and the host simply auto update the images,
  • sample data that can be inserted in the stack if a big failure occur, and we need to reset the stack,
  • a shared dashboard where we can graph, explore the logs and metrics of that stack (I am thinking about grafana + loki + prometheus).

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 ?

@paddatrapper
Copy link
Contributor

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)

@jooola
Copy link
Contributor Author

jooola commented Jan 12, 2022

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 !

@jooola
Copy link
Contributor Author

jooola commented Apr 14, 2022

Should we have a dedicated repository for the testing/demo deployment files or should we use the main repository ?

@jooola
Copy link
Contributor Author

jooola commented Apr 18, 2022

This requires a few subdomains too, I would go for demo.libretime.org and maybe (ubuntu|debian).testing.libretime.org

@paddatrapper
Copy link
Contributor

@hairmare will need to organise that

@paddatrapper
Copy link
Contributor

Probably a new repo that has a deployment pipeline triggered by commits to this repo

@jooola jooola self-assigned this Apr 25, 2022
@jooola
Copy link
Contributor Author

jooola commented May 5, 2022

Sorry to bother @hairmare, but we really need you on this one.

@jooola
Copy link
Contributor Author

jooola commented Jun 5, 2022

@paddatrapper We could buy libretime.dev and use that instead of libretime.org, and only keep libretime.org for public facing urls ?

image

@paddatrapper
Copy link
Contributor

Yeah, happy to do that

@paddatrapper
Copy link
Contributor

Funding request for the infrastructure to do this: libretime/organization#8

@jooola
Copy link
Contributor Author

jooola commented Jun 6, 2022

Yeah, happy to do that

Let's annoy @hairmare some more and see if we can get in touch though twitter.

@hairmare
Copy link
Member

hairmare commented Jun 6, 2022

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 demo. and the *.testing. domains i'll happily set up as soon as i can find a browser that still works with the DS admin currently in use.

@github-actions
Copy link

github-actions bot commented Mar 4, 2023

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.
Please chat to us on the forum or ask for help on our chat if you have any questions or need further support with getting this issue resolved.
You may also label an issue as pinned if you would like to make sure that it does not get closed by this bot.

@github-actions github-actions bot added the status: stalled This issue or pull request is stalled label Mar 4, 2023
@jooola jooola added status: pinned This issue or pull request won't stale and removed status: stalled This issue or pull request is stalled labels Mar 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
is: feature-request is: proposal status: pinned This issue or pull request won't stale
Projects
None yet
Development

No branches or pull requests

3 participants