Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Self Hosting environment variables scope #1861

Open
crzdg opened this issue Oct 24, 2024 · 2 comments
Open

Self Hosting environment variables scope #1861

crzdg opened this issue Oct 24, 2024 · 2 comments
Labels
Content 📝 Improvements or additions to documentation

Comments

@crzdg
Copy link

crzdg commented Oct 24, 2024

Hi!

Thanks for the great project, loving it. Well maintained and great code base.

I have a question for self-hosting deployment and the environment variables. Is it somewhere documented which environment variable are actually used by the two containers viewer and builder. I see in the example the share the .env`-file. However, I assume not all variables are needed in both containers. Some may shared and some may only used by one container. How can I find this out? Would like to have a clear separation of it.

Thanks!

@baptisteArno
Copy link
Owner

We had that separated in a previous version of the project but we prefer having a shared environment for better dev experience.

I guess we could add a mention on where each variable is used in the configuration docs

@baptisteArno baptisteArno added the Content 📝 Improvements or additions to documentation label Oct 25, 2024
@github-project-automation github-project-automation bot moved this to Backlog ☁️ in Typebot Oct 25, 2024
@crzdg
Copy link
Author

crzdg commented Oct 27, 2024

Thanks for the answer. I understand and agree on convenience for developers and quick test deployments having it one. But when deploying to production it would nice to have to allow for separation. May a column in the table https://docs.typebot.io/self-hosting/configuration - does the trick. Would be great to see :)

I think for the parts other then general it is only the builder which would need the config. Would only apply for General table.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content 📝 Improvements or additions to documentation
Projects
Status: Backlog ☁️
Development

No branches or pull requests

2 participants