Re: Using symbolic links for deployment (was: First Deployment Help)
Re: Using symbolic links for deployment (was: First Deployment Help)
- Subject: Re: Using symbolic links for deployment (was: First Deployment Help)
- From: Ian Joyner <email@hidden>
- Date: Fri, 4 May 2007 09:28:29 +1000
On 04/05/2007, at 1:11 AM, Mike Schrag wrote: On May 2, 2007, at 1:59 PM, Ian Joyner wrote: I have found that you only need a symbolic link in the /Library/WebServer/Documents/WebObjects folder:
ln -s /Library/WebObjects/MyApp.woa MyApp.woa
That way you never have to worry about copying it there every time. Has been working fine for us for the last 12 months, can any one see any problems with this?
It's not a general deployment strategy because it doesn't work under Windows or when the app and Web servers are different machines.
But when the app and Web servers are the same Unix machine, using a symbolic link seems fine to me as long as you don't break the link by relocating or renaming the app.
We only deploy on Macs – mainly to save our support guys all the Windows headaches, so sym links are OK in that particular case. I would recommend specifically linking WebServerResources. Otherwise someone can just download your jar files and potentially worse, your Properties files which might have passwords in them. It is MUCH safer to create MyApp.woa/Contents and then symlink WSR inside of it.
An excellent tip, I'll try that! If the whole woa file has a copy in WebServer/Documents people would have access to the jars and properties files anyway n'est pas?
Ian |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden