Like in simmilar question, we are also evaluating pros and cons of .bin and tar.gz installation of Jira and Confluence but for Linux.
From installation perspective, are there any benefits of using .bin installer over tar.gz?
Currently we are using tar.gz installation. Are you recommend switching to .bin installer and why?
Daniel,
As explained by Ann in the previous thread you've mentioned, there are few benefits of using .bin installer over .tar.gz
Its easy and quick
No need to mention the home dir path in config files
No need to download and setup Java/JRE and mention the JAVA home in config files
Use by default ports or use custom ports without modifying the server.xml file
It installs the service script so the confluence and jira starts up automatically when the server boots up or reboots
Also, useful in case of upgrades
In case of using tar.gz - you will have to do the above tasks manually.
-Shankar
Thanks, this is usefull. In addition, do you know are there any database related pros and cons with using binary vs archive installation.
Like DB connection, setup and so on?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Both options run a bit of an install for you, just enough to get Confluence running. Confluence then takes over, and runs a setup process. This setup process is the same whatever installer you've used, and one of the steps in it is "please give me a database to work with".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm a little confused. Why does the archive option exist at all?
I'm having a LOT of difficulty configuring an installation on Ubuntu 18
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The binary installers are built on top of the archive and they're intended to make it easier for manual installs and upgrades. The archives are more of a basic thing, better for people who want to script and automate deployments, or have customised installations - Adaptavist (and many of our customers) have processes that fetch archives and spin up instances automatically - the installers would be a nightmare to code these for.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks! That makes a ton of sense.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.