Add contributor edition
- added viaf resolver
- improve contributors list display
- add update of document objects
- propagate update to back office
- update back office
- add bo-client to back office
- setup language initializer
- add options mechanism
- add language information in language list
- add lexvo resolver service + api
- add language and lexvo resolver to js app
- correct env template
- refresh bootstrap
- download google font
- add version information
- update dev virtual machine to centos7
- add a readme + clean folders
- add local .env file to start commands
# PUPPI LOG README
Documentation and examples related to the puppi action log
## SYNOPSIS (cli)
puppi log [topic] [-i]
## EXAMPLES (cli)
Tails (tail -10f) all the known logs.
puppi log
Tails only the logs related to the given topic
puppi log apache
Choose interactively which logs to show
puppi log
Grep the output with the string defined
puppi log -g <string>
## EXAMPLES (puppet)
The basic define related to a log is:
puppi::log
it creates a file in /etc/puppi/logs/ with one or more logs paths.
A simple, operating system aware, example might be:
puppi::log { 'auth':
description => 'Users and authentication' ,
log => $::operatingsystem ? {
redhat => '/var/log/secure',
darwin => '/var/log/secure.log',
ubuntu => ['/var/log/user.log','/var/log/auth.log'],
}
}
but also something that uses variables Puppet already knows
puppi::log { "tomcat-${instance_name}":
log => "${tomcat::params::storedir}/${instance_name}/logs/catalina.out"
}
EXAMPLES (with example42 puppet modules)
If you use the old Example42 modules set you get automatically many service related logs out of the box to be used with Puppi One.
NextGen modules are supposed to provide puppi log intergration on Puppi Two (TO DO)