3 ms·
TBH, its not Tomcat but the terrible application packaging by Atlasssian. There was a time when they had it right. A single WAR file. Just drop it in the tomcat
by desktopninja 6y ago
TBH, its not Tomcat but the terrible application packaging by Atlasssian. There was a time when they had it right. A single WAR file. Just drop it in the tomcat webapps folder and (depending on your preferred config) boom! Application deployed. Your data and configs lived in the path defined by JVM_OPTION -Duser.home | -Duser.dir or environment variable CONFLUENCE_HOME (IIRC). Backups were a breeze. Just archive the data folder. Updates were a breeze too! just replace the WAR and restart. Case in point Jenkins deployment in tomcat. Ahh super painless. Running multi tomcats on single host for application separation was as simple as CATALINA_HOME and CATALINA_BASE being set. Now we have a spaghetti monster called kubernetes that makes people think their apps will run better in it. Works for some but not for all. very much like that gym membership.