Alternate installation scenarios with Jive CLI

You can use the Jive CLI to customize your Jive installation, so it fits your needs.

If the default method of installation doesn't work for you, choose a scenario that makes sense for your environment.

Installing Jive without root access Create a new user who performs both the RPM install and runs the platform. You need to create this user in advance.
Installing in a different directory with a different user Install the RPM normally as root, but with an installation user and group other than jive, or an installation directory other than /usr/local/jive, or both.
Running Jive on port 80 without SSL Although not recommended in production, you can run Jive on port 80 without using SSL if you configure webapp proxy settings and you redirect ports using iptables.
Installing Jive without root access Create a new user who performs both the RPM install and runs the platform. You need to create this user in advance.
Installing in a different directory with a different user Install the RPM normally as root, but with an installation user and group other than jive, or an installation directory other than /usr/local/jive, or both.
Running Jive on port 80 without SSL Although not recommended in production, you can run Jive on port 80 without using SSL if you configure webapp proxy settings and you redirect ports using iptables.