admin/twenty
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Documentation + docker-compose.yml update (#9653)

Browse Source 
Related to #9469 #9455 #9419 #8943
This commit is contained in:
BOHEUS
2025-01-16 09:43:27 +00:00
committed by GitHub
parent 5bae5a9f7c
commit 34ddeade83
7 changed files with 72 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
packages/twenty-website/src/content/developers/self-hosting/docker-compose.mdx
View File

@ -83,7 +83,7 @@ curl -O https://raw.githubusercontent.com/twentyhq/twenty/refs/tags/v0.35.0/pack
Start the Docker containers:
```bash
docker-compose up -d
docker compose up -d
```
### Step 4: Access the Application
@ -158,8 +158,8 @@ We strongly recommend setting up Twenty behind a reverse proxy with SSL terminat
For changes to take effect, restart the Docker containers:
```bash
docker-compose down
docker-compose up -d
docker compose down
docker compose up -d
```
#### Considerations

6
packages/twenty-website/src/content/developers/self-hosting/troubleshooting.mdx
View File

@ -94,8 +94,8 @@ If you can't log in after setup:
```
2. Restart the Docker containers:
```bash
docker-compose down
docker-compose up -d
docker compose down
docker compose up -d
```
Note the database:reset command will completely erase your database and recreate it from scratch.
@ -125,7 +125,7 @@ If you encounter issues not covered in this guide:
View container logs for error messages:
```bash
docker-compose logs
docker compose logs
```
- Community Support:

6
packages/twenty-website/src/content/developers/self-hosting/upgrade-guide.mdx
View File

@ -19,7 +19,9 @@ If you used Docker Compose, follow these steps:
2. Upgrade the version by changing the `TAG` value in the .env file near your docker-compose.
3. Bring Twenty back online with `docker-compose up -d`
3. Bring Twenty back online with `docker compose up -d`
If you want to upgrade your instance by few versions, e.g. from 0.33.0 to 0.35.0, you have to upgrade your instance sequentially, in this example from 0.33.0 to 0.34.0, then from 0.34.0 to 0.35.0.
## Version-specific upgrade steps
@ -75,6 +77,8 @@ The `yarn command:prod cache:flush` command will flush the Redis cache.
The `yarn database:migrate:prod` command will apply the migrations to the database structure (core and metadata schemas)
The `yarn command:prod upgrade-0.33` takes care of the data migration of all workspaces.
Starting from this version, twenty-postgres image for DB became deprecated and twenty-postgres-spilo is used instead.
If you want to keep using twenty-postgres image, simply replace `twentycrm/twenty-postgres:${TAG}` with `twentycrm/twenty-postgres` in docker-compose.yml.
### v0.31.0 to v0.32.0