[Archivesspace_Users_Group] Proxying and AppConfig[:frontend_url]

[Stephen Schor]

Thanks for the quick reply Brian.

In my case it's more a case of aesthetics.
We want users to have specific domains and not have to specify port numbers.

With that in mind - I was curious what would happen if we simply did the nginx
proxy configuration
<https://www.nginx.com/resources/admin-guide/reverse-proxy/>
but don't set AppConfig[:public_url]/[:public_proxy_url].



On Wed, May 4, 2016 at 12:39 PM, Brian Hoffman <brianjhoffman at gmail.com>
wrote:

> Hi,
>
> If you are planning to leave each virtual server open to the world, you
> should be fine just recording the application urls (example:
> AppConfig[:backend_url] = ‘archivesspace-api.example.org’). But if you
> are going to restrict www access to the api service or the staff interface,
> you’ll need to do something like what’s described here:
> https://github.com/archivesspace/archivesspace/blob/master/README_HTTPS.md.
> The proxy settings you mentioned are useful if the frontend_url is
> localhost:8080 but port 8080 isn’t accessible to end users.
>
> Brian
>
>
>
> On May 4, 2016, at 12:30 PM, Stephen Schor <stephenschor at nypl.org> wrote:
>
> Hi.
>
> I'm looking to deploy ASpace using NGIX as a proxy to present the various
> apps on port 80.
> For example:
>
> proxy port 8080 to archivesspace-staff.example.org     to port 80
> proxy port 8081 to archivesspace-public.example.org  to port 80
> proxy port 8089 to archivesspace-api.example.org       to port 80
>
>
> I'm interested in what the consequences are of leaving the boilerplate
> setup in config.rb would be?
> It was this section that caught my attention:
>
> ## Proxy URLs
> ## If you are serving user-facing applications via proxy
> ## (i.e., another domain or port, or via https, or for a prefix) it is
> ## recommended that you record those URLs in your configuration
> #AppConfig[:frontend_proxy_url] = proc { AppConfig[:frontend_url] }
> #AppConfig[:public_proxy_url] = proc { AppConfig[:public_url] }
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160504/ae98b4e5/attachment.html>