[Archivesspace_Users_Group] OCLC Digital Collection Gateway

Majewski, Steven Dennis (sdm7g) sdm7g at virginia.edu
Tue Dec 3 14:20:16 EST 2019

Not at all a solution to the original posters problem, but I was thinking of proposing that in a future release, we just get rid of the separate OAI server, and server OAI from  public-url/oai .

Some sites are already doing that — I assume thru apache or other proxy server. 
( I think that’s what Lyrasis is doing for the sites they manage. I wish I had thought of that obvious option before setting up a separate VHOST for OAI.  )

The existing OAI server is only proxying data from the backend server anyway. 

Proxying to the PUI would make configuration simpler, and would have the side benefit of a consistent OAI endpoint for all public sites. 

— Steve M. 

> On Dec 3, 2019, at 2:02 PM, Seth Shaw <seth.shaw at unlv.edu> wrote:
> Side note now that Steve pointed out that port 8081 does work, I recommend changing the PUI port to "80", the default web port, so users don't need to add the 8081 port to access your site.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4974 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20191203/cf7a9c6d/attachment.bin>

More information about the Archivesspace_Users_Group mailing list