twenty/packages/twenty-website
Félix Malfait c90d2fd5cc
Change default behavior of ENABLE DB MIGRATION (#9077)
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?
2024-12-16 17:31:45 +01:00
..
public 0.34 changelog (#9091) 2024-12-16 17:26:15 +01:00
src Change default behavior of ENABLE DB MIGRATION (#9077) 2024-12-16 17:31:45 +01:00
.env.example Added Algolia Search (#5524) 2024-05-22 12:06:00 +02:00
.eslintrc.js chore: use common eslint config for most packages (#4705) 2024-04-04 12:05:26 +02:00
.gitignore Marketing improvements 3 (#3175) 2023-12-29 11:17:32 +01:00
next.config.js Marketing improvements 3 (#3175) 2023-12-29 11:17:32 +01:00
package.json start 0.40.0 canary (#9029) 2024-12-11 19:23:51 +01:00
README.md Website - Readme update (#8712) 2024-11-25 17:26:39 +01:00
tsconfig.json Add proper ORM and postgres support (#3978) 2024-02-14 17:53:50 +01:00

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.

  1. Copy the .env.example file to .env and fill in the values.

  2. Run the migrations:

npx nx run twenty-website:database:migrate
  1. 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