[Archivesspace_Users_Group] Running the (development) PUI on a separate server?

Majewski, Steven Dennis (sdm7g) sdm7g at virginia.edu
Fri Sep 29 15:57:09 EDT 2017

I haven't tried it (yet) but I'm guessing that you just have to set AppConfig[:enable_*] for all but :enable_public to false, and redirect all of the "http://localhost:port" default settings for AppConfig[:*_url] to point to the remote counterparts. You might also need to set AppConfig[:frontend_proxy_url]

That should (in theory) get you a configuration with only public server running, talking to backend, solr and frontend on remote server.

-- Steve Majewski / UVA Alderman Library
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Fox, Bobbi <bobbi_fox at harvard.edu>
Sent: Friday, September 29, 2017 2:14:58 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Running the (development) PUI on a separate server?


I’m working on customizing the PUI for our institution, working in development mode, and, rather than cloning off our humongous, takes-2+-days to index database (which I need to do, because my “product owner” is a committee made up of picky(yeah, that’s redundant) Archivists :-) , I was hoping to point to the backend of our V2.1.* QA system already running.

Has anyone tried this?  What incredible munging of the build.xml am I likely to need to do?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170929/5f57acbf/attachment.html>

More information about the Archivesspace_Users_Group mailing list