We are far from a better Heroku for production apps in a hyper cloud
1–10 of 275 posts
Re: We are far from a better Heroku for production apps in a hyper cloud
#2I feel like Gitlab is going in a direction of AWS, except that instead of having separate products it just bundles everything in one. One massive bloatware that's scary to touch, no idea where features begin or end, or what is it even for in the end. Everything? I thought it was supposed to be Git hosting, but I'm not even sure anymore.
Re: We are far from a better Heroku for production apps in a hyper cloud
#3> The Git URL unfortunately does not provide access.
Sorry to say but not having a git web UI doesn't mean you can't access it. The very next command you push to it via `git push heroku main`, meaning you have full access to it, including the ability to force push to it.
Re: We are far from a better Heroku for production apps in a hyper cloud
#4This was a confusing read. I guess GitLab has a hosting service, or does it? Or was this a demo of terraform?
Re: We are far from a better Heroku for production apps in a hyper cloud
#5> The Git URL unfortunately does not provide access. Sorry to say but not having a git web UI doesn't mean you can't access it. The very next command you push to it via `git push heroku main`, meaning you have full access to it, including the ability to force push to it.
Puzzling from someone working for a git platform. Or maybe fitting?
Re: We are far from a better Heroku for production apps in a hyper cloud
#6> The Git URL unfortunately does not provide access. Sorry to say but not having a git web UI doesn't mean you can't access it. The very next command you push to it via `git push heroku main`, meaning you have full access to it, including the ability to force push to it.
Yeah, I think it would have been better to differentiate in the article based on setting up state.
It takes a while to configure a persistent database, redis, and storage on Heroku. That is what we’re trying to make easier, as well as hosting it on a hyper cloud.
See https://gitlab.com/gitlab-org/5-minute-production-app/deploy...
Re: We are far from a better Heroku for production apps in a hyper cloud
#7I feel like Gitlab is going in a direction of AWS, except that instead of having separate products it just bundles everything in one. One massive bloatware that's scary to touch, no idea where features begin or end, or what is it even for in the end. Everything? I thought it was supposed to be Git hosting, but I'm not even sure anymore.
In this case I think it is more an ecosystem of build and deploy scripts that use the tools GitLab already provides (gitlab pipelines, terraform, etc.). GitLab is not providing the server space, instead you provide credentials to any supported cloud space and GitLab pipelines deploy the application.
Re: We are far from a better Heroku for production apps in a hyper cloud
#8> A typical web app requires a database, storage or caching backend, which can get complicated to run with Heroku.
Plainly wrong. Easiest thing ever to spin a pg instance for free and have it immediately available for your app to use.
Better Heroku? Does it let you use a pipeline of dev, staging and prod? Does it auto create new copies of your app (db and other services included!) every time you issue a pull request? Does it destroy those apps/services when you merge to master? Does it let you push to prod with one button? Integrated logs viewable on the web ui? Hell, integrated bash to a copy of your app in the web ui? Oh I forgot testing... webhooks... access control for other devs...
Better Heroku. Pathetic
Re: We are far from a better Heroku for production apps in a hyper cloud
#9This was a confusing read. I guess GitLab has a hosting service, or does it? Or was this a demo of terraform?
The 5 minute production app is a fancy GitLab CI script that uses Terraform to provision managed services.
The goal is to “quickly make a stateful app that is deployed on a hypercloud” https://gitlab.com/gitlab-org/5-minute-production-app/deploy...
Re: We are far from a better Heroku for production apps in a hyper cloud
#10People do not use Heroku because it takes 5 minutes to spin up a box. They use it because it's super easy.
Click a button, bam deployed. Want to add a database, click what database you want, bam you got a database, environment variables set and a GUI (depending on what you pick). Want to scale up? Click a button, you're now scaled up. Want a entire review system with staging links and everything? Setup the review process line and you're done.
Everything is beyond easy and requires very little actual knowledge. You don't need a bunch of silly yml configs or knowledge of how containers work. You just pick a button and setup your git repo and it deploys your app. Want to SSH in? Install the CLI tools and type heroku ps:exec, want to see the logs? Go to the logs error to type heroku logs.
They have a perfect dev environment, fairly decent CLI tooling, bulletproof battle tested deployment setup (minus they fact they go down basically every 2 days if you aren't on the paid plans), and very little you need to understand.