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

Support for Linode #59

Closed
Raekye opened this issue Nov 14, 2016 · 2 comments
Closed

Support for Linode #59

Raekye opened this issue Nov 14, 2016 · 2 comments

Comments

@Raekye
Copy link
Member

Raekye commented Nov 14, 2016

Linode doubled their server sizes, seems about time to add support for other providers :P

@ajusa
Copy link

ajusa commented Jan 28, 2018

Hey Raekye, glad to see that you are (at least somewhat) back!

I think that adding support to Vultr might be better than Linode at this point. Vultr is slightly cheaper by the hour (I think), and it has 5gb more storage.

Based on their website, they also look like a DigitalOcean clone, but I haven't seen their API yet. If the API is also very similar, it shouldn't be too hard to add support to it.

EDIT: I didn't realize that DO just updated their droplet size. DO is now cheaper than Linode and Vultr, so you should probably stick with it for now.

@Raekye
Copy link
Member Author

Raekye commented Feb 19, 2018

Hi Ajusa, yeah based on the history of considering new backends (but never getting to it), and as you said DO doubling their sizes, I think it's best to stick to 1 thing that works. Already had a fiasco where DO removed old images and Gamocosm stopped working for almost a month 😅 I'm actually hoping to revisit soon to see if the Gamocosm background workers could be improved to be more stable/trackable. For triaging purposes, I'll close these issue for now

@Raekye Raekye closed this as completed Feb 19, 2018
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

No branches or pull requests

2 participants