debfranca
/
ansible-roles
forked from ISTI-ansible-roles/ansible-roles
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
ansible-roles/d4s_user_services_perms
History
Andrea Dell'Amico ec51482863 library/roles: d4s_user_services_perms, fixes to the tasks so that they work if we have multiple tomcat installations but only a subset of them have smartgears installed. 
library/roles/smartgears/smartgears/templates/container.xml.j2: Cosmetic fix.
 		2017-01-25 16:03:23 +01:00
..
defaults library/roles/d4s_user_services_perms: Change the gcore task to handle the case of multiple users. 2016-11-10 14:04:14 +01:00
tasks library/roles: d4s_user_services_perms, fixes to the tasks so that they work if we have multiple tomcat installations but only a subset of them have smartgears installed. 2017-01-25 16:03:23 +01:00
templates library/roles/d4s_user_services_perms: Add a series of task that configure a generic service to be managed by an unprivileged user. 2016-09-27 15:35:33 +02:00
README.md library/roles/d4s_user_services_perms: Add a series of task that configure a generic service to be managed by an unprivileged user. 2016-09-27 15:35:33 +02:00

README.md

Four different scenarios are covered.

  1. One smartgears tomcat instance, installed inside the user’s home
  2. One or more tomcat instances, each instance installed inside its user’s home
  3. One service, not tomcat based, installed inside the user’s home
  4. One service, installed inside the user’s home, not managed by other ansible playbooks (only the user is created)

Important note: the variable ‘http_port(s)’ needs to be defined earlier in the calling playbook.

What the role does:

  • Installs the sudoers config that permits the user to restart the service
  • Installs the script that allows the user to start and stop the service without using the full path
  • Installs the README file that explains where the options files are placed and how start/stop the service
  • The default open files limits are increased