3 ms·
> You think we'll build anything in delphi Haah of course not! :) but doesn't mean you should flip to the other extreme and learn how to do k8 and spend a whol
by vlod 5y ago
> You think we'll build anything in delphi
Haah of course not! :) but doesn't mean you should flip to the other extreme and learn how to do k8 and spend a whole bunch of time on it.
>Interesting approach but I respectfully disagree. I built a side SaaS app that's really important to stay up 24/7.
From the get-go? Did you spend a whole bunch of time learning it or did someone else pay you? (As an employee). Most solo projects are not like this.
> I would never do this for my paying customers. I have been running a somewhat critical piece of infrastructure for about 4 years now on AWS.
Of course not, neither do I anymore. For paying customers who can afford it, AWS is a great solution. Most small timers with low traffic are happy with DO/Linode. You can be fancy and have CI/CD or webhooks of code checkin on the master branch. As a side note, back in the day, I've used Capistrano, which is pretty much the the above commands wrapped in ruby script. The OP has said he is going to use this as it's a Rails project.
However this is the crux. You're most likely having someone else pay for hosting. You're probably getting someone else to pay for you to learn how to do XYZ. Most likely you're not even aware of how much this infra is costing the client.
I really don't have a problem with this. Good for you. However the person who posted the question was a solo-founder trying to understand whether to learn Docker.
This probably is a person who is not a super techy. (A lot of people here know docker just becz of curiosity) and I would hazard a guess not a big runway. These reasons alone, IMHO I would suggest getting something out there, learning to see if there's a market and reiterating.
- intev 5y ago> k8 and spend a whole bunch of time on it. I fully agree and no one said that you should do it. But these days there's so many abstraction layers that it's not nearly as complicated as it was 2 years ago. 2 years ago I wouldn't have even considered it, but now it might be on the table. > from the get-go? Did you spend a whole bunch of time learning it or did someone else pay you? Yup. Business SaaS product that had day and night use. No investment, no one paid me. Became "ramen profitable" year 2 but it's not much. I'm not interested in growing it any more for various reasons and right now it's just "side income". > However this is the crux. You're most likely having someone else pay for hosting. You're probably getting someone else to pay for you to learn how to do XYZ. Most likely you're not even aware of how much this infra is costing the client. Might be so but not in my case. I pay for everything and customers pay me a monthly fee depending on different params that aren't even very closely tied to how much it costs me. > However the person who posted the question was a solo-founder trying to understand whether to learn Docker. When I started, I was a solo founder too. Have you looked into caprover? I came across it recently and it looks really interesting. It uses docker internally but it seems to be a somewhat mature product and has so many nice bells and whistles. Best of all, very little time investment (or so they promise). If I was restarting today, I would look into that. It would help me run everything without relying on AWS/GCP and will end up being cheaper if everything works as advertised.
- vlod 5y agoGood for you! Thanks for the reference caprover, I'll take a look.