How sergimporto/personallibrary works
Project type and purpose
• This is a full-stack mobile application (“PersonalLibrary”) consisting of:
• An Android client app (Kotlin + Jetpack/AndroidX)
• A backend microservice (Python, likely Flask or FastAPI)
• A PostgreSQL database
• Kubernetes-based infrastructure (Docker, Helm charts)
• Observability stack (Prometheus & Grafana)
• CI/CD pipeline (CircleCI)
• Purpose: allow users to search books (via Google Books API), save them into a personal library, and manage them via the mobile app with data persisted on a backend.
File structure
• Top-level directories:
• “app” – Android application code (Activities, ViewModels, Retrofit client, UI, resources)
• “Backend API” – Kubernetes manifests, Helm charts, Dockerfile & Py code (main.py, requirements.txt) for the Python API service
• Infra-as-code artifacts: IngressController.yaml, namespace.yaml, ConfigMaps, PVC/PV, Service definitions, Helm charts under milibrary-charts for API, Postgres, and grafana-prometheus monitoring.
• CI/CD: .circleci/config.yml drives build/test/deploy.
• Build tools: Gradle (Kotlin DSL) for Android, Helm for K8s charts.
Extract architecture insights from the README
• The README only states “# PersonalLibrary,” but file tree shows the components.
Detail
• Helm chart artifacts as part of deployment automation.
• CI/CD flow: code commit → CircleCI → Docker image → Helm upgrade.
• Health-check endpoint and backup procedures (auto-start-library.sh, backup.yaml).