From 5a1f212c5dffe7498606e8180aed05e62beafe41 Mon Sep 17 00:00:00 2001 From: Pokey <79169880+Pokeylooted@users.noreply.github.com> Date: Mon, 4 Mar 2024 18:18:43 -0600 Subject: [PATCH] Fix duplication --- content/4.backend/1.deploy.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/content/4.backend/1.deploy.md b/content/4.backend/1.deploy.md index 0829e70..ddb1fb6 100644 --- a/content/4.backend/1.deploy.md +++ b/content/4.backend/1.deploy.md @@ -76,10 +76,8 @@ Your backend should be accessible on `(YourPrivateIP):80`. To share it outside y To enhance your SSL and domain configuration, it's advisable to establish a reverse proxy, such as Nginx. For an optimal choice in this regard, Cloudflare Zero Trust Tunnel is recommended. You can find more information [here](https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel/). -- If you decide to utilize a reverse proxy, it's important to include `MWB_SERVER__CORS: "example.com movie.example.com"` in your configuration. -- If you use a reverse proxy behind a domain, add `MWB_SERVER__CORS: "https://movie.example.com"`. +- If you decide to utilize a reverse proxy, it's important to include `MWB_SERVER__CORS: "https://movie.example.com"` in your configuration. - `MWB_SERVER__CORS` must contain a **space-separated** list of origins (Protocol + Hostname) for the client to be able to access the backend. - - Depending on your specific setup, you may also require the addition of `MWB_SERVER__TRUST_PROXY: true` and `MWB_SERVER__TRUST_CLOUDFLARE: true`. ## Method 2 - Railway (Easy)