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

Multiple regions & Historical reporting #61

Open
mrahmadt opened this issue Jul 11, 2022 · 2 comments
Open

Multiple regions & Historical reporting #61

mrahmadt opened this issue Jul 11, 2022 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@mrahmadt
Copy link
Contributor

Hello

Thank you very much for this great script, simple and can be a replacement for scraproxy

Is it possible to define multiple regions? for example, I want to have 3-5 regions with digitalocean and cloudproxy will randomly create VMs on them

my second question is there any log file or report that I can use to check how many VMs has been created, the duration, and the period? so I can compare my hosting cost let's say on weekly bases and decide which cloud provider is better for me?

@mrahmadt mrahmadt added the enhancement New feature or request label Jul 11, 2022
@claffin
Copy link
Owner

claffin commented Jul 12, 2022

Hey,

Thanks for the comment.

Multiple regions make sense. I'll look to implement in the future.

Log files/report are more complicated as this application is stateless. That data would need to be stored somewhere. I'm not sure on the best solution, a s3 bucket or a database maybe. I agree it would be useful to keep metrics and logs, but needs to be stored somewhere.

@ajtatum
Copy link

ajtatum commented May 20, 2023

Hi there, I stumbled upon this project and it looks great! Awesome work! I was just curious if this is still on the radar or if the project is considered inactive?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants