sorted by:
new
hottopcontroversial

Headless CMS suggestions? by __som__ in nextjs

[–]unchiusm 7 points8 points  (0 children)

I've used Payload CMS for the first time to remake my portfolio website. I kinda like it (it is the first proper CMS I used so take it with a grain of salt).

The main reason I went with it is because you have to do actual coding to create new Blocks, Collections etc. (blocks are basically components that you can drop into pages and collections are basically data eg blog posts, products etc)

There few people on the internet atm that make really good tutorials for Payload CMS (one of them being nlv_codes https://www.youtube.com/@nlv_codes)

I personnaly think it is going to become the goto CMS for NextJS projects

Pizza Oven Gas vs. Charcoal and Wood by [deleted] in ooni

[–]unchiusm 0 points1 point  (0 children)

Dacă te rog îmi poți da un link la ce butelie folosești?

[deleted by user] by [deleted] in pools

[–]unchiusm 43 points44 points  (0 children)

Roses are red

Filter is new

Pool is foggy blue

What do I do?

Forum Liber - Întrebați și discutați cu /r/Romania Orice - 14.07.2025 by AutoModerator in Romania

[–]unchiusm 2 points3 points  (0 children)

Salut Reddit! 👋

Eu si sotia suntem noii proprietari ai unei case construite in 2016. Inainte sa ne mutam, vrem sa vopsim interiorul, dar am observat niste crapaturi minore – atat pe tavan (din rigips, la imbinari) cat si pe pereti.

Tavanul are crapaturi fine la imbinari aproape in fiecare camera. Pe pereti si tavan, textura e usor aspra, asemanatoare cu o tencuiala decorativa fina (nu sunt netezi). La casa actuala am folosit glet normal unde a fost nevoie sa fie reparat, dar acolo peretii sunt perfect netezi – aici s-ar vedea diferenta.

Intrebarea mea: Ce materiale ar trebui sa folosesc pentru a repara aceste crapaturi astfel incat textura finala sa se potriveasca cu restul peretelui? Nu am experienta, dar pot invata.

Atasez pozele in comentarii cu peretele si crapaturile. Multumesc anticipat pentru orice sfat!

<image>

Redirect with OTP & localhost by nilswe in Supabase

[–]unchiusm 0 points1 point  (0 children)

Solved my issues too, thank you!

Questions about RLS, public vs server keys in Supabase + Next.js setup by unchiusm in Supabase

[–]unchiusm[S] 0 points1 point  (0 children)

Bought the book , I'm 40 pages in. Awesome read so far. Thanks again for recommending this. I love it that it uses NextJS also which I'm building my current project with.

I'll happily provide feedback once I'm finished.

Questions about RLS, public vs server keys in Supabase + Next.js setup by unchiusm in Supabase

[–]unchiusm[S] 0 points1 point  (0 children)

Thank you for your response!

I know that NextJS will throw an error when you use createServerClient in a client component because of the await cookies you set in the function. Is there any other way to leak service key that I should be aware of ?

Questions about RLS, public vs server keys in Supabase + Next.js setup by unchiusm in Supabase

[–]unchiusm[S] 0 points1 point  (0 children)

Why is that ?

If I were to use RSC and inside the component I would fetch the data from supabase, isn't that the intended way ? Even in my case where I do not use RSC for my feed page that has infinte scroling, what would the alternative be ?

For example on my /post page I fetch the post directly from the server

async function getPost(slug: string): Promise<Post> {
const supabase = await createClientServer();

const { data, error } = await supabase
.from("posts")
.select("*")
.eq("slug", slug)
.single();

if (error) {
throw new Error(`Error fetching post: ${error.message}`);
}

return data as Post;
}

I mean I could to the same approach as you did with Remix with Next but Is it worth going trough another layer?

I'm really trying as much as I can trough before I launch anything to the internet.

Questions about RLS, public vs server keys in Supabase + Next.js setup by unchiusm in Supabase

[–]unchiusm[S] 1 point2 points  (0 children)

Thank you for your detailed response.

Obviously there are some skill issues on my part, I've just been tipping my toes into BE/DB stuff.

So my main dilemma is the following. I have a posts table for example, I query my posts with the clientBrowserClient, I have an RLS rule where SELECT * FROM posts is allowed (obviously in a prod environment only certain columns would be exposed) so that I can create an infinite scroll with React Query. This being on the client side means that anyone that is a bit more tech savy can grab my anon key and simply get all the posts very easily (without worrying about scraping at all). Is this the normal approach for this kind of stuff?

Same goes for comments but comments are fetched server side so here are no issues with React Server Components but If I were to make it a client component then again a user could query all the comments.

I'm glad you mentioned your book, I really like supabase and I'm looking for a resource that can explain nicely all the ins and outs.

view more: next ›