No description
Prevent WebSocket disconnections during deployments by: 1. Rolling Update Strategy: - maxSurge: 1 (allow 1 extra pod during rollout) - maxUnavailable: 0 (keep all pods running) - minReadySeconds: 10 (wait before continuing rollout) 2. Graceful Shutdown: - terminationGracePeriodSeconds: 30 (allow Phoenix to drain connections) 3. PodDisruptionBudget: - minAvailable: 1 (ensure at least 1 pod always available) - Prevents all pods from being terminated simultaneously 4. Improved Health Checks: - Faster readiness probe (5s initial, 3s period) - More aggressive success/failure thresholds - New pods marked ready faster This ensures new pods are fully ready and serving traffic before old pods are terminated, maintaining WebSocket connections and preventing 'something went wrong' errors during deployments. |
||
|---|---|---|
| .gitlab/agents | ||
| assets | ||
| config | ||
| docs | ||
| k8s | ||
| lib | ||
| priv | ||
| rel/overlays/bin | ||
| scripts | ||
| test | ||
| towerops | ||
| .credo.exs | ||
| .dockerignore | ||
| .formatter.exs | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .sourceignore | ||
| .test-watch.exs | ||
| .tool-versions | ||
| AGENT_IMPLEMENTATION.md | ||
| AGENT_PROTOCOL.md | ||
| AGENTS.md | ||
| AWS_SES_SETUP.md | ||
| CLAUDE.md | ||
| DEPLOYMENT.md | ||
| Dockerfile | ||
| IMPLEMENTATION_PLAN.md | ||
| mix.exs | ||
| mix.lock | ||
| MOBILE_API.md | ||
| README.md | ||
| tail_logs.sh | ||
| TIMESCALEDB.md | ||
| WEBSOCKET_MIGRATION.md | ||
TowerOps
Network monitoring and alerting platform built with Phoenix LiveView.
Features
- Multi-tenant architecture - Organizations with role-based permissions
- Site hierarchy - Organize equipment across multiple sites
- Automated monitoring - Real-time ping monitoring with configurable intervals
- Time-series data - Efficient storage with TimescaleDB (optional)
- Real-time updates - LiveView dashboard with PubSub
- Equipment tracking - Monitor network devices by IP address
Quick Start
Prerequisites
- Elixir 1.14+
- PostgreSQL 14+
- (Optional) TimescaleDB for production-grade time-series performance
Setup
# Install dependencies
mix setup
# Start the server
mix phx.server
Visit localhost:4000 from your browser.
TimescaleDB (Production Only)
Development: Uses standard PostgreSQL (no TimescaleDB required).
Production: TimescaleDB is automatically enabled for optimal performance with time-series data.
# Production deployment - install TimescaleDB first
brew tap timescale/tap && brew install timescaledb # macOS
# Then run migrations with MIX_ENV=prod
MIX_ENV=prod mix ecto.migrate
See TIMESCALEDB.md for detailed installation and configuration.
How it works: Migrations detect the environment (MIX_ENV) and only enable TimescaleDB features (hypertables, compression, retention policies, continuous aggregates) in production.
Development
Database
mix ecto.create # Create database
mix ecto.migrate # Run migrations
mix ecto.reset # Drop, create, and migrate
Testing
mix test # Run all tests
mix test --trace # Run with detailed output
Code Quality
mix format # Format code with Styler
mix compile --warnings-as-errors
Learn more
- Official website: https://www.phoenixframework.org/
- Guides: https://hexdocs.pm/phoenix/overview.html
- Docs: https://hexdocs.pm/phoenix
- Forum: https://elixirforum.com/c/phoenix-forum
- Source: https://github.com/phoenixframework/phoenix