1/ what were/are your goals with the projects? 2/ what are some of the biggest lessons?
would love to hear your take on 1/2 if open to sharing
31–40 of 41 posts
1/ what were/are your goals with the projects? 2/ what are some of the biggest lessons?
would love to hear your take on 1/2 if open to sharing
I’m more interested in the tech behind these products. I have a dozen or so “apps” which amount to a python script or localhost site, but deploying them online has been a complete pain in the ass. I will spend ~8 hours perfecting a python script only to spend the next weekend figuring out how to deploy it behind a url. It’s extremely frustrating. Maybe it’s because I’m not an AWS expert anymore but frankly I don’t wa…
1. Host the complete React/Vue/static site of choice on netlify
2. Host the backend on AWS. I used to use ECS+Fargate, which means you just create a docker container, open some ports, and git push, but now it's even easier with AWS AppRunner. If you didn't want to touch AWS (it gets hairy fast), I would use something like PlanetScale or CockroachDB which have generous free tiers. From there you have a github action to push your container to your AWS ECR and AppRunner automatically redeploys your app. The only other platform that I think comes close to "I have my code just host it, and make sure it's redundant" is Fly.io
I’m more interested in the tech behind these products. I have a dozen or so “apps” which amount to a python script or localhost site, but deploying them online has been a complete pain in the ass. I will spend ~8 hours perfecting a python script only to spend the next weekend figuring out how to deploy it behind a url. It’s extremely frustrating. Maybe it’s because I’m not an AWS expert anymore but frankly I don’t wa…
CapRover app deployment on Digital Ocean is very cost effective. It’s easy to deploy on a droplet using the DO scripts, and the droplets can be as cheap as you want them to be with the ability to easily scale up. If you outgrown the biggest droplet size… congratulations! You made it!
I hate to nitpick, but when the https://chunk.run/ start button is typoed "Strat Now", I have to wonder how many corners were cut to launch 9 startups in a year.
When I encounter typos like these, I assume people are just dyslexic, it’s not a question of “too many websites”. If I made 9 start-up POCs, I‘d never Strat Now. But I might Strat Eventually.
I’m more interested in the tech behind these products. I have a dozen or so “apps” which amount to a python script or localhost site, but deploying them online has been a complete pain in the ass. I will spend ~8 hours perfecting a python script only to spend the next weekend figuring out how to deploy it behind a url. It’s extremely frustrating. Maybe it’s because I’m not an AWS expert anymore but frankly I don’t wa…
Hosting is dirt cheap, fixed cost, and it's just an rsync away from being deployed.
I hate to nitpick, but when the https://chunk.run/ start button is typoed "Strat Now", I have to wonder how many corners were cut to launch 9 startups in a year.
I’m more interested in the tech behind these products. I have a dozen or so “apps” which amount to a python script or localhost site, but deploying them online has been a complete pain in the ass. I will spend ~8 hours perfecting a python script only to spend the next weekend figuring out how to deploy it behind a url. It’s extremely frustrating. Maybe it’s because I’m not an AWS expert anymore but frankly I don’t wa…
I don't think it's that hard to a learn a little bit of AWS. What my "default" is 1. Host the complete React/Vue/static site of choice on netlify 2. Host the backend on AWS. I used to use ECS+Fargate, which means you just create a docker container, open some ports, and git push, but now it's even easier with AWS AppRunner. If you didn't want to touch AWS (it gets hairy fast), I would use something like PlanetScale or…
It's a lot more complicated than anything reasonable about deploying a webapp. Any shared hosting solution or deployment platform (think fly/shuttle) will be cheaper and easier to reason about. Even selfhosting on a rented VM or dedicated server and configuring auto-updates and maintenance windows will be much easier.
By going to netlify/AWS you are now tying the destiny of your app to two megacorps, doubling the risk of downtime (and cloud uptime is certainly not as good as dedicated) and other bugs.
I’m more interested in the tech behind these products. I have a dozen or so “apps” which amount to a python script or localhost site, but deploying them online has been a complete pain in the ass. I will spend ~8 hours perfecting a python script only to spend the next weekend figuring out how to deploy it behind a url. It’s extremely frustrating. Maybe it’s because I’m not an AWS expert anymore but frankly I don’t wa…
- frontend is ReactJs/ Typescript - Auto deployed on Netlify - backend in Express/Nodejs / Typescript - Deployed on Google Cloud Run - AI is usually in python running on Compute Engine VMs - Database auth is Supabase
I master these tools and more importantly, know their limitations. This way I can spin up a new project in days without surprises
Earlier quoted context omitted.
I don't think it's that hard to a learn a little bit of AWS. What my "default" is 1. Host the complete React/Vue/static site of choice on netlify 2. Host the backend on AWS. I used to use ECS+Fargate, which means you just create a docker container, open some ports, and git push, but now it's even easier with AWS AppRunner. If you didn't want to touch AWS (it gets hairy fast), I would use something like PlanetScale or…
> I don't think it's that hard to a learn a little bit of AWS. It's a lot more complicated than anything reasonable about deploying a webapp. Any shared hosting solution or deployment platform (think fly/shuttle) will be cheaper and easier to reason about. Even selfhosting on a rented VM or dedicated server and configuring auto-updates and maintenance windows will be much easier. By going to netlify/AWS you are now t…