svn - Source control, live server best practices -


i'm working on project we're using tomcat , svn. have repo checked out in different directory tomcat webapps directory (were code server uses lives). told bad idea checkout copy of repository in webapps directory. how can test live server code when code server sees in /webapps , repo located elsewhere? have been having make changes in both repo , webapps directory. what's solution this?

not sure if it's best practice i've been using (at least) 2 techniques:

  1. use context descriptor file

this file in $tomcat/conf directory tells tomcat app , what's called (ie. can change context, have app called my-best-app-ever , deploy on localhost:8080/my-second-best-app-ever.

  1. make symlink of code webapps directory test instance of tomcat.

this quick , effective , hassle-free. not meant teams, localhost.


Comments

Popular posts from this blog

javascript - RequestAnimationFrame not working when exiting fullscreen switching space on Safari -

Python ctypes access violation with const pointer arguments -