Overview
Request 646036 accepted
New package need for icingaweb2-module-graphite
- update to 1.1.4
- rebase spec
- drop usr-share.patch because no more need
- add graphite-web-path.patch to preallocate graphite paths.
- use apache.conf from upstream
- change initial database commond to wich are descriped in
upstream doc.
- Fix startup error with change of rights for /var/lib/graphite/storage
- Ensure /var/lib/graphite/graphite.db is writable by apache user
- Prefer /usr/share/graphite, /etc/graphite etc. to match python
site-packages directory naming, and also what calamari-server expects
(this obsoletes earlier graphite-web change).
- Ensure `manage.py syncdb` is invoked correctly on first install
- Generate random SECRET_KEY on install
- Use /usr/share/graphite-web instead of /usr/share/graphite
- Initial SUSE packaging
Request History
ecsos created request
New package need for icingaweb2-module-graphite
- update to 1.1.4
- rebase spec
- drop usr-share.patch because no more need
- add graphite-web-path.patch to preallocate graphite paths.
- use apache.conf from upstream
- change initial database commond to wich are descriped in
upstream doc.
- Fix startup error with change of rights for /var/lib/graphite/storage
- Ensure /var/lib/graphite/graphite.db is writable by apache user
- Prefer /usr/share/graphite, /etc/graphite etc. to match python
site-packages directory naming, and also what calamari-server expects
(this obsoletes earlier graphite-web change).
- Ensure `manage.py syncdb` is invoked correctly on first install
- Generate random SECRET_KEY on install
- Use /usr/share/graphite-web instead of /usr/share/graphite
- Initial SUSE packaging
lrupp accepted request
There is still a potential to overwrite an existing SECRET_KEY in %post. But the rest looks good: welcome in server:monitoring !
