3 ms·

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,

by sytse 6y ago

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-template https://gitlab.com/gitlab-org/5-minute-production-app/deploy...

throwaway883248 6y ago
I'm sorry but this is just a joke. It takes a while to configure a database, redis and storage on Heroku? This reads as someone who has never used Heroku.
- jack_riminton 6y ago
  lol its literally a couple of quite memorable CLI commands
  - jrochkind1 6y ago
    Or a couple clicks in the web GUI if you prefer.
tomd 6y ago
> It takes a while to configure a persistent database, redis, and storage on Heroku Really? Have you actually tried this? In my experience Heroku couldn't make it any easier. You can provision a database in 60 seconds, from a Deploy to Heroku button in your Github README, or in the lovely dashboard, or on the CLI, or with two lines in heroku.yml. We're a heavy Gitlab user and I'm a big fan of Gitlab's typically transparent communications style, but this article reflects really badly on you. I think you should take it down.
funnygitlab 6y ago
I have been following these gitlab promotion threads here at HN and I dont usually comment, but I had to create this account after reading this post. It looks really bad and incompetent when a CEO of the company makes a statement like this. Have you ever used Heroku? On what basis are you allowing people to bash that product on your website? Do you consider Heroku your competitor? On what technical abilities of Gitlab do you think you have reached a place where you consider them your competitor? Some random meaningless doc someone put together to show how you will do better?
jrochkind1 6y ago
I don't know what you mean. It's literally one click to configure a persistent database and redis on heroku. It's true that "persistent storage" can get more complicated, depending on what you mean, partially because that phrase encompasses a variety of different things for different needs. I don't see how you could possibly make this easier. You could make it cheaper, and possibly "transportable to a differnet vendor" (even a non-AWS vendor), which is what some people are chasing. To do this while being as easy as heroku is the holy grail. (not easier but as easy because configuring a persistent db or redis is already at the literal maximum of easiness on heroku). But you think you can make configuring a persistent database easier than heroku? I honestly have no idea what you are thinking of when you say this "takes a while to do" on heroku. Are we talking about the same heroku?

by sytse 6y ago

throwaway883248 6y ago

I'm sorry but this is just a joke. It takes a while to configure a database, redis and storage on Heroku? This reads as someone who has never used Heroku.

jack_riminton 6y ago
lol its literally a couple of quite memorable CLI commands
- jrochkind1 6y ago
  Or a couple clicks in the web GUI if you prefer.

tomd 6y ago

> It takes a while to configure a persistent database, redis, and storage on Heroku Really? Have you actually tried this? In my experience Heroku couldn't make it any easier. You can provision a database in 60 seconds, from a Deploy to Heroku button in your Github README, or in the lovely dashboard, or on the CLI, or with two lines in heroku.yml. We're a heavy Gitlab user and I'm a big fan of Gitlab's typically transparent communications style, but this article reflects really badly on you. I think you should take it down.

funnygitlab 6y ago

I have been following these gitlab promotion threads here at HN and I dont usually comment, but I had to create this account after reading this post. It looks really bad and incompetent when a CEO of the company makes a statement like this. Have you ever used Heroku? On what basis are you allowing people to bash that product on your website? Do you consider Heroku your competitor? On what technical abilities of Gitlab do you think you have reached a place where you consider them your competitor? Some random meaningless doc someone put together to show how you will do better?

jrochkind1 6y ago

I don't know what you mean. It's literally one click to configure a persistent database and redis on heroku. It's true that "persistent storage" can get more complicated, depending on what you mean, partially because that phrase encompasses a variety of different things for different needs. I don't see how you could possibly make this easier. You could make it cheaper, and possibly "transportable to a differnet vendor" (even a non-AWS vendor), which is what some people are chasing. To do this while being as easy as heroku is the holy grail. (not easier but as easy because configuring a persistent db or redis is already at the literal maximum of easiness on heroku). But you think you can make configuring a persistent database easier than heroku? I honestly have no idea what you are thinking of when you say this "takes a while to do" on heroku. Are we talking about the same heroku?