Remove duplicate caddyfile

README.md

@@ -49,13 +49,11 @@ data in real time! Below are some tips on how take full advantage of your node.
 * Whitelist some posts and verify that they show up on the global feed.
 * Deploy your node on any cloud provider with a static IP to make it accessible
   to anyone on the internet.
-  - If you do this, you must point *two* domains at your node.
-    domain.com *and* api.domain.com.
   - If you do this, you must replace deso.run with your domain in nginx.dev so
     that your traffic is routed to core and frontend properly.
-  - If you do this, you *must* add your domain to the Caddyfile.dev's
-    Content-Security-Policy or your site won't work. You will need to add two
-    entries: One for domain.com:\* and one for api.domain.com:\*
+  - If you want to customize which domains your frontend is allowed to connect to
+    you must copy the [Caddyfile from frontend](https://github.com/deso-protocol/frontend/blob/main/Caddyfile)
+    into this directory and set the `CADDY_FILE` variable in [dev.env](https://github.com/deso-protocol/run/blob/main/dev.env).
 * Add the necessary nginx configuration for your SSL certificates generated by letsencrypt
 * Set the TWILIO\* flags to allow new users to get some starter DeSo.
 * Set a SUPPORT\_EMAIL so your users can contact you if they run into trouble.

dev.env

@@ -41,15 +41,15 @@ ADD_IPS=
 ADD_SEEDS=
 
 # admin_public_keys is list of public keys delimited by a space
-# which gives users access to the admin panel. If '*' is specified 
-# anyone can access the admin panel. 
+# which gives users access to the admin panel. If '*' is specified
+# anyone can access the admin panel.
 ADMIN_PUBLIC_KEYS=*
 
 # super_admin_public_keys is a list of public keys delimited by a space
 # which gives users access to the super tab of the admin panel and select endpoints
 # for these privileged users.  At this time, super admins can adjust the reserve price
 # at which this node will sell $DESO, set the slippage fee applied to $DESO buys,
-# and manage verification of users on this node. 
+# and manage verification of users on this node.
 SUPER_ADMIN_PUBLIC_KEYS=*
 
 # When set, determines the port on which this node will listen for protocol-related
@@ -157,7 +157,7 @@ ACCESS_CONTROL_ALLOW_ORIGINS=*
 # is the default right now.
 SECURE_HEADER_DEVELOPMENT=true
 
-# These are the domains that our secure middleware will accept requests from. 
+# These are the domains that our secure middleware will accept requests from.
 # Accepts a space-separated lists of origin domains.
 # We also set the HTTP Access-Control-Allow-Origin
 SECURE_HEADER_ALLOW_HOSTS=
@@ -168,7 +168,7 @@ AMPLITUDE_KEY=
 # Optional. Client-side amplitude API Endpoint.
 AMPLITUDE_DOMAIN=api.amplitude.com
 
-# Optional. Twilio account SID (string id). Twilio is used for sending 
+# Optional. Twilio account SID (string id). Twilio is used for sending
 # verification texts. See twilio documentation for more info.
 TWILIO_ACCOUNT_SID=
 
@@ -236,7 +236,7 @@ LOG_DB_SUMMARY_SNAPSHOTS=false
 # / creator coins.
 SHOW_PROCESSING_SPINNERS=true
 
-# When set to true, unmined BitcoinExchange transactions from peers are 
+# When set to true, unmined BitcoinExchange transactions from peers are
 # disregarded. This is OK because we will eventually reprocess this transaction once
 # it gets mined into a block, although anything that is built on top of it may not
 # be considered. It's set to false by default because most nodes connect to trusted
@@ -257,4 +257,4 @@ GCP_BUCKET_NAME=images.bitclout.com
 ### Environment vars for the frontend image
 
 # Override the Caddyfile with the one in this directory
-CADDY_FILE=/app/Caddyfile.dev
+# CADDY_FILE=/app/Caddyfile.dev