Looks like an enticing solution to the age old problem! Great work guys
Launch HN: Release (YC W20) – Staging environments made easy
61–66 of 66 posts
Re: Launch HN: Release (YC W20) – Staging environments made easy
#62I may be at a place where this would be useful, so I signed up! That being said... At this point, one-click (or one command or one PR open) pre-production environments are almost table stakes for PaaS offerings. This kind of functionality was the primary reason we moved from self-hosted to PaaS (Pantheon) back in 2012/13 at a prior gig. Heroku (as mentioned in other comments) offers similar functionality these days.…
Many PaaS offerings do some version of this, but we're targeting companies who aren't using PaaS. Specifically companies that are in AWS natively (other could providers coming soon). The reason for this is they are the ones who tend to need to build this from scratch and the market for companies in the cloud is... well... huge. They tend to want PaaS features but have to build it themselves. That's where we are heade…
Thanks for the detailed response! It all makes sense, and it sounds like y'all are getting good advice.
My gut take on docker vs. config management came from the trend of IaaS providers moving higher up the chain in the services they offer (it ain't just compute anymore). So spinning up an ephemeral environment that also, for example, had its own SQS instance, or an Aurora DB, or (across clouds) had a Firebase DB or Cloud Scheduler configuration, seems like a very common use-case.
Gotta start somewhere though, and docker's probably a good place to do so.
Looking forward to trying it out!
Re: Launch HN: Release (YC W20) – Staging environments made easy
#63Been there done that. I would take a different route. I will start with one application and make it easy for a developer to install and run it on their computer, ideally with some dummy data. Price it as free to use, you will get tones of users. These users will need a way to get these local applications to a staging and to a production servers. Thats where you charge money and you control the entire cycle. Pulling a…
This is brilliant suggestion. After visiting Release's site, I clicked pricing and saw $500/month for what I'd consider playground environment and my instant thought was "nope, another tool I won't use, no chance I'm paying $500 only to speak to sales later in order to agree about more money". However, if I were charged when trying to make production work - that's something I'd pay for, if it's an application that he…
Thanks for the comment, I totally understand what you're saying. We need to do a better job of explaining that we can run production environments as well as staging. In fact, Release runs on Release.
Re: Launch HN: Release (YC W20) – Staging environments made easy
#64[deleted]
Re: Launch HN: Release (YC W20) – Staging environments made easy
#65The website is really slow. You got images which are 3700px in width and 1.2mb large on the landing page. You should resize them to the width you really need, probably 1000px in width max. Use .png for images which are transparent and .jpg for images which are not. Also don't forget to compress them. Google Chromes Lighthouse shows an optimization of 16seconds on 4G mobile by resizing/compressing images alone.
Re: Launch HN: Release (YC W20) – Staging environments made easy
#66I worked multiple years in an organization led by the founding team. Just dropping a note to say that the team is top-notch, and they are maniacal about listening to customer feedback.
They advocated for and implemented a strikingly similar product within the organization, and it was used for all deployments: development, test, staging, production, etc. The system was a crucial aspect of everyday development and extraordinarily helpful for working with cross-functional partners.