News for hackers. Stuff that matters.
Re:We are far from a better Heroku for production apps in a ... by dubcanada on Tuesday March 23, 2021 @09:31AM (#26554734)
People 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.

Re:We are far from a better Heroku for production apps in a ... by jelling on Tuesday March 23, 2021 @11:03AM (#26555877)
AWS may be the gold standard for hosting but I still recommended most startups start with Heroku for their hosting, especially since they add the code pipelines.

The amount of VC dollars I have seen wasted on re-inventing the wheel of hosting/devops is a textbook case of premature optimization.

Re:We are far from a better Heroku for production apps in a ... by ksec on Tuesday March 23, 2021 @11:38AM (#26556288)
Amazon really should have bought Heroku instead of Salesforces. I continue to wonder why Salesforce bought it in the first place. And if they are willing to unload it.
Re:We are far from a better Heroku for production apps in a ... by detaro on Tuesday March 23, 2021 @11:41AM (#26556318)
Heroku not being AWS might be a feature. I'm not sure if AWS wouldn't try and integrate them and "break" something in the process. Whereas now, they still get money from it (Heroku runs on AWS) and can offer their own "alternatives" as part of the larger AWS offering.
Re:We are far from a better Heroku for production apps in a ... by blacktriangle on Tuesday March 23, 2021 @02:42PM (#26558623)
Heroku not being AWS might be a feature, but Heroku being Salesforce is straight-up terrifying. I'm probably not moving my apps off Heroku anytime soon simply because they're running just fine maintenance free, but I'm not going to risk running any future apps on a Salesforce platform.
Re:We are far from a better Heroku for production apps in a ... by phxrsg on Tuesday March 23, 2021 @03:18PM (#26559143)
Not sure I follow this. Salesforce bought Heroku over a decade ago and Heroku is still improving in its areas of expertise, with no signs of changing that.

If anything, Salesforce has been moving more of its core developer experiences over to the Heroku model rather than trying to make Heroku more Salesforce-y.

Re:We are far from a better Heroku for production apps in a ... by macintux on Tuesday March 23, 2021 @03:40PM (#26559422)
After a short exposure to SFMC I can see why someone would be concerned about the impact they would have on Heroku, but it is good to hear there are reasons for optimism.
Re:We are far from a better Heroku for production apps in a ... by phxrsg on Tuesday March 23, 2021 @04:34PM (#26560066)
Funnily enough, SFMC was also an acquisition, and it was acquired after Heroku.

SFMC is easily the worst Salesforce project from a dev experience / integration point of view, agreed there.

Re:We are far from a better Heroku for production apps in a ... by ksec on Tuesday March 23, 2021 @11:46AM (#26556411)
The idea would be to allow Heroku working independently while offering their solution at literally AWS cost (without all the discount), or even AWS Graviton2 cost.

This would pretty much directly compete with Linode and DO on a value proposition. And a lock in to AWS ecosystem.

Re:We are far from a better Heroku for production apps in a ... by darkr on Tuesday March 23, 2021 @12:43PM (#26557063)
Heroku runs on AWS already, they're earning cost + markup as it is. If they purchased Heroku and did this, they'd be out several billion dollars plus lose their markup. Many of the Heroku addons also run on AWS, so customers may lock themselves into without knowing it. Additionally, customers are free to further lock themselves into the AWS ecosystem via "private space"/VPC peering.

And they have a competitor to Linode/DO in their Lightsail offering (though how successful it is in competition I'm not sure)

Re:We are far from a better Heroku for production apps in a ... by darkwater on Tuesday March 23, 2021 @12:53PM (#26557187)
> Heroku runs on AWS already, they're earning cost + markup as it is. If they purchased Heroku and did this, they'd be out several billion dollars plus lose their markup.

I fail to understand this. If Heroku is on AWS, Heroku is selling its services at price X. AWS is getting from Heroku Y money, where X > Y (or it should at least, if Heroku is not operating at loss). If Amazon owns Heroku it could sell its services still for X, eating Heroku's margin plus the margin it already had on the AWS offering.

Re:We are far from a better Heroku for production apps in a ... by darkr on Tuesday March 23, 2021 @02:41PM (#26558602)
> I fail to understand this

Parent was proposing that AWS sell Heroku services at cost.

As you say, my point was it doesn’t make sense

Re:We are far from a better Heroku for production apps in a ... by ksec on Wednesday March 24, 2021 @12:34AM (#26563623)
Heroku Buy AWS services at standard AWS Price (X) * (Substantial) Discount.

HeroKu Sell their services at (Y) where currently Y is >(X).

If they had acquired Heroku by Selling it at AWS Price (X), Amazon is still earning where they previously were not earning from those heavy Discount. At the expense of the Operational Cost of Heroku Team. And the benefits of further lock in and additional market segment which is currently not very well served by AWS.

Re:We are far from a better Heroku for production apps in a ... by sprite on Tuesday March 23, 2021 @01:39PM (#26557787)
Did not even know VPC peering was a thing. In the past I've often used Amazon RDS with Heroku Web servers for hosting Rails apps. For my current project I initially started out with Aurora Serverless which is VPC only, so I thought my web servers also had to be in the same VPC, so I decided to use Elastic Beanstalk instead of Heroku.

I do wish Amazon had an offering like Heroku. While Elastic Beanstalk works pretty good it's nowhere near as nice or easy to use as Heroku. It has gotten a bit better with Amazon Linux 2 [Procfile, platform hooks], but still leaves a lot to be desired. I wish I could scale up/down faster like you can with Heroku. There is probably a way to improve it, but right now the way it's set up any deploy, config change, etc bundles the gems and precompiles the assets which take a while. So deploy/scale up take around 8-10 minutes. It's been a while since I've used Heroku but from what I remember it's pretty much instant to add more dynos.

I also ran into a couple of other annoying issues with EB.

1. There is a bug if using Amazon Linux 2 Ruby 2.7 deploying a RoR app where assets are not precompiled on configuration changes. It was an easy fix, just needed to add a script to .platform/confighooks/predeploy but it should have just worked.

2. When migrating to Amazon Linux 2 I deployed a version of the app that needed some code changes to work on Amazon Linux 2. There is no way to disable rollback on failed deploy on EB. Setting the "Ignore Health Check" option to true does not help here. I ended up in a situation where I needed to both push a code update and update some environment variables. However any code update I would push would fail because of the missing environment variables and rollback and any configuration change to update the environment variables would rollback because the current code had an error. I ended up having to tear down the environment and recreate it to get out of this loop.

3. Another minor issue is the Monitoring/Health dashboard. It will show warning/degraded/severe during scaling operations. For example when you trigger a scale down event it will complain:

"Environment health has transitioned from Ok to Warning. ELB processes are not healthy on 1 out of 6 instances. ELB health is failing or not available for 1 out of 6 instances."

Like of course it's not responding, the autoscaling group just terminated it.

I feel like Elastic Beanstalk really could be a Heroku competitor if AWS cared enough to put the work into it. It just needs some polish and quality of life improvements, but I guess this way they still make their money and Heroku has a good business middle-man'ing it.

I'm wondering if perhaps I would be better off using ECS or EKS, or if that's what AWS wants me to use hence why they are not putting much effort in EB.

Re:We are far from a better Heroku for production apps in a ... by granshaw on Tuesday March 23, 2021 @12:44PM (#26557087)
In terms of the raw pieces yes but AWS UX (or lack of it) leaves a lot to be desired. It's basically – "Here! Here's the raw pieces and API – have at it!" and you have to build or bring in external tooling to use it seamlessly.

There's a product opportunity for basically every AWS service to make it usable for those who just wanna get sh*t done.

Re:We are far from a better Heroku for production apps in a ... by laurent92 on Tuesday March 23, 2021 @02:07PM (#26558159)
Yes. I have spent $4000 on consultants to set up our AWS project and it’s still not easy as “git remote add prod ssh://heroku.com/my-app”.

This “git push” is a killer feature — maybe it doesn’t really make sense security-wise or in a real architecture, but it makes it very sexy.

Re:We are far from a better Heroku for production apps in a ... by k__ on Tuesday March 23, 2021 @10:50AM (#26555727)
User experience is often laughed at or even overlooked, but this is why Firebase and Heroku are used!

I had a mainframes course in university and people from IBM would tout how everything we do today was already invented by them decades ago. But yeah, when you tried to use their stuff you had to jump through so many hoops, that you lost your motivation half the way.

Re:We are far from a better Heroku for production apps in a ... by alecbz on Tuesday March 23, 2021 @12:37PM (#26557000)
I'm often confused at how poor so many engineers' product-sense is. Especially infra engineers (speaking as one). It's one thing to not have good product-sense when you're not the user, but for products like Heroku you literally are.

My best guess is that a lot infra engineers actually value seeing the complexity and being able to understand all the pieces being used in the system more than they value getting something working quickly and easily.

Re:We are far from a better Heroku for production apps in a ... by jack_riminton on Tuesday March 23, 2021 @01:06PM (#26557338)
It must be something to do with forgetting how hard things are for novices

Reminds me of the famous old HN comment about Dropbox

Re:We are far from a better Heroku for production apps in a ... by colesantiago on Wednesday March 24, 2021 @02:58AM (#26564289)
Re:We are far from a better Heroku for production apps in a ... by ulisesrmzroche on Wednesday March 24, 2021 @01:26AM (#26563900)
That one never gets old.
Re:We are far from a better Heroku for production apps in a ... by j4yav on Tuesday March 23, 2021 @02:25PM (#26558391)
It’s from getting caught out when they’ve hidden the setting that is causing your site to be down in the name of making things easier.

I’m not saying it’s right or wrong, but that’s where it comes from.

Re:We are far from a better Heroku for production apps in a ... by stickfigure on Tuesday March 23, 2021 @01:47PM (#26557891)
People use Heroku (and Google App Engine) because - if your app fits the model, and most do - you can completely skip ops/devops. Your whole team can go to sleep without a pager. You spend your life building features that customers care about instead of mucking with config files.
Re:We are far from a better Heroku for production apps in a ... by SoreGums on Tuesday March 23, 2021 @03:55PM (#26559617)
Yes!! Being part of a large org, nobody cares about the ops bit, leadership/product/dev mgrs just want features deployed!!! It's very obvious that the sooner we can abstract all the ops away the leaner we'll be.
Re:We are far from a better Heroku for production apps in a ... by ksajadi on Tuesday March 23, 2021 @09:57AM (#26555018)
Totally agree. The ease was the reason for us as well (although now running Cloud 66).

This post seems a bit disingenuous. Gitlap + Terraform + AWS != Heroku.

Re:We are far from a better Heroku for production apps in a ... by emdowling on Tuesday March 23, 2021 @10:14AM (#26555259)
Agree with all of this. It is just such an easy environment to work in. Pipelines, team management, etc are a breeze.

When it gets too expensive, Cloud66 is a great migration path and offers the best of both worlds. It's a fairly simply transition too.

Re:We are far from a better Heroku for production apps in a ... by rgharris on Tuesday March 23, 2021 @10:21AM (#26555350)
Heroku CI, Pipelines, and Review Apps made for an awesome continuous deployment setup for me in the past.

Easy promotion of builds to staging/production after your tests pass and apps created automatically per pull request for testing in an environment just like all of your other environments.

Re:We are far from a better Heroku for production apps in a ... by gwbas1c on Tuesday March 23, 2021 @09:35AM (#26554784)
On top of that: It's very easy to create an open-source project and put a "Deploy on Heroku" button right on the Github page.
Re:We are far from a better Heroku for production apps in a ... by rcarmo on Tuesday March 23, 2021 @10:18AM (#26555304)
Yep. Heroku's workflow is why I created Piku (https://github.com/piku/piku). I wanted something dead easy for deployments and updates when iterating.
Re:We are far from a better Heroku for production apps in a ... by ctas on Tuesday March 23, 2021 @11:57AM (#26556536)
Interesting. On Dokku installing postgres and redis takes just two commands. How would the equivalent look on piku?
Re:We are far from a better Heroku for production apps in a ... by rcarmo on Tuesday March 23, 2021 @06:33PM (#26561192)
There isn't one. Piku does not concern itself with back-end stores, only apps (it was designed to run on ARM hardware, without containers and with minimal packages).
Re:We are far from a better Heroku for production apps in a ... by jack_riminton on Tuesday March 23, 2021 @10:01AM (#26555070)
"there is no CLI involved"

Well that's annoying, seeing as I've just done everything else on the CLI

Re:We are far from a better Heroku for production apps in a ... by Trasmatta on Tuesday March 23, 2021 @10:04AM (#26555115)
You can do the majority of Heroku interactions on the CLI if you prefer.
Re:We are far from a better Heroku for production apps in a ... by jack_riminton on Tuesday March 23, 2021 @10:07AM (#26555163)
I know, and I do

The quote was from the blog. Making it seem like doing things off the CLI was a plus point

Right now I have a git alias that does everything, including pushing to my heroku master, in one command. Why would I want to go off the CLI?

Re:We are far from a better Heroku for production apps in a ... by throwaway894345 on Tuesday March 23, 2021 @03:08PM (#26559005)
> You don't need a bunch of silly yml configs

The "silly yml configs" are the things I care about the most. I don't want to have to remember how to reproduce my environment in order to stamp out a new one or recover an existing one. I'm all for removing the seldom-needed complexity, but "reproducibility" is the concern around which I build my whole tech stack--I largely avoid VM-based stacks precisely because the reproducibility story is so much flakier than the reproducibility story for containers. I imagine you can use something like Terraform for Heroku, but pretending that you can ignore reproducibility altogether is... really something. Maybe the parent means that "yaml is silly" and Heroku has a better reproducibility story in some other format (maybe graphical?)?

Re:We are far from a better Heroku for production apps in a ... by lumost on Tuesday March 23, 2021 @03:14PM (#26559091)
There is a gap here in apps that (typical) developers need. There is absolutely a market for footguns that work 95% of the time as long as the developer pays some attention to it.

If you did all of the things required of launching a cloud level service for every signup page... few things would get done. There are some web apps which only need to exist for a few weeks or less before they can be tossed in a fire.

If I'm a startup with limited customer expectations of reliability and I just want to see if my friends would use my product demo... a point and click solution sounds pretty great.

Re:We are far from a better Heroku for production apps in a ... by throwaway894345 on Tuesday March 23, 2021 @03:33PM (#26559343)
Absolutely, I didn't mean to imply that there was no room for MVPs (as well as signup pages, demos, etc), but I didn't understand that the thread was limited in scope to MVPs. Is it?
Re:We are far from a better Heroku for production apps in a ... by detaro on Tuesday March 23, 2021 @03:19PM (#26559152)
they have them if you want. But you don't need them, which is the getting started quickly bonus.
Re:We are far from a better Heroku for production apps in a ... by tyingq on Tuesday March 23, 2021 @03:19PM (#26559149)
They did update just under the title...

"Update: This post does not live up to its original title We are building a better Heroku. It shows my own personal experience and reflects poorly on competitors. I am sorry about that."

Re:We are far from a better Heroku for production apps in a ... by ralph84 on Tuesday March 23, 2021 @04:51PM (#26560244)
No, it reflects poorly on GitLab. The competitor comes out looking just fine.
Re:We are far from a better Heroku for production apps in a ... by sytse on Tuesday March 23, 2021 @10:44AM (#26555645)
I fully agree, this should have been about it production app, not a development app which is already great on Heroku. Also see this post by the author https://news.ycombinator.com/item?id=26555617
Re:We are far from a better Heroku for production apps in a ... by detaro on Tuesday March 23, 2021 @11:07AM (#26555919)
What difference is the "production app" distinction supposed to make? Its not clear from neither the article nor the linked comment. If it's an attempt to suggest that Heroku isn't suitable for production use, that's going to need a lot of argument backing it up.
Re:We are far from a better Heroku for production apps in a ... by sytse on Tuesday March 23, 2021 @12:24PM (#26556842)
A production app has stateful services that retain data between deployments. The ambition of the 5 minute production app is to make this faster than doing it on Heroku.

The article doesn't make this case at all. Heroku is suitable for production and we didn't intent to suggest otherwise.

Re:We are far from a better Heroku for production apps in a ... by jrochkind1 on Tuesday March 23, 2021 @11:36PM (#26563307)
Typical heroku apps have services like postgres and redis that maintain state between deployments. This is very typical, and trivial to provision. Still not sure what you mean. Are you sure you are at all familiar with heroku?
Re:We are far from a better Heroku for production apps in a ... by sytse on Tuesday March 23, 2021 @09:41AM (#26554829)
I agree Heroku has the perfect dev environment, not much to improve there.

We’re trying to make the perfect production environment. Most people end up hosting at a hyper cloud (edit: like AWS). We’re trying to make the app on a hyper cloud in production as easy as Heroku is in development.

We’re still building that, it is t done by any means. And the article doesn’t do a good job of showing what we are trying to make easier. Setting up managed services on AWS is time consuming and that is what we want to solve. See https://gitlab.com/gitlab-org/5-minute-production-app/deploy...

The contents of the blog post doesn’t warrant the title. We regret it.

Re:We are far from a better Heroku for production apps in a ... by gjhr on Tuesday March 23, 2021 @11:29AM (#26556161)
I am not a Heroku user so cannot assess how this compares to their offering but as someone who spends ~4 hours a day looking at Terraform and the AWS console this does not look "production" quality at all.

* The web app is deployed to a single AWS EC2 instance which cannot be scaled horizontally.

* The web server is deployed from an AMI filter, when a new AMI matches this filter there will be downtime to redeploy the instance entirely.

* There does not seem to be any considerations for patching the web server.

* Everything shares a single security group. Although this is probably fine because you are using managed services for redis and postgres its still weird to allow port 443/22 from anywhere on your database.

I'd be happy to be proven wrong on these points.

There also seems to be quite a bit of assumed knowledge about AWS and Terraform. You mention the free tier a lot, but that only applies for the first year since your AWS sign up. After the free tier is up this infra is going to cost $40+ per month.

Re:We are far from a better Heroku for production apps in a ... by Trasmatta on Tuesday March 23, 2021 @09:59AM (#26555048)
It would be helpful if the post was a bit clearer on that.

FWIW, I've used Heroku as a production environment at multiple jobs. It works great there as well. The primary issue in my experience is cost. If you need to serve a lot of traffic, Heroku gets very expensive very fast. But it's still easy to use.

That cost can be offset by the fact that you may not need to hire a dedicated devops engineer right away, and your other developers spend much less time dealing with server setup and debugging.

Re:We are far from a better Heroku for production apps in a ... by sytse on Tuesday March 23, 2021 @10:05AM (#26555126)
I agree the blog post isn’t clear on that.

I agree a simple production app can be great on Heroku. However besides being costly it is also hard when you want a managed service that isn’t on the platform. There are other reasons, https://gitlab.com/gitlab-org/5-minute-production-app/deploy... lists 9 in total.

While a production app on Heroku isn’t hard it isn’t trivial either. We’re trying to make the 5 minute production app faster to set up than Heroku for production apps by automatically configuring a bunch of services. We’re not there yet but that is the goal.

Re:We are far from a better Heroku for production apps in a ... by edoceo on Tuesday March 23, 2021 @10:29AM (#26555447)
We hear you. But it looks like you're losing focus.
Re:We are far from a better Heroku for production apps in a ... by llbeansandrice on Tuesday March 23, 2021 @12:38PM (#26557013)
> Hypercloud

Why list all of these reasons and then make no use of them in the infrastructure code? The code doesn't scale, has huge downtime, you recommend granting Admin access to the CI jobs, the free tier is only for the first year the account exists. The purpose and focus of this repo isn't clear to me at all.

Re:We are far from a better Heroku for production apps in a ... by llbeansandrice on Tuesday March 23, 2021 @12:35PM (#26556963)
> See https://gitlab.com/gitlab-org/5-minute-production-app/deploy...

This code is awful.

> Terraform which has the following advanatges: > 1. Terraform is the most popular

What an awful reason to pick a technology. I love TF but using something because it's popular is the worst reason ever. Why even include this as a reason? None of the others are particularly compelling for a "5-minute" setup either.

> 5. You avoid the cost and complexity of Kubernetes

But k8s is popular so why not use that?

>If you are not sure what correct permissions are then use AdministratorAccess as a temporay solution.

Aside from all of the spelling errors in the README I hate this advice. You have the infrastructure code, you know what's going to be provisioned. Create an IAM policy and add it to the code or README. Telling people to give their little app Admin access is a terrible idea.

In addition to all of the issues another commenter mentioned. This is hardly "production" quality code or infrastructure. Production should be able to scale, that's the entire point of using HyperCloud providers.

Re:We are far from a better Heroku for production apps in a ... by throwaway823882 on Tuesday March 23, 2021 @02:41PM (#26558603)
> I love TF but using something because it's popular is the worst reason ever. Why even include this as a reason?

They don't really mean "because it's popular", they mean because it's the industry incumbent and de-facto standard. You can't use anything else, because nothing else makes sense.

You need to standardize on one tool, especially if your infrastructure / teams grow. If you want to deploy something on AWS using an API with a minimal graph of dependencies, there's just Terraform. Pulumi isn't totally free, you have to write more code, there aren't nearly as many providers, not as many people know it, etc. There's basically nothing else. As a result, it's "popular".

Re:We are far from a better Heroku for production apps in a ... by capableweb on Tuesday March 23, 2021 @09:45AM (#26554866)
What does "hyper cloud" mean in this context? Searching only shows a headset with the name "HyperX Cloud" but I'm sure that's not what you are referring to.
Re:We are far from a better Heroku for production apps in a ... by boleary-gl on Tuesday March 23, 2021 @09:46AM (#26554879)
In this context "Hyper Cloud" means one of the major cloud vendors - AWS, GCP, Azure.
Re:We are far from a better Heroku for production apps in a ... by parasubvert on Tuesday March 23, 2021 @09:48AM (#26554900)
Hyperscaler = Google, Amazon, Microsoft, Alicloud
Re:We are far from a better Heroku for production apps in a ... by sytse on Tuesday March 23, 2021 @09:49AM (#26554925)
In the West it means AWS, Azure, or GCP. See https://gitlab.com/gitlab-org/5-minute-production-app/deploy...
Re:We are far from a better Heroku for production apps in a ... by jrochkind1 on Tuesday March 23, 2021 @01:46PM (#26557877)
What are you saying is lacking in heroku's production environment?

"Setting up managed services on AWS is time consuming and that's what we want to solve."

Right, that's exactly what heroku has solved. Are you saying you don't think heroku has solved it as well as you have or you can?

> The contents of the blog post doesn’t warrant the title. We regret it.

OK, what SHOULD the title be, what's it actually about? Trying to build a heroku competitor?

Re:We are far from a better Heroku for production apps in a ... by fnomnom on Tuesday March 23, 2021 @09:55AM (#26554984)
but isnt that what AWS does with elastic beanstalk? elastic beanstalk always seemed to me as a "heroku with more dials"
Re:We are far from a better Heroku for production apps in a ... by runako on Tuesday March 23, 2021 @11:06AM (#26555903)
Oh my goodness, no. Beanstalk is a very poor clone of Heroku.

Context: I have used Elastic Beanstalk in real production apps for years. For my Rails side project, figured I would use Beanstalk instead of Heroku so that I'm using the same platform (although I have also used Heroku in prod settings).

Quick summary is the AWS tutorial for launching their Rails sample app in Elastic Beanstalk doesn't work at all. I though maybe my Rails install was borked somehow, so I tried launching a sample app at Heroku. Worked on the first try.

Heroku really spends time making sure everything works out of the box, and that's what you're paying for.

Re:We are far from a better Heroku for production apps in a ... by wussboy on Tuesday March 23, 2021 @02:40PM (#26558581)
I've never tried Heroku, but I have tried EB on a number of occasions and never had anything but grief with it. Often takes me days to get something deployed.

And the next time I do it, it's like it's all brand new. It never gets easier.

Re:We are far from a better Heroku for production apps in a ... by boleary-gl on Tuesday March 23, 2021 @09:59AM (#26555045)
I think that lots of the clouds will have their own offering, but having an open source based offering across clouds is what we're going for.

Also it's very early stages - but the goal would to be better than Beanstalk

Re:We are far from a better Heroku for production apps in a ... by rad_gruchalski on Tuesday March 23, 2021 @10:51AM (#26555737)
As long as it is faster than gitlab itself, sure. Every time I go to the hosted gitlab, I cringe. I like the product but the whole thing is sooo slow. First, 5 seconds wasted to "check if my browser supports gitlab", then the lag on every click. Hopefully your heroku will have a better experience than your gitlab.
Re:We are far from a better Heroku for production apps in a ... by brodock on Tuesday March 23, 2021 @09:29PM (#26562484)
Isn't that "5 seconds" a cloudflare thing?
Re:We are far from a better Heroku for production apps in a ... by rad_gruchalski on Saturday March 27, 2021 @06:14PM (#26606100)
Why should I care? I click sign in button, which takes me to https://gitlab.com/users/sign_in and I see the message. Who cares where it comes from.