|
|
|
|
|
by mannders
818 days ago
|
|
Simply put, I found deploying a Django app on an EC2 instance to be a huge pain. Getting letsencrypt certs through nginx, setting up routes to a unix socket, choosing between WSGI and ASGI. Docker compose can help orchestrate these processes more easily, but its still a non-trivial amount of complexity. This isn't a documentation problem, but a personal distaste for the architecture. This is the problem your first quote actually solves. I didn't fabricate a fake problem, I felt a real one. Deploying a pocketbase application is as simple as getting a binary on a server with a HTTPS configured firewall, and giving it a domain name. I launched both deploysolo.com and deploysolodemo.com in a tmux instance, which isn't a great permanent solution, but a testament to ease of deployment for a market validation phase. The "for engineers" generally comes from the fact that many web software engineers enjoy the Go ecosystem, and they can take a lot of their expertise creating HTTP routes into a SaaS boilerplate that solves common problems out of the box. Reinventing the wheel sucks when you have a business idea to get out into the world. Anyway truly thank you for the feedback, I'm still learning and not trying to use grandiose language to extract money. I'm just trying my best to create something that helps people create their own value. |
|