Neontribe is a software development company. We're agile and user-centered in our design and development work, producing websites and apps.
This plugin allows time to be logged from ChromePlugin tickets into a Kimai instance.
Clone the repo into your plugins folder of a Kimai installation (it must be in a folder named
cd /path/to/kimai cd var/plugins clone https://github.com/tobybatch/ChromeKimaiBridge.git ChromePluginBundle
Reload the plugins:
cd /path/to/kimai ./bin/console kimai:reload
Right now it’s not in the chrome store, it will be, but for now there is a packed crx file in the var/plugins/ChromePluginBundle/Resources/ folder. Because the extension needs to access your Kimai instance it has to have the
hosts: https://*/* permissions which google (quite correctly) finds very permissive and this holds up getting it into the store.
Get it here.
This will add a new icon to your chrome extensions. The first time you click it you will launch the options page. Here you must add a URL pointing to the web root of you Kimai server. Save the options and then you can use the extension.
Time can be logged directly against a project from a Github issue/project or Trello board.
The external board id accepts multiple board references in a comma seperated list.
Extract the ZIP file and upload the included directory and all files to your Kimai installation to the new directory:
The file structure needs to look like this afterwards:
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:
It is not advised, but in case the above command fails you could try:
You might have to set file permissions afterwards:
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):
Test Kimai before executing these commands (they are likely not required in a shared-hosting environment).
You probably need to prefix them with
the group might be called different than
Updating the plugin works exactly like the installation: