Bug: "relation 'organizations' does not exist" error when self-hosting with Docker Compose.

[dayrondev94]

When deploying LinkForty in a self-hosted environment using Docker Compose, the API service fails to start and returns the following error:

{"statusCode":500,"code":"42P01","error":"Internal Server Error","message":"relation "organizations" does not exist"}

The application becomes inaccessible, and the error appears consistently when the API attempts to query the organizations table. This seems to indicate that the required database table is missing, possibly due to migrations not running automatically during the self-hosted setup.

[m-racine]

I was just looking into this for my own setup. The issue lies with the database migrations not creating an organizations (or users) table, but the redirect in the routes code still references it.

This is not helped by the /health endpoint apparently needing to redirect to /api/sdk/v1/health, so even checking /health throws the error.

It's likely that the non-core version of LinkForty needs the organizations join on the redirect; but maybe the core version can have at least dummy tables ship with it? or the minimum schema needed detailed at least?