Kimai
Lockdown per-user settings
A Kimai plugin to set the lockdown period per user
Kevin Papst
A Kimai plugin that allows to set the lockdown period per user.
See documentation for lockdown settings here.
Compatibility
The following table contains a comparison between plugin and required minimum Kimai version.
| Bundle version | Minimum Kimai version |
|---|---|
| 2.1.0 | 2.0.0 |
| 2.0.0 | 2.0.0 |
| 1.0.0 | 1.16.9 |
Installation
Copy files
Extract the ZIP file and upload the included directory and all files to your Kimai installation to the new directory:
var/plugins/LockdownPerUserBundle/Or you can clone it directly to the var/plugins/ directory of your Kimai installation:
cd kimai/var/plugins/
git clone https://github.com/Keleo/LockdownPerUserBundle.git LockdownPerUserBundleThe file structure needs to look like this afterwards:
var/plugins/
├── LockdownPerUserBundle
│ ├── LockdownPerUserBundle.php
| └ ... more files and directories follow here ...Clear cache
After uploading the files, Kimai needs to know about the new plugin. It will be found once the cache was re-built. Call these commands from the Kimai directory:
How to reload Kimai cache
bin/console kimai:reload --env=prod
It is not advised, but in case the above command fails you could try:
rm -r var/cache/prod/*
You might have to set file permissions afterwards:
Adjust file permission
You have to allow PHP (your webserver process) to write to var/ and it subdirectories.
Here is an example for Debian/Ubuntu, to be executed inside the Kimai directory:
chown -R :www-data .
chmod -R g+r .
chmod -R g+rw var/
You might not need these commands in a shared-hosting environment.
And you probably need to prefix them with sudo and/or the group might be called different from www-data.
Updates
Updating the plugin works exactly like the installation:
- Delete the directory
var/plugins/LockdownPerUserBundle/ -
Execute all installation steps again:
- Copy files
- Clear cache
