More tools

[zhicwu]

Add more tools / utilities for convenience, for examples:

• (re)schedule a job
• purge jackrabbit repository
• purge useless(mostly empty) files in repository
• automated daily/weekly backup
• clear cache

A better idea is probably to introduce a lightweight graphql server with most pentaho rest apis encasulated for ease of use.

[stonegatebi]

I'll be sharing a script that should help with this. It's an adaptation of CBF2's scripts which do some of the tasks you're showing. Specifically: https://github.com/webdetails/cbf2/blob/master/cbf2.sh#L368

[stonegatebi]

There are two things I'm doing in my adaptation of your project to a stack that make this mechanic more complete.

1. Bind mount the directory /pentaho/pentaho-server/pentaho-solutions/system/default-content to a local folder. (Any zips in that will on server start, get deployed to the repository, including any connections defined in the exportManifest.xml)
2. Introduced a ./backups/biserver folder on the dockerhost where these import-export packages could be stored for the case of proper whole platform backups and restores. (haven't built anything smart into a script to let people choose yet, but that's the plan.

You can see my thought process and current adaptations of your original work at:
https://github.com/usbrandon/docker-pentaho-stack

[zhicwu]

That's great!

I thought about exposing a deployment directory(not only for backups) and use import-export utility to get things done in a hot-deployment fashion.