How to provide self-hosted admin URL

Issues
5

Thank you so much ! I will do it !

I also want to ask you about docker compose files.
I described a lot here Docker Compose file not working - #8 by david_d

But shortly spoken, docker files have some problems:

  1. Command part can’t be finished correctly, since it has not rights for creating files during docker composing:
command: |
    jq '(.host = "plasmic-db") | (.password //= "SEKRET")' ormconfig.json > tmp.json && mv tmp.json ormconfig.json && \
    yarn typeorm migration:run && \
    yarn seed && \
    cd /plasmic && \
    yarn dev

plasmic-wab-1 | sh: can’t create tmp.json: Permission denied

  1. Observability file should be edited to make it work platform/wab/src/wab/server/observabilty/index.ts:
import { PinoLogger } from "./PinoLogger";

export function logger() {
  return new PinoLogger();
}
  1. Ports in docker compose are open for external connections like 3003:3003 which is not very safe when deploying it together on host with other services. It’s better to use a common network, something like plasmic-network

And than refer cointainers together by their names inside this network like:
http://plasmic-wab:3003

Conclusion:
The main problem here is this command section (problem #1) which I haven’t fixed normally as a permanent solution, not temporary.

Maybe you could advice something to customize it so it will work just by
docker compose up -d ?

Since deploying in docker here is much more demanding, I already made a deployment by yarn without docker. But it would be wounderful if it could be just 1 docker command.

I see on reddit in r/selfhosted plasmic is not such popular only beacuse it’s hard to deploy. There are also no updated instructions on internet about this, but only step could fix it is to correct docker compose files.

Thank you for your response!