mirror of
https://github.com/twentyhq/twenty.git
synced 2024-12-23 03:51:36 +03:00
c90d2fd5cc
See: https://github.com/twentyhq/twenty/issues/9031#issuecomment-2542015975 I think it would be easier if the default behavior for the container was to run the migration, and setting the environment variable would be used to disable it (e.g. on the worker). Long-term goal is for the default setup to work out of the box with ~2 env variables only (database url, redis url) I don't think there's a big risk if people forget to turn it off on the worker? |
||
|---|---|---|
| .. | ||
| public | ||
| src | ||
| .env.example | ||
| .eslintrc.js | ||
| .gitignore | ||
| next.config.js | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
Twenty-Website
This used for the marketing website (twenty.com). This is not related in anyway to the main app, which you can find in twenty-front and twenty-server.
Getting Started
We're using Next.JS We're using Postgres for the database. Mandatory for the website to work, even locally.
-
Copy the .env.example file to .env and fill in the values.
-
Run the migrations:
npx nx run twenty-website:database:migrate
- From the root directory:
npx nx run twenty-website:dev
Then open http://localhost:3000 with your browser to see the result.
Or to build in prod:
npx nx run twenty-website:build
npx nx run twenty-website:start