ilia
f4155cf820
- Added a new section in `REBUILD.md` for watching activity logs with usage instructions for different modes. - Updated `rebuild.sh` to dynamically set the log file path and provide clearer log viewing instructions. - Enhanced `watch-activity.sh` to support monitoring both systemd journal logs and specified log files, with improved error handling and user guidance.
1.3 KiB
1.3 KiB
Rebuild Scripts
Quick Start
Production Mode (Recommended for testing)
./rebuild.sh prod
# or just
./rebuild.sh
Development Mode (Hot reload)
./rebuild.sh dev
What it does
- Kills all processes - Stops any running Node/Next.js processes
- Frees ports - Ensures ports 3000 and 3003 are available
- Cleans build artifacts - Removes
.next, cache files, etc. - Rebuilds (production only) - Runs
npm run build - Starts server - Runs in foreground (dev) or background (prod)
Viewing Logs
Production Mode
tail -f /tmp/mirrormatch-server.log
Development Mode
Logs appear directly in the terminal (foreground mode)
Watching Activity Logs
# If using rebuild.sh (production mode)
./watch-activity.sh /tmp/mirrormatch-server.log
# If using systemd service
./watch-activity.sh
# Or specify custom log file
./watch-activity.sh /path/to/your/logfile.log
Manual Commands
If you prefer to run commands manually:
# Kill everything
sudo fuser -k 3000/tcp
killall -9 node
pkill -f "next"
sleep 2
# Clean
cd /home/beast/Code/mirrormatch
rm -rf .next node_modules/.cache
# Rebuild (production)
npm run build
# Start
NODE_ENV=production npm run start > /tmp/server.log 2>&1 &
# or for dev
NODE_ENV=development npm run dev