Support for Environment Variables/Secrets in Frontend Clones

[enahsor]

🌈 Feature

This feature already exists on server clones. There's a tab called 'Server Control Panel' which doesn't appear on React clones. It allows you to store environment variables for your application. It's not hard to see how this feature would prove useful.

[DeMoorJasper]

Thanks for your feedback!

I have added your feature request to our internal backlog which we use to prioritize what to build next. We can't make any promises about the timing, but it's on the list!

If you'd like to work on this feature with us, please create a pull request and we'll help you along the way.

For others landing on this issue, feel free to add more context or simply leave a thumbs up 👍 on this comment if you find this feature useful.

[enahsor]

Sure. I'll give it a try.

[enahsor]

@DeMoorJasper what's to stop me from simply importing the 'Server' component found on server sandboxes and using it on frontend sandboxes and it just working?

[DeMoorJasper]

I think the server component is very tied to a server instance that's probably why it won't work.

To begin it would probably be best to support basic .env file support and than additionally add some ui to more easily edit this file? As a hacky way of supporting this we could make process a global variable that has a js object representation of the .env file.

Having secrets in a browser based sandbox will be a more complicated undertaking as we'll have to store these securely on the api and ensure we never leak these in compiled code. But than it probably no longer really makes sense to use a browser-based sandbox anyway as client-side code can never really have secrets?

Sorry for the very late reply, this issue got buried in my github notifications