This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
computing:munin [2019/12/30 02:13] – oemb1905 | computing:munin [2021/11/05 18:37] (current) – oemb1905 | ||
---|---|---|---|
Line 11: | Line 11: | ||
------------------------------------------- | ------------------------------------------- | ||
- | This tutorial is for users of Debian who have already established a host with TLS/LAMP and want to create a [[http:// | + | This tutorial is for users of Debian who have already established a host with TLS/LAMP and want to create a [[http:// |
- | sudo apt install munin | + | sudo apt install munin libcgi-fast-perl libapache2-mod-fcgid |
- | sudo apt install | + | |
| | ||
If you have WordPress CMS enabled on this same server, or Nextcloud, etc., then you will likely have the fast cgi module enabled already. | If you have WordPress CMS enabled on this same server, or Nextcloud, etc., then you will likely have the fast cgi module enabled already. | ||
Line 35: | Line 34: | ||
use_node_name yes | use_node_name yes | ||
- | Now that you are done with that, we need to enable an apache virtual host configuration file that resides within the base configuration files for Munin. | + | Create the directory for munin, apply appropriate permissions. |
+ | |||
+ | mkdir / | ||
+ | chown munin:munin / | ||
+ | |||
+ | Now configure the apache virtual host that munin provides, and configure overrides so it can populate that directory with its webpages/ | ||
sudo nano apache24.conf | sudo nano apache24.conf | ||
- | <Alias /munin / | + | <Alias /munin /var/www/ |
- | After that, you need to change the override status from: | + | After that, you need to change the override status, in the //primary block//, |
< | < | ||
Line 49: | Line 53: | ||
To: | To: | ||
- | < | + | < |
- | Require all **granted** | + | Require all granted |
Options FollowSymLinks SymLinksIfOwnerMatch | Options FollowSymLinks SymLinksIfOwnerMatch | ||
</ | </ | ||
Line 58: | Line 62: | ||
sudo systemctl restart munin-node | sudo systemctl restart munin-node | ||
sudo systemctl restart apache2 | sudo systemctl restart apache2 | ||
- | | + | |
+ | The first thing you can do to verify your setup worked is navigate to the munin alias on your terminal and if it populated the munin webpages inside that directory, then the munin-node is working properly with apache. | ||
+ | |||
+ | cd / | ||
+ | ls -lah | ||
+ | <If you succeed, munin will populate this directory with .html files and a few directories.> | ||
That's all that is required for a directory set-up (not a node), so navigate to the site now as follows: | That's all that is required for a directory set-up (not a node), so navigate to the site now as follows: | ||
https:// | https:// | ||
| | ||
- | If you need to set up a node instead of a directory, then you need to provide additional configurations beyond what was discussed here, but this should get you started. My instance is located here: | + | This should get you started! My instance is located here: |
https:// | https:// | ||
Line 69: | Line 79: | ||
Happy hacking! | Happy hacking! | ||
- | --- // | + | --- // |