-
Notifications
You must be signed in to change notification settings - Fork 87
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
🧱 Better infrastructure #1413
Comments
Platform.shThe OSM Welcome Tool is developed using Symfony and Platform.sh is the hosting platform "linked" to Symfony: https://symfony.com/cloud/
InfrastructureProvides all necessary features: app, PostgreSQL, queue/worker, cron job, ... You don't seem to be have control on the hosting provider, this is handled for you based onnthe region you choose ; available regions (and providers): https://docs.platform.sh/development/regions.html PricingI can't immediately figure out how much it would cost us but I'm guessing something around 30 USD/month. Laravel ForgeInfrastructureProvides all necessary features: app, PostgreSQL, queue/worker, cron job, ... You seem to be able to choose your hosting provider (which requires an account in that/those provider(s) ; providers: DigitalOcean, Akamai, Vultr, Amazon, Hetzner, ... Pricinghttps://forge.laravel.com/#pricing
Seems to NOT include server cost from provider (see above). Laravel VaporInfrastructureProvides all necessary features: app, PostgreSQL, queue/worker, cron job, ... Provider: Amazon Pricing39 USD/month + AWS usage cost (pay-as-you go) |
If we go for Laravel Forge or Vapor, might be worth migrating from Symfony to Laravel. |
I’m here cos @joostschouppe mentioned this to the local chapters & communities working group. I’m very out of touch regarding modern PHP frameworks but it looks like you have a docker container so if that’s up to date then I wonder whether you’ve considered using a cloud provider (eg Amazon) and hosting via the container (eg https://aws.amazon.com/getting-started/hands-on/deploy-docker-containers/ ). Afaik all cloud providers offer somekind of docker/container option. I think it should end up a bit cheaper but I appreciate it would be more/differently complex to get up and running in the first place. |
I have quite some experience with hosting docker containers using Hetzner Cloud (https://www.hetzner.com/cloud/), probably even cheaper compared to Amazon and should be stable enough for this usecase. We host all our company stuff like that. I would be willing to try this with @jbelien if he thinks this is a good enough option. But it's up to him, I also am very out of touch with PHP. |
Thank you both! Docker containerization was indeed a plan I had a while back (see #766). I'm still convinced that Docker could be an option but looking at the time I could invest in this these last few months, I'm looking now for a "fully managed" solution. I'm currently running tests on Plaform.sh and Laravel Forge that look promising (basically push update to main branch and wait for redeploy).
I'm close to have a version of the app running on Platform.sh. I'll keep you updated. |
Test on Platform.shhttps://2-x-rai4ihq-b62c5e7ddypzg.fr-3.platformsh.site/ Daily automated update setup for Belgium, Berlin, and Brazil as test. Test 1: Belgium + Brazil ✅ |
Hello, I logged in to the website but the website is giving me an error. I'm from Brazil and I started using this tool on the origin server and used it to invite new members of the community but it was no longer updated. |
@raphaelpe Ah yes, I also get an error... Most likely due to a dependency upgrade. I'll have a look 👍 |
Issue is fixed in 102a13b |
Since yesterday evening, https://welcome.osm.be/ is pointing to the new instance. I'll copy the "historical" data from the previous instance to the new one in the next few days. |
I've refactored the process (see adacee1) and it uses way less memory. |
Seems to work fine! 🎉 I've tried to restore the data from the "old" Welcome Tool. |
Yes, this project is still maintained!
The current issue is that our (OpenStreetMap Belgium) server and the infrastructure (SQLite) worked perfectly fine for a few region but is undersized for the number of regions we have now!
I gave it some thought and here are a few suggestions/ideas:
We could also rewrite the whole application using other language(s) but that would require too much work.
You're more than welcome to contribute to this discussion if you have experience with one of those solutions.
The text was updated successfully, but these errors were encountered: