Docker image: Environment variables for domains and ports

[avunculargroup]

I am self-hosting using the Docker image with the Railway template.

I'm wanting to clarify how many ports the app runs on. I notice on the main cal.com, there is app.cal.com, then cal.com for the public booking pages. How does that work with the environment variables? I'm a bit confused.

I assumed that everything ran on the same port, so I'm just using cal.avunculargroup.com. It is working fine for the "app" part (admin side), but for the public booking pages its defaulting to the Railway url. I haven't had a lot of experience with deploying cal, would appreciate some direction. I've looked at the the github env example, but it's not clear.

I have posed this question in the Railway support pages but they said they cannot help and better to ask here.

[dosubot[bot]]

Hello @avunculargroup! I'm here to help you with bugs, answer questions, and guide you toward contributing. Feel free to ask anything while you wait for a human maintainer. Let's tackle this together!

To configure the domain and ports for both the admin and public booking pages in a self-hosted Cal.com setup, you need to set specific environment variables. Here are the key variables you should focus on:

1. NEXT_PUBLIC_WEBAPP_URL: This variable sets the URL for the web application, which is typically the public booking page. For example, you can set it to NEXT_PUBLIC_WEBAPP_URL='http://cal.avunculargroup.com'.

2. NEXT_PUBLIC_CONSOLE_URL: This variable sets the URL for the admin console. You can set it to NEXT_PUBLIC_CONSOLE_URL='http://cal.avunculargroup.com' if you want both the admin and public pages to be accessible from the same domain.

Additionally, if the public booking pages are defaulting to the Railway URL, you might need to set the RAILWAY_STATIC_URL environment variable to override the default Railway URL. This will ensure that the public booking pages use your specified domain instead of the Railway URL ^[1][2].

Make sure these environment variables are correctly set in your deployment configuration to ensure both the admin and public booking pages are accessible through your desired domain.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[avunculargroup]

Actually RAILWAY_STATIC_URL is deprecated.

Here are my non-private env variables as json:

{ "ALLOWED_HOSTNAMES": "\"avunculargroup.com\"", "CALCOM_TELEMETRY_DISABLED": "1", "CALENDSO_ENCRYPTION_KEY": XXX, "DATABASE_DIRECT_URL": "${{Postgres.DATABASE_PRIVATE_URL}}", "DATABASE_HOST": "${{Postgres.PGHOST_PRIVATE}}:${{Postgres.PGPORT_PRIVATE}}", "DATABASE_URL": "${{Postgres.DATABASE_PRIVATE_URL}}", "GOOGLE_LOGIN_ENABLED": "false", "NEXT_PUBLIC_API_V2_URL": "https://cal.avunculargroup.com/api/v2", "NEXT_PUBLIC_APP_NAME": "Cal.com", "NEXT_PUBLIC_APP_URL": "https://cal.avunculargroup.com", "NEXT_PUBLIC_CALCOM_VERSION": "1.0.0", "NEXT_PUBLIC_DISABLE_SIGNUP": "false", "NEXT_PUBLIC_HOSTED_CAL_FEATURES": "0", "NEXT_PUBLIC_IS_E2E": "0", "NEXT_PUBLIC_IS_PREMIUM_NEW_PLAN": "0", "NEXT_PUBLIC_IS_SELF_HOSTED": "1", "NEXT_PUBLIC_ORGANIZATION_URL": "https://cal.avunculargroup.com", "NEXT_PUBLIC_TEAM_PARENT_GROUP_ID": "null", "NEXT_PUBLIC_WEBAPP_URL": "https://${{RAILWAY_PUBLIC_DOMAIN}}", "NEXT_PUBLIC_WEBSITE_URL": "https://cal.avunculargroup.com", "NEXTAUTH_COOKIE_DOMAIN": ".avunculargroup.com", "NEXTAUTH_URL": "https://${{RAILWAY_PUBLIC_DOMAIN}}", "NPM_CONFIG_UPDATE_NOTIFIER": "false", "WEBAPP_URL": "https://cal.avunculargroup.com", "WEBSITE_URL": "https://cal.avunculargroup.com" }