Setting URL/Port for running cobudget behind https/https proxies

[hh]

As a user of a cobudget-ui instance
In order to have a delightful user experience
I want to only see http(s)://myhost.org in my web browser

Given source code checkout of cobudget-ui
And I have configured a proxy from http://mygroup.org:80 to http://cobudgethost:9000
When I run npm start and friends
Then I won't see the default port 9000 used anywhere

We need to run npm start on a high port (obviously don't run as root just to grab port 80).

However, it's unclear how to configure the internal generation of urls to use port 80 when the default is port 9000.

[hh]

@gardner is there an easy happy path on this?

[gardner]

Looks like using PORT=3133 npm start should override the dev server port.

The API server is adjusted using config files like this development one.

The API and the UI currently have their own repos and their own development configs. I feel as if it would be easier to be able to test a commit if they were in the same repo.

It sounds like you have the reverse proxy setup already. We're running metabase on one of our servers and this is how we're forwarding to it:

    ProxyVia on

    ProxyPass / http://127.0.0.1:3000/ nocanon
    ProxyPassReverse /  https://127.0.0.1:3000/
    ProxyPassReverse / https://secure.myhost.org/
    RequestHeader set X-Forwarded-Proto "https"
    RequestHeader set X-Forwarded-Port "443"

    ### Allow everything by default
    <Proxy *>
        Require all granted
    </proxy>

We just moved this domain behind cloudflare for a free wildcard TLS certificate. I'm not sure if any of this answered your question.

[denverwilliams]

@gardner

Awesome Thanks for that, the only other thing that was required to get "Email Invites" sending out with a different url/port was setting the default_url_options under config/environments/test.rb to the required host/port

config.action_mailer.default_url_options = { :host => 'cobudget.ii.org.nz' }