11–20 of 21 posts
And
>2. My time - I want to spend time on value creation.
You already have your answer: stick with the stack you know and focus on value creation and serving your VIP user.
The approach here to answering your questions is to give you the easiest path towards making something. 1. Cloud hosting? No - buy the cheapest linux virtual server you can - like $5/month hosting. Cloud is most appropriate for variable compute needs (which edtech has) but you're not there yet. When you have scaling problems, solve scaling problems. Since you have a trial user at home you could build it out locally o…
It might also be a good idea to investigate some of the existing edtech offerings (canvas, moodle, blackboard etc.) and see if it makes sense to either use a similar stack (if you want to run alongside them) or do something totally different (if you want heavy AJAX interactions, for example).
What exactly are you trying to run? The ideal stack really depends on your app, it's not a one size fits all question. Often there is a tradeoff between complexity and power, for example. Or ease of use vs ease of migration. It might also be a good idea to investigate some of the existing edtech offerings (canvas, moodle, blackboard etc.) and see if it makes sense to either use a similar stack (if you want to run alo…
The approach here to answering your questions is to give you the easiest path towards making something. 1. Cloud hosting? No - buy the cheapest linux virtual server you can - like $5/month hosting. Cloud is most appropriate for variable compute needs (which edtech has) but you're not there yet. When you have scaling problems, solve scaling problems. Since you have a trial user at home you could build it out locally o…
When you say "no" to cloud hosting in the same sentence as you recommend buying a VPS in the cloud... it's odd.
“Cloud” tends to assume elasticity, pay by minute, managed software services, etc.
“On the internet” isn’t cloud automatically
Earlier quoted context omitted.
When you say "no" to cloud hosting in the same sentence as you recommend buying a VPS in the cloud... it's odd.
A VPS paid monthly isn’t “cloud”. It’s just a server. “Cloud” tends to assume elasticity, pay by minute, managed software services, etc. “On the internet” isn’t cloud automatically
Others would define a cloud server as any server that someone else owns and you don't have physical access to it.
Earlier quoted context omitted.
A VPS paid monthly isn’t “cloud”. It’s just a server. “Cloud” tends to assume elasticity, pay by minute, managed software services, etc. “On the internet” isn’t cloud automatically
I think that's a subjective interpretation. Others would define a cloud server as any server that someone else owns and you don't have physical access to it.
The main point I was making was figure out hosting later after figuring out the product/market fit.
Did not like using Django, needing to learn two DSL for templates and htmx, and a cumbersome React frontend integration.
I've found alpineJS easy to learn but a good fit for this kind of approach.
Also, use a design system. I'm finding daisy UI a good mix between ease of use without a mess of tailwind classes, but you may prefer material etc.