A small PR but a big step towards making Twenty easier to self-host and upgrade! Now changing the tag and pulling a new version should be the only step to upgrade as migrations script will be ran automatically upon starting the containers. It was already the case for typeorm migrations, but not for standard objects migration and data migration scripts. It is still possible to disable this behavior for the most complex deployments such as our own cloud.
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