WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org
View all threadsChad,
That clears up some things! However, I have questions about creating the
new tenant as cspace user. So if I log in as user cspace and ls in
terminal, this is the output I get (See screenshot 1):
cspace_source data examples.desktop initial_password.txt
Going into the cspace_source directory: cd cspace_source, ls, I get (See
screenshot 2):
application services ui
which is the collectionspace layer code.
The 4.1.1 creating a new tenant wiki doc
https://wiki.collectionspace.org/display/CSPACE41/Creating+your+new+tenant
tells me to checkout the application, services, and ui code from github
into a newly created directory and configure them for my new tenant.
However, I already have the source code in the cspace_source directory,
most likely made from the automated installer.
My question now is what steps do I need to do? Do I still need to configure
the source code from the cspace_source or should I create a new directory
and checkout the code?
Cheers,
RJ
On Tue, Jul 7, 2015 at 11:45 AM, Chad Nelson chad.nelson@lyrasis.org
wrote:
Hi RJ,
If you used the automated installer, then you indeed should be
performing actions as the cspace user, as, IIRC, those environment
variables are defined in the the cspace user's .bashrc.
Chad
From: RUIJING LI ruijing.li@berkeley.edu
Sent: Tuesday, July 7, 2015 2:32 PM
To: Chad Nelson
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] Trouble Configuring CSpace 4.1 Doc - Creating New
Tenant UI
Hi Chad,
I actually used the automated installer for 4.1 so I didn't go through
these pages.
Right now I am my own user checking out the source code on a directory I
made. Am I supposed to be user cspace instead?
Cheers,
RJ
On Tue, Jul 7, 2015 at 11:23 AM, Chad Nelson chad.nelson@lyrasis.org
wrote:
Hi RJ,
I think that error message happens when you don't have all of the
environment variables defined, and in the case I think it is specifically
the $CSPACE_JEE_SERVER env variable that is missing.
If you you already have CollectionSpace running, then you likely have
already been through:
but just make sure that the user you are running this command with
still has these env variables set.
Chad
From: Talk talk-bounces@lists.collectionspace.org on behalf of
RUIJING LI ruijing.li@berkeley.edu
Sent: Tuesday, July 7, 2015 1:32 PM
To: talk@lists.collectionspace.org
Subject: [Talk] Trouble Configuring CSpace 4.1 Doc - Creating New
Tenant UI
Hi all,
I'm trying to run through the configuration exercises for CSpace 4.1
and I'm in the process of creating my own tenant. After following all the
steps for configuring a new tenant for the ui layer, I ran into a problem
when trying to build my ui layer by calling this command:
mvn clean install
I tried giving sudo access and still could not overcome this. Any help
on what the resolution for the error is? I have attached the error message.
Cheers,
RJ
Hi Ruijing,
Good question! No, you don't need to check out the source code once again.
There's a JIRA to fix this unfortunate ambiguity in the docs:
https://issues.collectionspace.org/browse/CSPACE-6581
Aron
On Tue, Jul 7, 2015 at 12:07 PM, RUIJING LI ruijing.li@berkeley.edu wrote:
Chad,
That clears up some things! However, I have questions about creating the
new tenant as cspace user. So if I log in as user cspace and ls in
terminal, this is the output I get (See screenshot 1):
cspace_source data examples.desktop initial_password.txt
Going into the cspace_source directory: cd cspace_source, ls, I get (See
screenshot 2):
application services ui
which is the collectionspace layer code.
The 4.1.1 creating a new tenant wiki doc
https://wiki.collectionspace.org/display/CSPACE41/Creating+your+new+tenant
tells me to checkout the application, services, and ui code from github
into a newly created directory and configure them for my new tenant.
However, I already have the source code in the cspace_source directory,
most likely made from the automated installer.
My question now is what steps do I need to do? Do I still need to
configure the source code from the cspace_source or should I create a new
directory and checkout the code?
Cheers,
RJ
On Tue, Jul 7, 2015 at 11:45 AM, Chad Nelson chad.nelson@lyrasis.org
wrote:
Hi RJ,
If you used the automated installer, then you indeed should be
performing actions as the cspace user, as, IIRC, those environment
variables are defined in the the cspace user's .bashrc.
Chad
From: RUIJING LI ruijing.li@berkeley.edu
Sent: Tuesday, July 7, 2015 2:32 PM
To: Chad Nelson
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] Trouble Configuring CSpace 4.1 Doc - Creating New
Tenant UI
Hi Chad,
I actually used the automated installer for 4.1 so I didn't go through
these pages.
Right now I am my own user checking out the source code on a directory
I made. Am I supposed to be user cspace instead?
Cheers,
RJ
On Tue, Jul 7, 2015 at 11:23 AM, Chad Nelson chad.nelson@lyrasis.org
wrote:
Hi RJ,
I think that error message happens when you don't have all of the
environment variables defined, and in the case I think it is specifically
the $CSPACE_JEE_SERVER env variable that is missing.
If you you already have CollectionSpace running, then you likely have
already been through:
but just make sure that the user you are running this command with
still has these env variables set.
Chad
From: Talk talk-bounces@lists.collectionspace.org on behalf of
RUIJING LI ruijing.li@berkeley.edu
Sent: Tuesday, July 7, 2015 1:32 PM
To: talk@lists.collectionspace.org
Subject: [Talk] Trouble Configuring CSpace 4.1 Doc - Creating New
Tenant UI
Hi all,
I'm trying to run through the configuration exercises for CSpace 4.1
and I'm in the process of creating my own tenant. After following all the
steps for configuring a new tenant for the ui layer, I ran into a problem
when trying to build my ui layer by calling this command:
mvn clean install
I tried giving sudo access and still could not overcome this. Any help
on what the resolution for the error is? I have attached the error message.
Cheers,
RJ
And apologies, RJ, for this ... we're still doing some post-4.2 catch-up
on the docs. You and Regina are welcome to make corrections to the docs, as
you come across issues like this. (And no obligation! :-)
On Tue, Jul 7, 2015 at 12:09 PM, Aron Roberts aron@socrates.berkeley.edu
wrote:
Hi Ruijing,
Good question! No, you don't need to check out the source code once
again.
There's a JIRA to fix this unfortunate ambiguity in the docs:
https://issues.collectionspace.org/browse/CSPACE-6581
Aron
On Tue, Jul 7, 2015 at 12:07 PM, RUIJING LI ruijing.li@berkeley.edu
wrote:
Chad,
That clears up some things! However, I have questions about creating the
new tenant as cspace user. So if I log in as user cspace and ls in
terminal, this is the output I get (See screenshot 1):
cspace_source data examples.desktop initial_password.txt
Going into the cspace_source directory: cd cspace_source, ls, I get (See
screenshot 2):
application services ui
which is the collectionspace layer code.
The 4.1.1 creating a new tenant wiki doc
https://wiki.collectionspace.org/display/CSPACE41/Creating+your+new+tenant
tells me to checkout the application, services, and ui code from github
into a newly created directory and configure them for my new tenant.
However, I already have the source code in the cspace_source directory,
most likely made from the automated installer.
My question now is what steps do I need to do? Do I still need to
configure the source code from the cspace_source or should I create a new
directory and checkout the code?
Cheers,
RJ
On Tue, Jul 7, 2015 at 11:45 AM, Chad Nelson chad.nelson@lyrasis.org
wrote:
Hi RJ,
If you used the automated installer, then you indeed should be
performing actions as the cspace user, as, IIRC, those environment
variables are defined in the the cspace user's .bashrc.
Chad
From: RUIJING LI ruijing.li@berkeley.edu
Sent: Tuesday, July 7, 2015 2:32 PM
To: Chad Nelson
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] Trouble Configuring CSpace 4.1 Doc - Creating New
Tenant UI
Hi Chad,
I actually used the automated installer for 4.1 so I didn't go through
these pages.
Right now I am my own user checking out the source code on a directory
I made. Am I supposed to be user cspace instead?
Cheers,
RJ
On Tue, Jul 7, 2015 at 11:23 AM, Chad Nelson chad.nelson@lyrasis.org
wrote:
Hi RJ,
I think that error message happens when you don't have all of the
environment variables defined, and in the case I think it is specifically
the $CSPACE_JEE_SERVER env variable that is missing.
If you you already have CollectionSpace running, then you likely have
already been through:
but just make sure that the user you are running this command with
still has these env variables set.
Chad
From: Talk talk-bounces@lists.collectionspace.org on behalf of
RUIJING LI ruijing.li@berkeley.edu
Sent: Tuesday, July 7, 2015 1:32 PM
To: talk@lists.collectionspace.org
Subject: [Talk] Trouble Configuring CSpace 4.1 Doc - Creating New
Tenant UI
Hi all,
I'm trying to run through the configuration exercises for CSpace 4.1
and I'm in the process of creating my own tenant. After following all the
steps for configuring a new tenant for the ui layer, I ran into a problem
when trying to build my ui layer by calling this command:
mvn clean install
I tried giving sudo access and still could not overcome this. Any
help on what the resolution for the error is? I have attached the error
message.
Cheers,
RJ
Thanks Aron for the link, I'm reading it right now and I see a lot of work
has been made on this JIRA issue! I'm guessing the changes are reflected in
the current documentation (v4.2) and the unreleased documentation (v4.3).
However, I actually have a question about the easy way noted in the
documentation, which I believe is the fix for this JIRA.
https://wiki.collectionspace.org/display/UNRELEASED/Creating+your+new+tenant#Creatingyournewtenant-Theeasyway
When cd to application, and then running vim tenant.properties, am I
supposed to creating this file from scratch? There is no tenant.properties
hidden or listed in the application directory. Perhaps there could be some
clarification on where to find it?
And thanks to everyone for the rapid responses to my questions!
Cheers,
RJ
On Tue, Jul 7, 2015 at 12:11 PM, Aron Roberts aron@socrates.berkeley.edu
wrote:
And apologies, RJ, for this ... we're still doing some post-4.2 catch-up
on the docs. You and Regina are welcome to make corrections to the docs, as
you come across issues like this. (And no obligation! :-)
On Tue, Jul 7, 2015 at 12:09 PM, Aron Roberts aron@socrates.berkeley.edu
wrote:
Hi Ruijing,
Good question! No, you don't need to check out the source code once
again.
There's a JIRA to fix this unfortunate ambiguity in the docs:
https://issues.collectionspace.org/browse/CSPACE-6581
Aron
On Tue, Jul 7, 2015 at 12:07 PM, RUIJING LI ruijing.li@berkeley.edu
wrote:
Chad,
That clears up some things! However, I have questions about creating the
new tenant as cspace user. So if I log in as user cspace and ls in
terminal, this is the output I get (See screenshot 1):
cspace_source data examples.desktop initial_password.txt
Going into the cspace_source directory: cd cspace_source, ls, I get (See
screenshot 2):
application services ui
which is the collectionspace layer code.
The 4.1.1 creating a new tenant wiki doc
https://wiki.collectionspace.org/display/CSPACE41/Creating+your+new+tenant
tells me to checkout the application, services, and ui code from github
into a newly created directory and configure them for my new tenant.
However, I already have the source code in the cspace_source directory,
most likely made from the automated installer.
My question now is what steps do I need to do? Do I still need to
configure the source code from the cspace_source or should I create a new
directory and checkout the code?
Cheers,
RJ
On Tue, Jul 7, 2015 at 11:45 AM, Chad Nelson chad.nelson@lyrasis.org
wrote:
Hi RJ,
If you used the automated installer, then you indeed should be
performing actions as the cspace user, as, IIRC, those environment
variables are defined in the the cspace user's .bashrc.
Chad
From: RUIJING LI ruijing.li@berkeley.edu
Sent: Tuesday, July 7, 2015 2:32 PM
To: Chad Nelson
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] Trouble Configuring CSpace 4.1 Doc - Creating
New Tenant UI
Hi Chad,
I actually used the automated installer for 4.1 so I didn't go
through these pages.
Right now I am my own user checking out the source code on a
directory I made. Am I supposed to be user cspace instead?
Cheers,
RJ
On Tue, Jul 7, 2015 at 11:23 AM, Chad Nelson chad.nelson@lyrasis.org
wrote:
Hi RJ,
I think that error message happens when you don't have all of the
environment variables defined, and in the case I think it is specifically
the $CSPACE_JEE_SERVER env variable that is missing.
If you you already have CollectionSpace running, then you likely
have already been through:
but just make sure that the user you are running this command with
still has these env variables set.
Chad
From: Talk talk-bounces@lists.collectionspace.org on behalf of
RUIJING LI ruijing.li@berkeley.edu
Sent: Tuesday, July 7, 2015 1:32 PM
To: talk@lists.collectionspace.org
Subject: [Talk] Trouble Configuring CSpace 4.1 Doc - Creating New
Tenant UI
Hi all,
I'm trying to run through the configuration exercises for CSpace 4.1
and I'm in the process of creating my own tenant. After following all the
steps for configuring a new tenant for the ui layer, I ran into a problem
when trying to build my ui layer by calling this command:
mvn clean install
I tried giving sudo access and still could not overcome this. Any
help on what the resolution for the error is? I have attached the error
message.
Cheers,
RJ
Hi RJ,
Thanks for looking at that JIRA issue and the work that had been done
around it. Will follow-up on that, perhaps checking in with you at some
point, to see if we can resolve that issue.
The Ant targets that facilitate 'the easy way' to create a new tenant,
and the associated tenant.properties file, were introduced in v4.2. Did you
happen to say that you were working with v4.1?
Aron
On Tue, Jul 7, 2015 at 12:42 PM, RUIJING LI ruijing.li@berkeley.edu wrote:
Thanks Aron for the link, I'm reading it right now and I see a lot of work
has been made on this JIRA issue! I'm guessing the changes are reflected in
the current documentation (v4.2) and the unreleased documentation (v4.3).
However, I actually have a question about the easy way noted in the
documentation, which I believe is the fix for this JIRA.
https://wiki.collectionspace.org/display/UNRELEASED/Creating+your+new+tenant#Creatingyournewtenant-Theeasyway
When cd to application, and then running vim tenant.properties, am I
supposed to creating this file from scratch? There is no tenant.properties
hidden or listed in the application directory. Perhaps there could be some
clarification on where to find it?
And thanks to everyone for the rapid responses to my questions!
Cheers,
RJ
On Tue, Jul 7, 2015 at 12:11 PM, Aron Roberts aron@socrates.berkeley.edu
wrote:
And apologies, RJ, for this ... we're still doing some post-4.2
catch-up on the docs. You and Regina are welcome to make corrections to the
docs, as you come across issues like this. (And no obligation! :-)
On Tue, Jul 7, 2015 at 12:09 PM, Aron Roberts <aron@socrates.berkeley.edu
wrote:
Hi Ruijing,
Good question! No, you don't need to check out the source code once
again.
There's a JIRA to fix this unfortunate ambiguity in the docs:
https://issues.collectionspace.org/browse/CSPACE-6581
Aron
On Tue, Jul 7, 2015 at 12:07 PM, RUIJING LI ruijing.li@berkeley.edu
wrote:
Chad,
That clears up some things! However, I have questions about creating
the new tenant as cspace user. So if I log in as user cspace and ls in
terminal, this is the output I get (See screenshot 1):
cspace_source data examples.desktop initial_password.txt
Going into the cspace_source directory: cd cspace_source, ls, I get
(See screenshot 2):
application services ui
which is the collectionspace layer code.
The 4.1.1 creating a new tenant wiki doc
https://wiki.collectionspace.org/display/CSPACE41/Creating+your+new+tenant
tells me to checkout the application, services, and ui code from github
into a newly created directory and configure them for my new tenant.
However, I already have the source code in the cspace_source directory,
most likely made from the automated installer.
My question now is what steps do I need to do? Do I still need to
configure the source code from the cspace_source or should I create a new
directory and checkout the code?
Cheers,
RJ
On Tue, Jul 7, 2015 at 11:45 AM, Chad Nelson chad.nelson@lyrasis.org
wrote:
Hi RJ,
If you used the automated installer, then you indeed should be
performing actions as the cspace user, as, IIRC, those environment
variables are defined in the the cspace user's .bashrc.
Chad
From: RUIJING LI ruijing.li@berkeley.edu
Sent: Tuesday, July 7, 2015 2:32 PM
To: Chad Nelson
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] Trouble Configuring CSpace 4.1 Doc - Creating
New Tenant UI
Hi Chad,
I actually used the automated installer for 4.1 so I didn't go
through these pages.
Right now I am my own user checking out the source code on a
directory I made. Am I supposed to be user cspace instead?
Cheers,
RJ
On Tue, Jul 7, 2015 at 11:23 AM, Chad Nelson chad.nelson@lyrasis.org
wrote:
Hi RJ,
I think that error message happens when you don't have all of the
environment variables defined, and in the case I think it is specifically
the $CSPACE_JEE_SERVER env variable that is missing.
If you you already have CollectionSpace running, then you likely
have already been through:
but just make sure that the user you are running this command with
still has these env variables set.
Chad
From: Talk talk-bounces@lists.collectionspace.org on behalf of
RUIJING LI ruijing.li@berkeley.edu
Sent: Tuesday, July 7, 2015 1:32 PM
To: talk@lists.collectionspace.org
Subject: [Talk] Trouble Configuring CSpace 4.1 Doc - Creating New
Tenant UI
Hi all,
I'm trying to run through the configuration exercises for CSpace
4.1 and I'm in the process of creating my own tenant. After following all
the steps for configuring a new tenant for the ui layer, I ran into a
problem when trying to build my ui layer by calling this command:
mvn clean install
I tried giving sudo access and still could not overcome this. Any
help on what the resolution for the error is? I have attached the error
message.
Cheers,
RJ