Kumaのインストール方法 - Ubuntu 20.04での自己ホスト型Uptime Robotの代替

useradd -m -s /bin/bash johndoe

passwd johndoe

usermod -aG sudo johndoe

su - johndoe

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash

source ~/.bashrc

command -v nvm

nvm --help

Node Version Manager (v0.38.0)  
  
Note:  refers to any version-like string nvm understands. This includes:  
  - full or partial version numbers, starting with an optional "v" (0.10, v0.1.2, v1)  
  - default (built-in) aliases: node, stable, unstable, iojs, system  
  - custom aliases you define with `nvm alias foo`  
  
  Any options that produce colorized output should respect the `--no-colors` option.  
  
Usage:  
  nvm --help                             Show this message  
    --no-colors                           Suppress colored output  
  
.....  
  
Note:  
  to remove, delete, or uninstall nvm - just remove the `$NVM_DIR` folder (usually `~/.nvm`)

nvm install --lts

node --version  
npm --version

# nodejs version  
v14.17.4  
  
# npm version  
6.14.14

git clone https://github.com/louislam/uptime-kuma.git

cd uptime-kuma/  
npm run setup

npm install pm2

pm2 start npm --name uptime-kuma -- run start-server -- --port=3001 --hostname=127.0.0.1

pm2 status

pm2 logs

pm2 monit

pm2 startup

sudo env PATH=$PATH:/home/johndoe/.nvm/versions/node/v14.17.4/bin /home/johndoe/.nvm/versions/node/v14.17.4/lib/node_modules/pm2/bin/pm2 startup systemd -u johndoe --hp /home/johndoe

pm2 save

sudo systemctl is-enabled pm2-johndoe

sudo systemctl status pm2-johndoe

? pm2-johndoe.service - PM2プロセスマネージャー  
     Loaded: loaded (/etc/systemd/system/pm2-johndoe.service; enabled; vendor preset: enabled)  
     Active: active (running) since Tue 2021-08-10 01:52:37 UTC; 3min 57s ago  
       Docs: https://pm2.keymetrics.io/  
   Main PID: 745 (PM2 v5.1.0: God)  
      Tasks: 34 (limit: 2343)  
     Memory: 120.4M  
     CGroup: /system.slice/pm2-johndoe.service  
             ??745 PM2 v5.1.0: God Daemon (/home/johndoe/.pm2)  
             ??772 npm  
             ??873 sh -c node server/server.js "--port=3001" "--hostname=127.0.0.1"  
             ??874 node server/server.js --port=3001 --hostname=127.0.0.1  
  
Aug 10 01:52:36 ubuntu64 pm2[633]: [PM2] Spawning PM2 daemon with pm2_home=/home/johndoe/.pm2  
Aug 10 01:52:37 ubuntu64 pm2[633]: [PM2] PM2 Successfully daemonized  
Aug 10 01:52:37 ubuntu64 pm2[633]: [PM2] Resurrecting  
Aug 10 01:52:37 ubuntu64 pm2[633]: [PM2] Restoring processes located in /home/johndoe/.pm2/dump.pm2  
Aug 10 01:52:37 ubuntu64 pm2[633]: [PM2] Process /home/johndoe/.nvm/versions/node/v14.17.4/bin/npm restored

sudo apt install apache2

sudo a2enmod ssl proxy proxy_ajp proxy_wstunnel proxy_http rewrite deflate headers proxy_balancer proxy_connect proxy_html

sudo nano /etc/apache2/sites-available/uptime-kuma.conf

  
  ServerName uptime.example.net  
  
  ProxyPass / http://localhost:3001/  
  RewriteEngine on  
  RewriteCond %{HTTP:Upgrade} websocket [NC]  
  RewriteCond %{HTTP:Connection} upgrade [NC]  
  RewriteRule ^/?(.*) "ws://localhost:3001/$1" [P,L]  

sudo a2ensite uptime-kuma

sudo apachectl configtest

sudo systemctl restart apache2

sudo apt install python3-certbot-apache

sudo certbot --apache yourdomain.com

Saving debug log to /var/log/letsencrypt/letsencrypt.log  
Plugins selected: Authenticator apache, Installer apache  
Enter email address (used for urgent renewal and security notices) (Enter 'c' to  
cancel): [email protected]

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
Please read the Terms of Service at  
https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must  
agree in order to register with the ACME server at  
https://acme-v02.api.letsencrypt.org/directory  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
(A)gree/(C)ancel: A

Would you be willing to share your email address with the Electronic Frontier  
Foundation, a founding partner of the Let's Encrypt project and the non-profit  
organization that develops Certbot? We'd like to send you email about our work  
encrypting the web, EFF news, campaigns, and ways to support digital freedom.  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
(Y)es/(N)o: N

Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
1: No redirect - Make no further changes to the webserver configuration.  
2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for  
new sites, or if you're confident your site works on HTTPS. You can undo this  
change by editing your web server's configuration.  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
Congratulations! You have successfully enabled https://uptime.example.net  
  
You should test your configuration at:  
https://www.ssllabs.com/ssltest/analyze.html?d=uptime.example.net  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
  
IMPORTANT NOTES:  
  - Congratulations! Your certificate and chain have been saved at:  
   /etc/letsencrypt/live/uptime.example.net/fullchain.pem  
   Your key file has been saved at:  
   /etc/letsencrypt/live/uptime.example.net/privkey.pem  
   Your cert will expire on 2021-10-10. To obtain a new or tweaked  
   version of this certificate in the future, simply run certbot again  
   with the "certonly" option. To non-interactively renew *all* of  
   your certificates, run "certbot renew"  
  - Your account credentials have been saved in your Certbot  
   configuration directory at /etc/letsencrypt. You should make a  
   secure backup of this folder now. This configuration directory will  
   also contain certificates and private keys obtained by Certbot so  
   making regular backups of this folder is ideal.  
  - If you like Certbot, please consider supporting our work by:  
  
   Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate  
   Donating to EFF:                https://eff.org/donate-le  
  
  - We were unable to subscribe you the EFF mailing list because your  
   e-mail address appears to be invalid. You can try again later by  
   visiting https://act.eff.org.