Hacker News Reader

Comment by codeptualize | Hacker News Reader

Supabase + Next.js is what I'm using.

To cover your list:

- Auth: Supabase has auth, with oauth support for many services. Also prebuild UI for login forms etc. It's really easy to set up

- Live updates: Supabase has a realtime api to send messages, or subscribe to db changes

- Database: Supabase is basically a Postgres database with a bunch of stuff on top, it generates a REST/GraphQL api from your schema, meaning you don't have to make endpoints.

It's incredibly productive as it covers all the basics. It's open source so you are not locked in, and they have a free plan that will get you quite far.

For the frontend Next.js is my preference, but you could opt for other frameworks if you are more familiar with them. Next.js on Vercel is really easy to set up with preview builds, automatic deployments etc.

View on HN

I would go for something similar.

I would try supabase + Astro.

With astro you can have more choice in frontend framework, vanilla js, alpinejs, react, svelte, vue.

I recently made a portfolio website for my girlfriend and the experience was awesome.

https://zhazira.design/

If anyone's hiring junior designers ;)

If you are building a blog or something content Astro is a great choice!

The portfolio looks great, congrats! I hope she will find a job soon, and good for you for building & promoting it ;D

While I haven't quite tried it yet. I think it is possible to also use astro with functions/lambda's to do a full blown app.

I personally really like their approach to templating and components as well as server vs client side JavaScript.

Seems very interesting. What would recommend for followings:

1) Background jobs - Something like Sidekiq for Rails.

2) Admin Dashboard - Something admin interface of Django or active-admin for Rails

3) Authorization

4) Is NextJs good for working with Websockets ?

Do you have/know any git repository which implements this stack ?

1. Depends on what you need, how long it runs, etc etc. If you just need cron/triggers, Supabase can get you quite far. If you need proper processing you might need some other service or host something yourself. We use modal.com, but there are many options.

2. Three options: use the supabase admin panel, build something yourself (or use templates), or use a 3rd party tool - many low code tools can connect to postgres and there are also some specific integrations with supabase.

3. Supabase has auth built in, with RLS you can control data access.

4. Next.js is just React when it's in the browser, so yes, it will work well. If you use the Supabase realtime with their client library it will handle all the socket connection for you.

5. Have a look at https://www.madewithsupabase.com/tag/Open%20Source it's not all next.js but there are quite a few.

Qless is a good language-agnostic queue system; its essentially a bunch of Lua that runs within your redis server(s), and then you have a client library in your language of choice (i know of at least ruby, python, nodejs and php libs for it) that calls to the Lua.

https://github.com/seomoz/qless Is the original project.

Cool! Seems very productive. Only thing I'm thinking of is reliability and the lack of control since you aren't hosting it yourself.

You could self host as it's all open source, but that would be a lot more work..

Reliability, it depends on your app and requirements. Been using them for about a year and it has been really solid, the few times I did have some issues the support was really quick and helpful. But I do see your point, it might not work for everyone.

Self-hosting Supabase is pretty hard when you consider mail set up, and all the config like setting your own domain/secrets/config without the full dashboard Supabase managed service provides, doesn't it? Aka you can't just get-up-and-go fill in a nice UI/form on an EC2 instance AMI template for Supabase...

I would assume so. Never tried it, and I hope I never have to, I use Supabase to have less work not more haha.

I still find it important that the option exists if ever needed, and maybe even more important is the ability to move away from Supabase, which some people have done successfully (see for example https://news.ycombinator.com/item?id=36004925)

Other services like Firebase make that really complicated. I quite like that portability is one of their core principles.

There are some guides and templates on self hosting https://supabase.com/docs/guides/self-hosting but it's obviously a big complicated project with lots of features. It probably also requires a bunch of work to monitor, maintain and update it once you get it running.

Reply on news.ycombinator.com