Feature: .env file for the api

[a0m0rajab]

Type of feature

🔥 Performance

Current behavior

Based on the conversation here: https://discord.com/channels/714698561081704529/928693344358514698/1111046044646645931
I think it would be nice to have a .env file for the beta and test and using it in production.

Suggested solution

No response

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Contributing Docs

• I agree to follow this project's Contribution Docs

[a0m0rajab]

related to: #101

[bdougie]

I want to understand this before implementing it. This adds a level of complexity to the development process and we will have insight from all active contributors.

Could we do this for production& beta builds? This would allow us to provide beta apis by default, while not breaking anything.

NODE_ENV=production 
npm run build

[a0m0rajab]

I think it's possible to do. It will be similar to the https://github.com/open-sauced/insights repo.

We will need to apply the .env variables on the constant file: https://github.com/open-sauced/ai/blob/beta/src/constants.ts

[a0m0rajab]

Based on the vite documentation, this is possible to be done with --mode command.

vite build --mode prod 
vite build --mode beta

The .env files will .env.prod and .env.beta

Related docs:
https://vitejs.dev/guide/env-and-mode.html

[diivi]

Why do you need an env file though, we don't have any secrets right now afaik. For constant values, constants.ts should be enough?

[a0m0rajab]

@diivi it's not about secrets only, the constants we have right now is for productions, we need to have beta values to be able to test features like: post to highlight from the extension, otherwise the tests will go to production always.

[bdougie]

we need to have beta values to be able to test features like: post to highlight from the extension, otherwise the tests will go to production always.

My suggestion use the mode env only production and create an if statement for NODE_ENV to use the production URL only in production.

[github-actions]

🎉 This issue has been resolved in version 1.3.1-beta.5 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version 1.4.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀