igorzij

14 ms·

91.
by igorzij 4y ago
Thank you!! And fair point. To us it's in a sense a bet on a particular direction the industry is going to take. If we're right then infrastructure-as-code isn't going away, someone needs to write it, even for the managed ser
92.
by igorzij 4y ago
Thanks so much for sharing the feedback!! This is super helpful, and we will work to address this.
93.
by igorzij 4y ago
That's a very good point. And it is also the very reason we wanted to build smth like this. The question we asked ourselves: why are people leaving PaaS platforms like Heroku? The answer seems to be that people are starting with simple
94.
by igorzij 4y ago
thanks!!
95.
by igorzij 4y ago
that was the intention actually but then we thought many people would use it on mobile and settled on clicks. would you prefer dnd interaction?
96.
by igorzij 4y ago
Hey HN crowd, founder here. The fact that we hit the frontpage somehow broke the new app signup flow. While we are fixing it, we are temporarily redirecting to app.digger.dev (the old UI). Will keep you posted here!
97.
by igorzij 4y ago
Same team behind it. But it's a completely new UI, much simplified and streamlined. From previous launches we learned that the UI was quite confusing, and rebuilt it from scratch. The old one can be found at app.digger.dev; this is das
98.
by igorzij 4y ago
thanks!!! that's what we thought as well :) OpsFlow automatically generates IAM roles, security groups and stuff like that. And Terraform - which you can fully customize
99.
Show HN: OpsFlow – Low-code DevOps – Webflow for infrastructure(opsflow.app)
71 points by igorzij 4y ago|37 comments
100.
by igorzij 4y ago
Almost 2 years ago my cofounder and I started building Digger. It took us a year, and last summer we have finally shown it to the world. We launched Digger quite successfully on ProductHunt as well as here on HackerNews. But it wasn’t insta
101.
Show HN: Flywheel.sh – the fastest way to build on AWS(flywheel.sh)
5 points by igorzij 4y ago|2 comments
102.
by igorzij 4y ago
oops - thanks! will fix.
103.
by igorzij 4y ago
I see your point clearly, and it's a good one. However, consider the following counterargument: the exact same thing could be said (and was said) extensively about low-level programming concepts such as registers, later pointers, memor
104.
by igorzij 4y ago
such a great point, we'll do that!
105.
by igorzij 4y ago
that's a great point indeed - we have Terragrunt support on the roadmap but didn't manage to ship yet. What kind of stuff if you don't mind sharing?
106.
by igorzij 4y ago
Oh wow it didn't occur to us to check facepalm
107.
by igorzij 4y ago
Haven't thought of that actually... Thanks!!
108.
by igorzij 4y ago
Fair point indeed. They way we built it is that it actually generates and applies Terraform in your AWS account and synchronises it with your Github. The idea is to eliminate all devops-y steps from the flow so that the user who knows nothi
109.
by igorzij 4y ago
Both - it first generates Terraform and run it on our servers to configure your AWS account (a bit like CI but for infra). And you can connect a dedicated GitHub repo for infrastructure that will get Terraform synced into. So after you make
110.
by igorzij 4y ago
The latter, yes. The former is a feature on the roadmap. Our idea is to make it as easy as possible for the user to take advantage of IaC without having to learn it. Remove the entry barrier, give a nice UI that would make it super easy to
111.
by igorzij 4y ago
This is an amazing project you have there! We have a very similar philosophy - but taking it one step further. We believe that developers do not and should not care about things like VPCs, security groups, etc. We believe that the current s
112.
by igorzij 4y ago
A database or a queue or things like Redis. S3 buckets we don't count, as well as any other stuff that you add to Terraform yourself. So you can have as many S3 buckets as you want. We haven't yet put much attention into pricing.
113.
by igorzij 4y ago
Because it actually runs the Terraform on Terragen servers to solve the state conflict problem. You can think of it like "CI for infrastructure". Or a "compiler+runtime" that outputs Terraform instead of binary / by
114.
by igorzij 4y ago
That's quite cool!
115.
by igorzij 4y ago
Yes GCP and Azure support is on the roadmap. But we're a 6-person startup so trying to narrow down, for now it AWS only
116.
by igorzij 4y ago
Thanks so much for your kind words! This means a lot to us.
117.
by igorzij 4y ago
Almost exactly a year ago we have launched Digger. Since then thousands of developers started using it, and our mission remains to build the best developer platform ever. But we are often asked - why so many products that look so similar? A
118.
Show HN: Terragen.dev – Automagically Generate Terraform for AWS(terragen.dev)
73 points by igorzij 4y ago|56 comments
119.
by igorzij 4y ago
Hi all, I'm one of the founders. Our initial product was Digger.dev - a platform that makes AWS easy by automatically generating and infra-as-code (Terraform) and managing your AWS account through it. Then we noticed that our most exci
120.
Show HN: AWSify – Move from Heroku to AWS in one click(awsify.io)
4 points by igorzij 4y ago|1 comments

More ›