Elvis Stansvik

I got a similar issue when upgrading to 14.2.1 just now. The OpenProject page after login is requesting `/assets/frontend/runtime.e9ffdf40b4330a46.js` and `/assets/frontend/main.63f41c09d0497c69.js`, but that is not the name of those files...

@abrmichael Ah now I saw your comment and also https://github.com/opf/openproject-deploy/commit/dbccaae404b977fdd1e1f1e36ded12b7a1e8207d#r143825032 That must be what happened to me. What is the solution to get out of this?

Ah, removing the volume sorts it out. So @infocillasas, I believe what @abrmichael meant was something like: ``` docker-compose down docker rm compose_assets docker-compose up -d ``` I.e. remove the...

Our docker-compose.yml should be essentially as the official one, except we're not making use of any named volumes, since we want all volume data stored at a particular place under...

Same issue with 0.23.2.

@charlesBochet @lucasbordeau Anything you've encountered in testing? ^

@charlesBochet Thanks! I don't think we're using Redis. We're essentially using the official docker-compose example at https://github.com/twentyhq/twenty/blob/main/packages/twenty-docker/docker-compose.yml as is, just with some minor modifications to put docker volume data at...

[Upgrade instructions](https://twenty.com/developers/section/self-hosting/upgrade-guide#if-you-used-docker-compose) for docker-compose installations don't mention `yarn command:prod upgrade-0.23`. Is it a command that must be run manually after `docker-compose up -d` after each upgrade? Or was it a...

Alright, thanks. I'll have a go at running that within the container after it's up. Since we didn't run this back when we upgraded from 0.21 to 0.22 either, I...

Ah, nevermind, I tried `yarn command:prod upgrade-0.22` and it told me there's no such command, so I guess that yarn command is not available when running the 0.23.2 code base....