[HN Gopher] Show HN: DeploySolo - The SaaS boilerplate for engin...
___________________________________________________________________
Show HN: DeploySolo - The SaaS boilerplate for engineers.
(Pocketbase/ Htmx)
Golang is an incredible language for web development. That being
said, indie developers and small businesses will likely miss
extensive resources found in other projects like Django. Although
building an application from the ground up using the standard
library is possible, it can be error prone and time consuming.
Pocketbase has almost everything an indie developer needs,
supporting database, authentication, and file storage into a
single, easy-to-deploy executable. Combined with HTMX, and you can
created a full stack web application without bloated front end
frameworks. That being said, its a relatively new project, without
extensive hands on resources for new developers to dive in and
create full projects. This is why I'm building DeploySolo. On the
surface, its a SaaS boilerplate carefully crafted to leverage the
best of these technologies. Looking further, it is my mission to
create cook books and resources for indie hackers and small
businesses to build real world apps using this stack without
feeling lost.
Author : mannders
Score : 17 points
Date : 2024-03-25 14:31 UTC (8 hours ago)
(HTM) web link (deploysolo.com)
(TXT) w3m dump (deploysolo.com)
| tamimio wrote:
| Any working demo for that boilerplate?
| mannders wrote:
| I will get one up and running in the next day or two. Its
| literally as simple as getting a domain, booting up a server,
| downloading the exe, and running one command, even with HTTPS
| certificates.
|
| Thanks for the tip.
| cweagans wrote:
| Even though Pocketbase is simple to get up and running, I'd
| have a hard time dropping $50 sight unseen. There's no
| screenshots or demos or anything. I'm interested, but that's
| really what's missing to get me to commit.
|
| Hope this helps (and hope you have a demo and/or screenshots
| or something up soon!). Sounds like a really interesting
| project.
| anonzzzies wrote:
| Yep, upvote for this. As even if there is a refund within a
| week, I don't really want to do that unless I can test it.
| Onavo wrote:
| Does pocketbase support auth refresh tokens?
| mannders wrote:
| Pocketbase doesn't maintain separate refresh and access tokens.
| Credit to the discussion behind this can be found here:
| https://github.com/pocketbase/pocketbase/discussions/2154#di...
|
| This is essentially because Pocketbase commits to being a
| monolithic architecture. There's no need to pass around auth
| status to different microservices, because all relevant
| services are accessible locally.
|
| It doesn't even store the auth tokens themselves on the server,
| as the clients are expected to store and handle them, which
| eventually do expire.
|
| TL:DR, having a long lived refresh token is not more secure
| than just having a long lived auth token in the first place.
|
| The pocketbase monolithic architecture is one of the primary
| reasons I am so excited about this technology. No it isn't
| appropriate where horizontal scaling is mission critical, but
| for the indie developer projects, having more microservices
| than users is just complexity for no reason.
___________________________________________________________________
(page generated 2024-03-25 23:02 UTC)