Yeah I was thinking of that

Can’t cookies() be used in client components as well? I have to use 3rd party lib?

no you can't. For what do you need cookies clientside? What do you want to do?

I would need to set a cookie based on selected item in selectbox

And also display current app config (env name, api base)

why dont you set that only clientside? For what does the server know the value before any action?

Why dont you use a database that saves everything about the user (env name, api base, ...)?

That could work

Some /config endpoint

yea, or server actions if the user can do something with it

My intention is to have a selectbox in the header next to logout button that allows changing current environment that would reload the app but fetching all the data from other api server (and different database)

so this selectbox can be one value, right? Like either epic or mystic or legendary or ... (of course just examples) xD (but one value)

Yeah

I have multiple backends doing the same thing but using a different database

Server actions just serve as additional layer over these APIs

alright. What do you think about having this one value inside your searchParams? They can be changed and read clientside and also serverside

Now if I had 5 backends running I would need to deploy 5 separate nextjs apps using different env variables

So this is what I’m trying to solve

That could work maybe 🤔

ohhh dont do that 💀

It’s really just 1 app

do these backend have a name like production developement test ...?

Noo

yea, we want 1 app that can connect to 5 different backends and the user can easily switch them using one select

Yes

Its really like multiple oauth apps with their client ids and secrets but each app has their own backend with database deployed

So app1-api.example.com, app2-api.example.com

oh ok, then forget the idea with the searchparams.. it would be to much work to maintain the state over route changes... I would say, that cookies are the best idea to solve it.

I think about this now:
1. Create a database table, that contains the specific keys and pair them with an id.
2. Then the user can select one of these ids (you can also fetch them directly from the database if you need to)
3. The user select an id and everything automatically changes.
Because: if the user now for example call the function authMe the authMe function (serverside) would check the value of the specific cookie for the backend and use the correct backend directly

Yeah so cookies or database config it is then 🤔

I would do it like that, yea. Of course you can extend the database table even more. For example if a backend is currently in maintainence then there is a status inside the database, that it is in maintainence. Or you can configure a fallback, that is saved inside the database. Or ...

Thanks i will try. Other option is to make my backend select different database dynamically and just deploy 1 backend l then I don’t have to do much in nextjs

When I integrate auth with different backends (providers), I like to make an array of providers, that contains the specific env variables for these specific providers, yea. I guess you have a more complex scenario, where you might need the database stuff

@Great golden digger waspsolved?

Yeah thank you, got the idea of how to do it

happy to help. Please mark solution

done