mannders's comments

I built BSocial as an attempt to create an online space which encourages the ranking and discussion of topics related to a business sector.

To reduce spam, posts require a small fee from an Ethereum wallet. This also means you own your posts.

I would love to see this become a better home page to scroll. Just high impact information and discussion, without the distractions.

IMO AI was extremely important, but the breakthroughs are mostly done. I’m just expecting incremental improvements with LLMs now.

A Turing complete personal tutor to explain any concept already exists. You can prompt a logo or video into existence. This is crazy.

The real value will be the creative people who use AI to self teach and build real world value, like energy management, or anything else.

Not this pipe dream that AGI will be achieved and automate the entire world, which for some reason gets so much focus. Seems like procrastination to obsess over this.

There’s a fine line between validating an early MVP by verifying whether users will pay, and scamming users. An entrepreneur acting in good faith would ideally take this strong positive signal, listen to their initial users feedback, and iterate towards something better.

A natural consequence of the currently low barrier for developers to ship a whole product indie, is that you’ll see more low value projects online. I can understand how that’s annoying.

But when one strikes gold and creates real value, I think it’s pretty cool how it’s ran by an individual who truly cares and understands the target user and problem.

I prefer that to an over funded VC project that gets dissolved, or a Google project that gets EOL from layoffs.

Hey there, your feedback is extremely valuable, thank you.

I wanted to get an appealing MVP to launch, to see if there's any interest. Since there is some, I'll prioritized getting a more organized and polished component list. Also forgot -webkit-backdrop-filter, oops.

I did make the cmd+k shortcut the doc search modal, so you can try that if you'd like. Its also a cool htmx demo against an EC2 Go net/http server.

Yes this was massively inspired by shadcn and his great work. I'll make sure that's better communicated in the site. And the MIT License.

I wanted to use shadcn/ui for a project, but I wasn't using React. I thought that was a shame, so I built one for my preferred stack, Bootstrap+net/http+html/template+htmx.

So its fundamentally a different architecture better suited for template based web applications. Like Django or Rails or Go html/template. It serves a completely disjoint market.

Thanks a lot for this understanding response, I'm still pretty new to this.

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.

This is in addition to the educational content I'm going to be creating around this topic. While building DeploySolo, I spent 50% of my time reading source code and 50% in GitHub discussions.

Its a skill that engineers should develop to be comfortable with these resources.

But having tutorials and cookbooks that help achieve a user's specific goal is extremely helpful for the new engineer or the time conscious one.

I attribute a lot of Django/Laravel's popularity to these resources, that are currently missing in the Go/Pocketbase ecosystem.

I'm just building in public. I don't think there's any hacks.

I would say that making a python-cookiecutter template would just be a different delivery method for the same underlying value.

The underlying value of DeploySolo is that it is a complete SaaS template integrating a unique combination of tech that I haven't seen before in a complete package yet.

It comes out of the box integrated with:

1. Auth cookie storage with vanilla js (avoiding front end frameworks)

2. Stripe webhooks setup so you only have to generate product IDs and secrets, and simply place it in the code.

3. UI elements/pages from tailwind, serving as a minimal foundation for your own tailwind styles.

4. An extremely sane and pleasant templating system using Go's html/template. You can effectively reuse html fragments as components, but output simple pages. If you need dynamic interactivity, htmx fits into this beautifully.

Of course its possible to set up all these things yourself, but all in it took me two months of early mornings.

If you're a busy adult, starting with a complete package like this could be the difference between success and never launching at all, weighed down by complexity.

Live demo has been put with a button on the front page. Thanks for the feedback!

https://deploysolodemo.com/

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.

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.

DeploySolo is the SaaS boilerplate for engineers. It enables individual developers to quickly validate ideas and deploy with ease, all while building high value engineering skills and maintaining full project autonomy.