Skip to content

update setup docs - config variables #12370

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

ehconitin
Copy link
Contributor

@ehconitin ehconitin requested a review from FelixMalfait May 28, 2025 18:55
@ehconitin ehconitin self-assigned this May 28, 2025
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Summary

This PR significantly updates the setup documentation by introducing a hybrid configuration management approach that combines environment variables with an admin panel interface, making configuration more user-friendly and maintainable.

  • Added admin panel configuration section detailing user access controls and configurable settings
  • Introduced configuration modes (Default/Environment-Only) with clear explanations of each mode's behavior
  • Clarified essential infrastructure variables that must remain in .env files
  • Added multi-container deployment considerations for database configuration
  • Improved documentation structure with clearer separation between environment-only and admin-panel configurable variables

1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile

@ehconitin
Copy link
Contributor Author

TODO:

  • where should Frontend section go?
Screenshot 2025-05-29 at 00 26 57
  • find a good position to put Email SMTP Server configuration examples
Screenshot 2025-05-29 at 00 27 30


**Most configuration can be managed through the Admin Panel** once your instance is running:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we have this run automatically so that users don't have to think about it during setup?

"yarn command:prod cron:messaging:messages-import
yarn command:prod cron:messaging:message-list-fetch
yarn command:prod cron:calendar:calendar-event-list-fetch
yarn command:prod cron:calendar:calendar-events-import
yarn command:prod cron:messaging:ongoing-stale
yarn command:prod cron:calendar:ongoing-stale
yarn command:prod cron:workflow:automated-cron-trigger"

Maybe create one super command or integrate it as part of the upgrade... Never dug into this so not 100% sure what they do. But it would help us keep the docs focused on Env Var only

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can be in another PR of course

@@ -25,12 +25,12 @@ See docs [Setup Environment Variables](https://twenty.com/developers/section/sel

Install the latest stable version of Twenty with a single command:
```bash
bash <(curl -sL https://git.new/20)
bash <(curl -sL https://raw.githubusercontent.com/twentyhq/twenty/main/packages/twenty-docker/scripts/install.sh)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

temporary! till we get short link working

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update/depreciate self hosting mdx on twenty-website
2 participants