Hi Kieran,

We are deploying on linux and use the "apache" user instead of appserver so 
things are a little different, but here's how I do it right now:

I use scp to copy the files to the server's /tmp directory (I'm switching to 
having hudson do this step automatically)

I then ssh into the box as my regular user and then  "sudo su - apache" to 
switch to being the correct user

I then copy the tar files from the /tmp directory to my "releases" directory, 
untar them and then link to extracted .woa files

Here's the commands:

cd ${HUDSON_HOME}/jobs/

scp 
TotalViewAdminD2W/lastSuccessful/archive/Projects/Application/dist/TotalViewAdminD2W-Application.tar.gz
 [email protected]:/tmp/

scp 
TotalViewAdminD2W/lastSuccessful/archive/Projects/Application/dist/TotalViewAdminD2W-WebServerResources.tar.gz
 [email protected]:/tmp/

ssh [email protected]

sudo su - apache

mkdir 
/data/servers/wo-totalview/Local/Library/WebObjects/Applications/releases/TotalViewAdminD2W/2010-11-15-12-04-36/

cp /tmp/TotalViewAdminD2W-Application.tar.gz 
/data/servers/wo-totalview/Local/Library/WebObjects/Applications/releases/TotalViewAdminD2W/2010-11-15-12-04-36/

tar -xzf 
/data/servers/wo-totalview/Local/Library/WebObjects/Applications/releases/TotalViewAdminD2W/2010-11-15-12-04-36/TotalViewAdminD2W-Application.tar.gz
 -C 
/data/servers/wo-totalview/Local/Library/WebObjects/Applications/releases/TotalViewAdminD2W/2010-11-15-12-04-36/

mkdir 
/data/app/apache-wo-2.2.4/htdocs/WebObjects/releases/TotalViewAdminD2W/2010-11-15-12-04-36/

cp /tmp/TotalViewAdminD2W-WebServerResources.tar.gz 
/data/app/apache-wo-2.2.4/htdocs/WebObjects/releases/TotalViewAdminD2W/2010-11-15-12-04-36/

tar -xzf 
/data/app/apache-wo-2.2.4/htdocs/WebObjects/releases/TotalViewAdminD2W/2010-11-15-12-04-36/TotalViewAdminD2W-WebServerResources.tar.gz
 -C 
/data/app/apache-wo-2.2.4/htdocs/WebObjects/releases/TotalViewAdminD2W/2010-11-15-12-04-36/

STOP APP

rm 
/data/servers/wo-totalview/Local/Library/WebObjects/Applications/TotalViewAdminD2W.woa

ln -s 
/data/servers/wo-totalview/Local/Library/WebObjects/Applications/releases/TotalViewAdminD2W/2010-11-15-12-04-36/TotalViewAdminD2W.woa/
 /data/servers/wo-totalview/Local/Library/WebObjects/Applications/

rm /data/app/apache-wo-2.2.4/htdocs/WebObjects/TotalViewAdminD2W.woa

ln -s 
/data/app/apache-wo-2.2.4/htdocs/WebObjects/releases/TotalViewAdminD2W/2010-11-15-12-04-36/TotalViewAdminD2W.woa
 /data/app/apache-wo-2.2.4/htdocs/WebObjects/

RESTART APP





On Nov 17, 2010, at 9:03 AM, Kieran Kelleher wrote:

> Hi all,
> 
> Like many of you, I have custom scripts that use ssh to deploy woa apps. 
> Scripts issue remote commands via ssh and script exec user's id_dsa has 
> corresponding id_dsa.pub in the remote server's auth keys for admin and root. 
> The problem is that root (apparently) is needed to set the chown on the woa 
> bundles to appserver:appserveradm, however I would like to get away from 
> needing root user remote ssh commands for security reasons.
> 
> Assuming you all use chown of appserver:appserveradm and chmod of 550 on your 
> deployed woa bundles (are you?), then the question is with respect to 
> non-interactive, passwordless, secure remote deployment (copy, untar, chown, 
> chmod) of WOAs, what user/ssh setup are you all using besides r...@remote, or 
> is r...@remote the only way?
> 
> Regards, Kieran
> 
> PS.
> I deploy to OS X client, OS X Server and Centos Linux 
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-deploy mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/webobjects-deploy/webobjects%40avendasora.com
> 
> This email sent to [email protected]
> 
> 

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to