You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Aryeh Friedman <ar...@gmail.com> on 2014/07/07 11:48:37 UTC
preserving content not in the war
I have auto deploy on (and want to keep it that way) but I also have
content that is not a part of the war and do not want it deleted on a new
reploy... namely I have xxx/content/.... and I do not want that erased on
war deployment.... I tried symlinks and it nuked all the sym linked data on
deploy
--
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
Re: preserving content not in the war
Posted by "Mark H. Wood" <mw...@IUPUI.Edu>.
On Mon, Jul 07, 2014 at 05:48:37AM -0400, Aryeh Friedman wrote:
> I have auto deploy on (and want to keep it that way) but I also have
> content that is not a part of the war and do not want it deleted on a new
> reploy... namely I have xxx/content/.... and I do not want that erased on
> war deployment.... I tried symlinks and it nuked all the sym linked data on
> deploy
I would place the content elsewhere -- outside of Tomcat's directories
altogether -- and pass its path in through the environment.
--
Mark H. Wood, Lead System Programmer mwood@IUPUI.Edu
Machines should not be friendly. Machines should be obedient.
Re: preserving content not in the war
Posted by Aryeh Friedman <ar...@gmail.com>.
Forgot to mention I *DO* want to update the java and such in the war though
On Mon, Jul 7, 2014 at 5:48 AM, Aryeh Friedman <ar...@gmail.com>
wrote:
> I have auto deploy on (and want to keep it that way) but I also have
> content that is not a part of the war and do not want it deleted on a new
> reploy... namely I have xxx/content/.... and I do not want that erased on
> war deployment.... I tried symlinks and it nuked all the sym linked data on
> deploy
>
> --
> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
>
--
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org