inwerejosic/flask-ip-reverse

Purpose and Entry Point

Flask IP Reverse is a small server-rendered Python service that records visitor IP addresses and renders each address reversed, alongside stored visit history. The application entry point is app.py; its browser-facing UI is templates/index.html.

Web Application Layer

app.py owns the Flask application lifecycle, request handling, IP collection, reversal logic, SQLite access, and HTML rendering. Requests enter Flask, derive the visitor address, persist it, query history, then render the template. The primary application boundary is HTTP request/response handling versus local database state.

Paths: app.py, templates/index.html, requirements.txt

Persistence

The stated persistence model is SQLite, with visit records retained in data/visit.db at runtime. SQLite keeps the service self-contained: no network database or separate persistence process is required. Database durability depends on the runtime/container volume arrangement rather than application code alone.

Paths: app.py, docker-compose.yml

Container Runtime and Local Deployment

Docker is the intended packaging/runtime boundary for the Flask process. Compose provides a local service definition and is the likely place to configure port exposure and persistent storage for SQLite. The README describes a multi-stage Alpine image build, though a Dockerfile is not present in the supplied tree and should be treated as a repository gap or external omission.

Paths: docker-compose.yml, app.py, requirements.txt

Kubernetes Deployment

A Helm chart packages the service for Kubernetes. The deployment template defines the workload, the service template exposes it inside the cluster, and the namespace template establishes deployment scope. Values centralize environment-specific chart settings.

Paths: flask-ip-reverse-helm/templates/deployment.yaml, flask-ip-reverse-helm/templates/service.yaml, flask-ip-reverse-helm/values.yaml

Observability Boundary

The Helm chart includes a ServiceMonitor resource, indicating intended Prometheus-operator discovery of service metrics. Actual metric emission by the Flask process is not established by the supplied tree; the ServiceMonitor is infrastructure-side configuration.

Paths: flask-ip-reverse-helm/templates/servicemonitor.yaml, flask-ip-reverse-helm/templates/service.yaml

Delivery Pipeline and External Services

GitHub Actions builds and publishes container images on pushes to main and release tags. Docker Hub is the external image registry target; Kubernetes deployments are expected to consume the resulting image through Helm values.

Paths: .github/workflows/docker-publish.yml, flask-ip-reverse-helm/values.yaml, flask-ip-reverse-helm/Chart.yaml