This guide explains how to set up the Simple Menu system for access from multiple computers on the same Local Area Network (LAN).
Note: For complete setup instructions, see DEPLOYMENT.md. For production deployment, see DEPLOYMENT_GUIDE.md.
-
Deploy with Docker:
git clone <repository-url> simple-menu cd simple-menu docker compose -f docker/docker-compose.unified.yml up -d
-
Find your IP address:
ipconfig | findstr IPv4 -
Access from any device on your network:
- Menu Display:
http://YOUR_IP:3000 - Admin Panel:
http://YOUR_IP:3000/submit
- Menu Display:
-
Run the setup script:
.\setup-lan.ps1 -
Or manually start services:
# Backend (in Backend folder) npm start # Frontend (in Frontend/front folder) npm start
Run these commands as Administrator in PowerShell:
# Allow Backend Port (3000)
netsh advfirewall firewall add rule name="Simple Menu Backend" dir=in action=allow protocol=TCP localport=3000
# Allow Frontend Port (4200)
netsh advfirewall firewall add rule name="Simple Menu Frontend" dir=in action=allow protocol=TCP localport=4200cd "c:\Users\Lorenzo\source\repos\Simple-menu\Backend"
npm startThe backend will display your LAN IP addresses when it starts.
cd "c:\Users\Lorenzo\source\repos\Simple-menu\Frontend\front"
npm startFind your host machine's IP address (displayed when servers start), then:
- Menu Display:
http://YOUR_IP:3000 - Menu Administration:
http://YOUR_IP:3000/submit
Example: If your IP is 192.168.1.100:
- Menu Display:
http://192.168.1.100:3000 - Menu Admin:
http://192.168.1.100:3000/submit
- Unified Port: Both frontend and backend are served through port 3000 in production
- Real-time Updates: All connected devices receive live menu updates via WebSocket
- Multi-device Support: Multiple people can view the menu while one person manages it
- Auto-detection: The frontend automatically connects to the correct backend URL
- Restaurant Display: Host machine connected to a TV showing the menu (
/) - Kitchen Updates: Staff computer for menu management (
/submit) - Customer Access: Tablets or phones for customers to view menu
- Check Firewall: Ensure port 3000 is allowed through Windows Firewall
- Verify Network: All devices must be on the same WiFi/LAN
- Test Connectivity: Ping the host machine from other devices
- Router Settings: Some routers block internal communication
- Check that WebSocket connections can be established on port 3000
- Ensure no proxy servers are interfering with WebSocket upgrades
- Verify that the backend WebSocket server is running
# Check if containers are running
docker compose -f docker/docker-compose.unified.yml ps
# Check container logs
docker compose -f docker/docker-compose.unified.yml logs
# Restart services
docker compose -f docker/docker-compose.unified.yml restart- DEPLOYMENT.md - Complete setup and deployment guide
- DEPLOYMENT_GUIDE.md - Advanced production deployment
- API_REFERENCE.md - API and WebSocket documentation
- COMPONENTS.md - Technical component details