updating readme without email

This commit is contained in:
Nasir Anthony Montalvo
2026-01-27 21:25:07 -06:00
parent 60d619502c
commit 3fd32b57e3

View File

@@ -41,7 +41,6 @@ This site is built with [CollectionBuilder-CSV](https://collectionbuilder.github
**How it works:** **How it works:**
- A cron job runs every minute checking for new commits - A cron job runs every minute checking for new commits
- When changes are detected, it pulls and rebuilds the site - When changes are detected, it pulls and rebuilds the site
- You receive an email notification when deployment completes
- Takes ~10-30 seconds to build and deploy - Takes ~10-30 seconds to build and deploy
**Usage:** **Usage:**
@@ -51,7 +50,7 @@ git add .
git commit -m "Update collection metadata" git commit -m "Update collection metadata"
git push gitea main git push gitea main
# Wait ~1 minute, check your email, site is live! # Wait ~1 minute, site is live!
``` ```
#### 2. Manual SSH Deploy 🔧 #### 2. Manual SSH Deploy 🔧
@@ -112,8 +111,7 @@ exit
4. If yes: pulls new code and runs `deploy.sh` 4. If yes: pulls new code and runs `deploy.sh`
5. `deploy.sh` runs `bundle exec rake deploy` (builds site) 5. `deploy.sh` runs `bundle exec rake deploy` (builds site)
6. Built site is synced to `/var/www/my_webapp/www/` (live directory) 6. Built site is synced to `/var/www/my_webapp/www/` (live directory)
7. Email notification sent to 1800nasi@tutamail.com 7. Site is live!
8. Site is live!
**Why this approach?** **Why this approach?**
- No PHP required (keeps site purely static) - No PHP required (keeps site purely static)
@@ -256,25 +254,6 @@ sudo journalctl -u ssh -n 50 | grep my_webapp
--- ---
### Email Notifications Not Working
**Check mail service:**
```bash
sudo systemctl status postfix
```
**Test email manually:**
```bash
echo "Test deployment notification" | mail -s "Test from {B/qKC}" 1800nasi@tutamail.com
```
**Check mail logs:**
```bash
sudo tail -50 /var/log/mail.log
```
---
### Emergency Rollback ### Emergency Rollback
If a deployment breaks the site, rollback to a previous version: If a deployment breaks the site, rollback to a previous version: