[Development Pack] [MacOS] No issue - The thread can be closed / deleted!

[mustafa-yilmaz]

This thread was opened because of a misunderstanding on Docmost's installation instructions at https://docmost.com/docs/installation.

Although the relevant document clearly directs towards a non-Docker installation for development purposes in the very first line, we proceeded with a Docker-based setup and had to open this thread.

---

The original/initial thread is below.

Hi @Philipinho and all Docmost experts / enthusiasts,

Our team recently installed the Docmost development pack in a (!)MacOS(!) local environment, and we are encountering an issue when trying to edit pages. The problem is demonstrated in the video linked below.

Issue Description:
1. When making changes as a user (without specifying a certain port in the URL), the edits do not appear on the backend port (3000 in our case)—it only displays the initial state from when Docmost was first installed.
2. However, changes made directly on the backend port (3000) do reflect on the frontend port.
3. The frontend port (5173) does not allow us to edit the table cells; it only allows us to change the page title.

What could be causing this issue? Any suggestion would be much appreciated. Thanks.

VID-20250127-WA0003.mp4

[Philipinho]

If the page is in readonly mode, it means it is failing to establish a websocket connection.
Check the browser console to see the websocket status.

[mustafa-yilmaz]

Thanks for the response, @Philipinho .

I am sharing the browser console (for the frontend port - 5173) below. It says the WebSocket (ws) is connected.

We will try to re-install the development pack (on MacOS) once again and update here if we'll still face any issues.

CC : @singleservingfriend , @furkansalihipek .

[mustafa-yilmaz]

I am sharing the edited/altered "vite.config.ts" file in our installation below. We thought we had to change/edit it because of the synchronization issue we have with the initial state of the installation.

The edited/altered "vite.config.ts" file :

Did you get to reinstalling it?

Yes, we also installed the development pack of Docmost locally on another MacOS machine, and we still have the same synchronization issue with the initial installation state (without touching any file or any code), as explained through the three screenshots below.

After the installation, when we try to make a change in any file (it is changing the color of the table border in our case) , that change appears on the 5173 port but not on the 3000 port.

We have also another running online installation on an Ubuntu server. We just did not check if we also have the same issue on that installation.

Dear @Philipinho ,

Would it be possible for someone from the Docmost team to directly assist us by connecting to our installation(s) and examining the issue from the owner's perspective? We now seriously need such direct assistance, as this issue has already been taking up a considerable amount of our team's time.

[Philipinho]

After the installation, when we try to make a change in any file (it is changing the color of the table border in our case) , that change appears on the 5173 port but not on the 3000 port.

If you are in development mode for client-side changes, you should use the Vite port 5173 which comes with HMR refreshes. For port 3000 to pickup client side changes, you have to rebuild every time you make changes.

Would it be possible for someone from the Docmost team to directly assist us by connecting to our installation

Community support is the best we can offer, unless you are willing to pay for premium support (based on availability).

In addition, we provide production Docker images to simplify and make Docmost's behavior consistent across installations.
Development mode issues can tricky as your environment might not easily be replicated.
Generally, we assume users working in development mode are familiar with Node.js and can debug their own environments.

[mustafa-yilmaz]

It's my fault for not mentioning that we already rebuild with either "docker compose —build" or "docker compose up -d" terminal commands after the alterations/changes we make. We already rebuild every time, but still, we are not able to see any changes on the 3000 port.

[Philipinho]

From the screenshot provided above, docker ps shows you are pulling docmost/docmost:latest from Dockerhub and not locally. You may want to confirm that. It could also be the root of your problems because the /api/auth/collab-token endpoint is not available in our production Docker builds. It is only in the Github repo.

[mustafa-yilmaz]

Thanks so much, @Philipinho .

All our installations are with Docker, yes.

Just to confirm/clarify: For development purposes, the Docmost team recommends developers installing Docmost without Docker? Am I right?

If it is the case, then we will reinstall without Docker and try to update here whether or not we will face any other issues. Thanks once again.

[Philipinho]

Just to confirm/clarify: For development purposes, the Docmost team recommends developers installing Docmost without Docker? Am I right?

Correct.

[mustafa-yilmaz]

@Philipinho ,

Thanks so much for all your help.

Now we have multiple development packs running locally and also online without any issue.

Our team (@singleservingfriend, @furkansalihipek) is now switching to #651 .

Thanks once again.