How to have Consul up & running in production

#1

I set up consul and it works well in dev mode running bin/rails s -b 0.0.0.0 -p 8080

Now I want to run it in production mode, so I run bin/rails s -b 0.0.0.0 -p 8080 -e production

First error was:
Missing secret_token and secret_key_base for ‘production’ environment, set these values in config/secrets.yml

So I set secret_key_base in config/secrets.yml, which has already a secret_key_base.
Bot no idea where to set secret_token and in which format.

Anyhow I can now run bin/rails s -b 0.0.0.0 -p 8080 -e production. The server is launched. But a browser cannot connect. See the output when trying to connect right from localhost in text mode:

consul@consul:~$ lynx http://localhost:8080

Looking up localhost:8080
Making HTTP connection to localhost:8080
Sending HTTP request.
HTTP request sent; waiting for response.
HTTP/1.1 301 Moved Permanently
Data transfer complete
HTTP/1.1 301 Moved Permanently
Using https://localhost:8080/
Looking up localhost:8080
Making HTTPS connection to localhost:8080
Alert!: Unable to make secure connection to remote host.

lynx: Can't access startfile http://localhost:8080/
consul@consul:~$

Why is a HTTPS redirection set up? How to disable it?

I would appreciate any help about how to run Consul in production mode.

Thank you very much.

#2

HTTPS issue was solved in just one step:

consul@consul:~/consul$ git diff
diff --git a/config/environments/production.rb b/config/environments/production.rb
index 9ca195d..0dd66db 100644
--- a/config/environments/production.rb
+++ b/config/environments/production.rb
@@ -42,7 +42,7 @@ Rails.application.configure do
   # config.action_dispatch.x_sendfile_header = 'X-Accel-Redirect' # for NGINX
 
   # Force all access to the app over SSL, use Strict-Transport-Security, and use secure cookies.
-  config.force_ssl = true
+  config.force_ssl = false
 
   # Use the lowest log level to ensure availability of diagnostic information
   # when problems arise.

Anyway, now CSS is not loaded (404 error).