- Backend is running on Railway
- Backend URL configured in
admin/app.js - Admin credentials set in backend
.env - CORS enabled in backend
- Admin folder has all files (index.html, app.js, style.css, netlify.toml)
- Go to https://app.netlify.com/
- Click "Add new site" → "Import an existing project"
- Select GitHub repo:
Enatega_website_chatbot - Set base directory:
admin - Leave build command empty
- Set publish directory:
. - Click "Deploy site"
- Wait for deployment (1-2 minutes)
- Open Netlify URL
- Login with credentials from backend
.env - Verify files list loads
- Create a test file
- Edit the test file
- Delete the test file
- Check status bar shows correct data
- Open browser console (F12) - no errors
- Change
ADMIN_PASSWORDin backend.env - Restart Railway service
- Test login with new password
- (Optional) Restrict CORS to Netlify domain only
- Save Netlify URL
- Share credentials with team
- Update project README with admin URL
- Set up custom domain (optional)
- Enable Netlify analytics (optional)
- Check Railway dashboard - service running?
- Test backend:
curl https://enategawebsitechatbot-production.up.railway.app/healthz - Check browser console for errors
- Verify API_URL in
admin/app.jsmatches Railway URL - Check Railway logs for API errors
Test backend:
curl https://enategawebsitechatbot-production.up.railway.app/healthzDeploy via CLI:
cd admin
netlify deploy --prodCheck Railway logs:
railway logs --tail- Backend API: https://enategawebsitechatbot-production.up.railway.app
- Admin API: https://enategawebsitechatbot-production.up.railway.app/admin/api
- Netlify Dashboard: https://app.netlify.com/
- Railway Dashboard: https://railway.app/
Username: admin
Password: SecurePassword123!
If you get stuck:
- Check
DEPLOYMENT_SUMMARY.mdfor detailed troubleshooting - Check
ADMIN_DEPLOYMENT_GUIDE.mdfor full guide - Check browser console (F12) for errors
- Check Railway logs for backend errors
🎯 Goal: Get admin panel live on Netlify in under 5 minutes!