Skip to content

DEPLOYMENT_STATUS.md

Latest commit

 

History

History
80 lines (63 loc) · 2.24 KB

DEPLOYMENT_STATUS.md

File metadata and controls

80 lines (63 loc) · 2.24 KB

Deployment Status

Last Updated: December 1, 2025 - 22:52 UTC

✅ Successfully Deployed

Frontend

  • Build Date: December 1, 2025 - 22:39 UTC
  • Location: /home/ishaglcy/public_html/yeladim.church/
  • Status: ✅ Deployed and accessible
  • Features:
    • Mobile responsive design
    • Video streaming (YouTube/Discord)
    • Quiz system (Teacher & Student modes)
    • Scripture Notebook
    • Drawing Pad
    • All components connected to backend API

Backend API

  • Status: ✅ Running (PID: 3999956)
  • Port: 3001
  • Location: /home/ishaglcy/public_html/yeladim.church/api/
  • Log File: /tmp/yeladim-api.log
  • Endpoints:
    • Health: http://localhost:3001/health
    • Quiz: http://localhost:3001/api/quiz/*
    • Notes: http://localhost:3001/api/notes/*

Apache Configuration

  • Proxy: Configured via .htaccess to proxy /api and /health to backend
  • React Router: Configured to serve index.html for all client-side routes

Quick Commands

Check Backend Status

curl http://localhost:3001/health

View Backend Logs

cat /tmp/yeladim-api.log

Restart Backend

# Find and kill the process
ps aux | grep "node server.js" | grep -v grep | awk '{print $2}' | xargs kill

# Start it again
cd /home/ishaglcy/public_html/yeladim.church/api
nohup node server.js > /tmp/yeladim-api.log 2>&1 &

Deploy Frontend Updates

cd /home/ishaglcy/public_html/yeladim.church
./deploy-frontend.sh

File Locations

  • Frontend Source: /home/ishaglcy/public_html/yeladim.church/src/
  • Build Output: /home/ishaglcy/public_html/yeladim.church/dist/
  • Production Files: /home/ishaglcy/public_html/yeladim.church/ (root)
  • Backend: /home/ishaglcy/public_html/yeladim.church/api/
  • Database: /home/ishaglcy/public_html/yeladim.church/api/data.json

API Configuration

The frontend automatically uses:

  • Development: http://localhost:3001
  • Production: https://yeladim.church (proxied through Apache)

Notes

  • Backend is running as a background process (nohup)
  • For production, consider using PM2 or systemd for process management
  • Backend data is stored in JSON file: api/data.json
  • All API endpoints support CORS for the configured origins
⚡