Empathy List Archives

AB

Al Bersch

Fri, Sep 20, 2013 9:26 PM

Hello all,

It's me again at OMCA. I tried uploading a test image to a media handling record in our tenant (omca). I got a message that my browser could not connect to localhost:8180. I remembered resetting the server address when installing CollectionSpace, under the "configure your tenant" section. After looking, I realized that while I changed to server address in local-core-settings.xml during installation, there wasn't a corresponding local-omca-settings document in $CSPACE_JEESERVER_HOME/lib/tenants/omca/.

I checked, and images load fine in our core tenant.

Should I create a version of local-omca-settings.xml for our 'omca' tenant directly in $CSPACE_JEESERVER_HOME/lib/tenants/omca/. ? Or should I edit the settings.xml file in $CSPACE_JEESERVER_HOME/lib/tenants/omca/ to set the correct server address for images? Or is this a change I make elsewhere?

Thanks so much,

Al

Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468

Hello all, It's me again at OMCA. I tried uploading a test image to a media handling record in our tenant (omca). I got a message that my browser could not connect to localhost:8180. I remembered resetting the server address when installing CollectionSpace, under the "configure your tenant" section. After looking, I realized that while I changed to server address in local-core-settings.xml during installation, there wasn't a corresponding local-omca-settings document in $CSPACE_JEESERVER_HOME/lib/tenants/omca/. I checked, and images load fine in our core tenant. Should I create a version of local-omca-settings.xml for our 'omca' tenant directly in $CSPACE_JEESERVER_HOME/lib/tenants/omca/. ? Or should I edit the settings.xml file in $CSPACE_JEESERVER_HOME/lib/tenants/omca/ to set the correct server address for images? Or is this a change I make elsewhere? Thanks so much, Al Al Bersch Digital Project Coordinator Oakland Museum of California 1000 Oak Street, Oakland, CA 94607 abersch@museumca.org 510-318-8468

AR

Aron Roberts

Fri, Sep 20, 2013 9:41 PM

It's timely that you've mentioned this configuration piece, Al! We
ran into some similar issues recently, and as a result, configuring
the path to images has been streamlined in v4.0. (See the two links
below for the related discussion.)

For now, in v3.3, you can clone:

$CSPACE_JEESERVER_HOME/lib/tenants/omca/settings.xml
to
$CSPACE_JEESERVER_HOME/lib/tenants/omca/local-omca-settings.xml

and edit the <ims-url> value in the latter (local-omca-settings.xml)
file, changing the hostname from 'localhost' to the actual Internet
hostname at which you and others will be accessing your
CollectionSpace instance.

Aron

--

Simplifications to configuring the path for loading images, introduced
in recent work on CollectionSpace version 4.0:

http://wiki.collectionspace.org/display/collectionspace/Release+4.0#Release4.0-Imageloadingnolongerfailswhentheimagerepositoryhostnamehasnotbeenconfigured%28CSPACE4051

and

http://issues.collectionspace.org/browse/CSPACE-6183?focusedCommentId=41000&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-41000

On Fri, Sep 20, 2013 at 2:26 PM, Al Bersch abersch@museumca.org wrote:

Hello all,

It's me again at OMCA. I tried uploading a test image to a media handling
record in our tenant (omca). I got a message that my browser could not
connect to localhost:8180. I remembered resetting the server address when
installing CollectionSpace, under the "configure your tenant" section. After
looking, I realized that while I changed to server address in
local-core-settings.xml during installation, there wasn't a corresponding
local-omca-settings document in $CSPACE_JEESERVER_HOME/lib/tenants/omca/.

I checked, and images load fine in our core tenant.

Should I create a version of local-omca-settings.xml for our 'omca' tenant
directly in $CSPACE_JEESERVER_HOME/lib/tenants/omca/. ? Or should I edit the
settings.xml file in $CSPACE_JEESERVER_HOME/lib/tenants/omca/ to set the
correct server address for images? Or is this a change I make elsewhere?

Thanks so much,

Al

Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

It's timely that you've mentioned this configuration piece, Al! We ran into some similar issues recently, and as a result, configuring the path to images has been streamlined in v4.0. (See the two links below for the related discussion.) For now, in v3.3, you can clone: $CSPACE_JEESERVER_HOME/lib/tenants/omca/settings.xml to $CSPACE_JEESERVER_HOME/lib/tenants/omca/local-omca-settings.xml and edit the <ims-url> value in the latter (local-omca-settings.xml) file, changing the hostname from 'localhost' to the actual Internet hostname at which you and others will be accessing your CollectionSpace instance. Aron -- Simplifications to configuring the path for loading images, introduced in recent work on CollectionSpace version 4.0: http://wiki.collectionspace.org/display/collectionspace/Release+4.0#Release4.0-Imageloadingnolongerfailswhentheimagerepositoryhostnamehasnotbeenconfigured%28CSPACE4051 and http://issues.collectionspace.org/browse/CSPACE-6183?focusedCommentId=41000&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-41000 On Fri, Sep 20, 2013 at 2:26 PM, Al Bersch <abersch@museumca.org> wrote: > Hello all, > > It's me again at OMCA. I tried uploading a test image to a media handling > record in our tenant (omca). I got a message that my browser could not > connect to localhost:8180. I remembered resetting the server address when > installing CollectionSpace, under the "configure your tenant" section. After > looking, I realized that while I changed to server address in > local-core-settings.xml during installation, there wasn't a corresponding > local-omca-settings document in $CSPACE_JEESERVER_HOME/lib/tenants/omca/. > > I checked, and images load fine in our core tenant. > > Should I create a version of local-omca-settings.xml for our 'omca' tenant > directly in $CSPACE_JEESERVER_HOME/lib/tenants/omca/. ? Or should I edit the > settings.xml file in $CSPACE_JEESERVER_HOME/lib/tenants/omca/ to set the > correct server address for images? Or is this a change I make elsewhere? > > Thanks so much, > > Al > > Al Bersch > Digital Project Coordinator > Oakland Museum of California > 1000 Oak Street, Oakland, CA 94607 > abersch@museumca.org > 510-318-8468 > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >

AB

Al Bersch

Fri, Sep 20, 2013 9:54 PM

Hi Aron,

Thanks for this. That's great it's being worked out in 4.0.

Al

Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
----- Original Message -----

From: "Aron Roberts" aronroberts@gmail.com
To: "Al Bersch" abersch@museumca.org
Cc: "talk" talk@lists.collectionspace.org
Sent: Friday, September 20, 2013 2:41:39 PM
Subject: Re: [Talk] setting the server address for images in a new tenant

It's timely that you've mentioned this configuration piece, Al! We
ran into some similar issues recently, and as a result, configuring
the path to images has been streamlined in v4.0. (See the two links
below for the related discussion.)

For now, in v3.3, you can clone:

$CSPACE_JEESERVER_HOME/lib/tenants/omca/settings.xml
to
$CSPACE_JEESERVER_HOME/lib/tenants/omca/local-omca-settings.xml

and edit the <ims-url> value in the latter (local-omca-settings.xml)
file, changing the hostname from 'localhost' to the actual Internet
hostname at which you and others will be accessing your
CollectionSpace instance.

Aron

--

Simplifications to configuring the path for loading images, introduced
in recent work on CollectionSpace version 4.0:

http://wiki.collectionspace.org/display/collectionspace/Release+4.0#Release4.0-Imageloadingnolongerfailswhentheimagerepositoryhostnamehasnotbeenconfigured%28CSPACE4051

and

http://issues.collectionspace.org/browse/CSPACE-6183?focusedCommentId=41000&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-41000

On Fri, Sep 20, 2013 at 2:26 PM, Al Bersch abersch@museumca.org wrote:

Hello all,

It's me again at OMCA. I tried uploading a test image to a media handling
record in our tenant (omca). I got a message that my browser could not
connect to localhost:8180. I remembered resetting the server address when
installing CollectionSpace, under the "configure your tenant" section. After
looking, I realized that while I changed to server address in
local-core-settings.xml during installation, there wasn't a corresponding
local-omca-settings document in $CSPACE_JEESERVER_HOME/lib/tenants/omca/.

I checked, and images load fine in our core tenant.

Should I create a version of local-omca-settings.xml for our 'omca' tenant
directly in $CSPACE_JEESERVER_HOME/lib/tenants/omca/. ? Or should I edit the
settings.xml file in $CSPACE_JEESERVER_HOME/lib/tenants/omca/ to set the
correct server address for images? Or is this a change I make elsewhere?

Thanks so much,

Al

Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Hi Aron, Thanks for this. That's great it's being worked out in 4.0. Al Al Bersch Digital Project Coordinator Oakland Museum of California 1000 Oak Street, Oakland, CA 94607 abersch@museumca.org 510-318-8468 ----- Original Message ----- From: "Aron Roberts" <aronroberts@gmail.com> To: "Al Bersch" <abersch@museumca.org> Cc: "talk" <talk@lists.collectionspace.org> Sent: Friday, September 20, 2013 2:41:39 PM Subject: Re: [Talk] setting the server address for images in a new tenant It's timely that you've mentioned this configuration piece, Al! We ran into some similar issues recently, and as a result, configuring the path to images has been streamlined in v4.0. (See the two links below for the related discussion.) For now, in v3.3, you can clone: $CSPACE_JEESERVER_HOME/lib/tenants/omca/settings.xml to $CSPACE_JEESERVER_HOME/lib/tenants/omca/local-omca-settings.xml and edit the <ims-url> value in the latter (local-omca-settings.xml) file, changing the hostname from 'localhost' to the actual Internet hostname at which you and others will be accessing your CollectionSpace instance. Aron -- Simplifications to configuring the path for loading images, introduced in recent work on CollectionSpace version 4.0: http://wiki.collectionspace.org/display/collectionspace/Release+4.0#Release4.0-Imageloadingnolongerfailswhentheimagerepositoryhostnamehasnotbeenconfigured%28CSPACE4051 and http://issues.collectionspace.org/browse/CSPACE-6183?focusedCommentId=41000&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-41000 On Fri, Sep 20, 2013 at 2:26 PM, Al Bersch <abersch@museumca.org> wrote: > Hello all, > > It's me again at OMCA. I tried uploading a test image to a media handling > record in our tenant (omca). I got a message that my browser could not > connect to localhost:8180. I remembered resetting the server address when > installing CollectionSpace, under the "configure your tenant" section. After > looking, I realized that while I changed to server address in > local-core-settings.xml during installation, there wasn't a corresponding > local-omca-settings document in $CSPACE_JEESERVER_HOME/lib/tenants/omca/. > > I checked, and images load fine in our core tenant. > > Should I create a version of local-omca-settings.xml for our 'omca' tenant > directly in $CSPACE_JEESERVER_HOME/lib/tenants/omca/. ? Or should I edit the > settings.xml file in $CSPACE_JEESERVER_HOME/lib/tenants/omca/ to set the > correct server address for images? Or is this a change I make elsewhere? > > Thanks so much, > > Al > > Al Bersch > Digital Project Coordinator > Oakland Museum of California > 1000 Oak Street, Oakland, CA 94607 > abersch@museumca.org > 510-318-8468 > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >

AB

Al Bersch

Fri, Sep 20, 2013 10:19 PM

Hi again Aron - just wanted to let you know it worked - I cloned settings.xml to local-omca-settings, changed the server address, and now we have images.

Thanks!

Al

Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
----- Original Message -----

From: "Aron Roberts" aronroberts@gmail.com
To: "Al Bersch" abersch@museumca.org
Cc: "talk" talk@lists.collectionspace.org
Sent: Friday, September 20, 2013 2:41:39 PM
Subject: Re: [Talk] setting the server address for images in a new tenant

It's timely that you've mentioned this configuration piece, Al! We
ran into some similar issues recently, and as a result, configuring
the path to images has been streamlined in v4.0. (See the two links
below for the related discussion.)

For now, in v3.3, you can clone:

$CSPACE_JEESERVER_HOME/lib/tenants/omca/settings.xml
to
$CSPACE_JEESERVER_HOME/lib/tenants/omca/local-omca-settings.xml

and edit the <ims-url> value in the latter (local-omca-settings.xml)
file, changing the hostname from 'localhost' to the actual Internet
hostname at which you and others will be accessing your
CollectionSpace instance.

Aron

--

Simplifications to configuring the path for loading images, introduced
in recent work on CollectionSpace version 4.0:

http://wiki.collectionspace.org/display/collectionspace/Release+4.0#Release4.0-Imageloadingnolongerfailswhentheimagerepositoryhostnamehasnotbeenconfigured%28CSPACE4051

and

http://issues.collectionspace.org/browse/CSPACE-6183?focusedCommentId=41000&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-41000

On Fri, Sep 20, 2013 at 2:26 PM, Al Bersch abersch@museumca.org wrote:

Hello all,

It's me again at OMCA. I tried uploading a test image to a media handling
record in our tenant (omca). I got a message that my browser could not
connect to localhost:8180. I remembered resetting the server address when
installing CollectionSpace, under the "configure your tenant" section. After
looking, I realized that while I changed to server address in
local-core-settings.xml during installation, there wasn't a corresponding
local-omca-settings document in $CSPACE_JEESERVER_HOME/lib/tenants/omca/.

I checked, and images load fine in our core tenant.

Should I create a version of local-omca-settings.xml for our 'omca' tenant
directly in $CSPACE_JEESERVER_HOME/lib/tenants/omca/. ? Or should I edit the
settings.xml file in $CSPACE_JEESERVER_HOME/lib/tenants/omca/ to set the
correct server address for images? Or is this a change I make elsewhere?

Thanks so much,

Al

Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Hi again Aron - just wanted to let you know it worked - I cloned settings.xml to local-omca-settings, changed the server address, and now we have images. Thanks! Al Al Bersch Digital Project Coordinator Oakland Museum of California 1000 Oak Street, Oakland, CA 94607 abersch@museumca.org 510-318-8468 ----- Original Message ----- From: "Aron Roberts" <aronroberts@gmail.com> To: "Al Bersch" <abersch@museumca.org> Cc: "talk" <talk@lists.collectionspace.org> Sent: Friday, September 20, 2013 2:41:39 PM Subject: Re: [Talk] setting the server address for images in a new tenant It's timely that you've mentioned this configuration piece, Al! We ran into some similar issues recently, and as a result, configuring the path to images has been streamlined in v4.0. (See the two links below for the related discussion.) For now, in v3.3, you can clone: $CSPACE_JEESERVER_HOME/lib/tenants/omca/settings.xml to $CSPACE_JEESERVER_HOME/lib/tenants/omca/local-omca-settings.xml and edit the <ims-url> value in the latter (local-omca-settings.xml) file, changing the hostname from 'localhost' to the actual Internet hostname at which you and others will be accessing your CollectionSpace instance. Aron -- Simplifications to configuring the path for loading images, introduced in recent work on CollectionSpace version 4.0: http://wiki.collectionspace.org/display/collectionspace/Release+4.0#Release4.0-Imageloadingnolongerfailswhentheimagerepositoryhostnamehasnotbeenconfigured%28CSPACE4051 and http://issues.collectionspace.org/browse/CSPACE-6183?focusedCommentId=41000&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-41000 On Fri, Sep 20, 2013 at 2:26 PM, Al Bersch <abersch@museumca.org> wrote: > Hello all, > > It's me again at OMCA. I tried uploading a test image to a media handling > record in our tenant (omca). I got a message that my browser could not > connect to localhost:8180. I remembered resetting the server address when > installing CollectionSpace, under the "configure your tenant" section. After > looking, I realized that while I changed to server address in > local-core-settings.xml during installation, there wasn't a corresponding > local-omca-settings document in $CSPACE_JEESERVER_HOME/lib/tenants/omca/. > > I checked, and images load fine in our core tenant. > > Should I create a version of local-omca-settings.xml for our 'omca' tenant > directly in $CSPACE_JEESERVER_HOME/lib/tenants/omca/. ? Or should I edit the > settings.xml file in $CSPACE_JEESERVER_HOME/lib/tenants/omca/ to set the > correct server address for images? Or is this a change I make elsewhere? > > Thanks so much, > > Al > > Al Bersch > Digital Project Coordinator > Oakland Museum of California > 1000 Oak Street, Oakland, CA 94607 > abersch@museumca.org > 510-318-8468 > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >