Breaking changes: Starting with version 0.4.x jottad will be run as the user jottad. If you upgrade from 0.3.x or lower this will cause jottad to not being able to read the old configuration directory located in /root/.jottad. To mitigate this issue move all files and folders from /root/.jottad to jottad users home, located in /var/lib/jottad and recursive chown to user jottad and group jottad:

mv /root/.jottad/* /var/lib/jottad
chown -R jottad.jottad /var/lib/jottad
systemctl restart jottad

Installation

Save the following to /etc/yum.repos.d/JottaCLI.repo :

[jotta-cli]
name=Jottacloud CLI
baseurl=https://repo.jotta.us/redhat
gpgcheck=1
gpgkey=https://repo.jotta.us/RPM-GPG-KEY-jotta-cli

Install the package jotta-cli :

sudo yum install jotta-cli

We supply init scripts for your running flavour (systemd,upstart,sysvinit)
After installation (and on upgrade) you can start or restart the CLI-daemon using your systems init flavour, i.e.:

sudo systemctl start jottad

To make sure it starts on boot:

sudo systemctl enable jottad

To get started:

jotta-cli help

NB:

Running as a not-root user by default will decrease security vulnerabilities but will also have the effect of jottad not being able to read any files not accessable by the jottad user or group. To mitigate this either:

  • Change the running user of the process by editing /etc/systemd/system/jottad.service , /etc/init/jottad.conf or /etc/init.d/jottad 
  • Make the files accessable by adding the jottad user to a group with access to the files
  • chmod -ing the files to make them accessable
Did this answer your question?