Is it possible to put secrets public ( main repl ) but when forked, you have to fill in the secret

Just wondering… Is it possible to do this? If yes, then my chatroom idea with a database proxy might be possible…

I don’t quite understand what you mean. Do you propose to make it so that when the replay is branched, the one who did the branching gets access to the secret values? Can you explain your question in more detail?

I must warn you that it is not safe to make secrets publicly available, since others will be able to use the information kept secret for their own purposes.
The secrets were created so that you could keep your API keys and other information unreadable for everyone but you.

Well, I will make secrets publicly available, but is it possible not to let the user get the value of it.

they get access, but they cannot see, use, or copy the value.

To prevent others from getting any personal benefit from your secret values, secrets must contain some useless or unimportant information.

They contain the link to a database proxy ( which I will put as private ( the repl ) ) Which is why I don’t want the user to physically get, see, use OR copy to alter data in chats.

If they can’t use them, then what would be their point?

So my understanding is you just want people to be able to see the secret names? If that’s the case, you can see that in the code. If you want to tell people, you could just outright tell them in the description or in whatever you’re developing.

I think I understand. You can see the IRL of the db, but you cannot access it, hack it, or edit it as it is Private. @Idkwhttph Am I right?

yes yes yes you are right
I meant that, they cannot access,hack,edit the database.

1 Like

Oh so they can still be connected to your database but not know the URL, that is not possible via a built-in method, on top of that your database URL changes occasionally too, however you could create an API that users can send requests to, then you can handle all requests and make any changes to the database and send responses.

I dont know how to do that can you help mi… :sob:

1 Like

Well, if you’re working with a database, you’ve probably got a backend, I’d guess it’s either Python Flask or NodeJS Express, most likely Flask, in which case you could then host an API which is just a POST route and when it receives requests, it interacts with the database accordingly.