# Property Portfolio Nexus

A holistic real estate management utility featuring a React presentation layer and a FastAPI processing core.

System Capabilities

Server-Side Engine (FastAPI)

• Secure user access control utilizing JSON Web Tokens (JWT)
• Core functionality for managing physical assets (properties)
• Reservation scheduling mechanism featuring dynamic availability visualization
• Automated aggregation and presentation of financial records
• Administration interfaces for property owners and tenant interaction modules
• Framework for tracking capital expenditure and calculating Return on Investment (ROI)
• Interoperability layer designed for the Sara intelligent automation agent
• Persistence handled via PostgreSQL, interfaced through SQLAlchemy ORM

Client-Side Interface (React)

• Modern development utilizing TypeScript for type safety
• Data synchronization and caching managed via React Query hooks
• Input validation implemented using Zod schemas integrated with React Hook Form
• Responsive visual design employing shadcn UI components and Tailwind utility classes
• Role-based access gating for secure navigation paths
• Mechanism for instantaneous updates displayed on the primary monitoring screen

Initiation Guide

Essential Prerequisites

• Docker and Docker Compose environment managers
• Node.js runtime environment (version 18 or newer) for local iteration
• Python interpreter (version 3.11 or newer) for backend operations

Setup and Deployment Procedures

Utilizing Containerization (Recommended Approach)

1. Obtain the source repository files

git clone https://github.com/yourusername/habibi-dashboard.git
cd habibi-dashboard

1. Initiate the bundled environment via Docker Compose

docker-compose up

This action deploys: - The PostgreSQL data repository on network port 5432 - The Backend RESTful interface on port 8000 - The Frontend serving application on port 5173

1. Access Points:
2. Client Application: http://localhost:5173
3. Service API Endpoint: http://localhost:8000
4. Interactive API Specification: http://localhost:8000/api/v1/docs

Independent Local Configuration

Backend Service Setup

1. Establish an isolated Python execution environment

cd backend
python -m venv venv
source venv/bin/activate  # For Windows: venv\Scripts\activate
pip install -r requirements.txt

1. Configure the underlying data store (requires PostgreSQL service to be running)

# Define database connection parameters in a .env configuration file
alembic upgrade head

1. Launch the backend application listener

uvicorn app.main:app --reload

Frontend Interface Initialization

1. Install necessary Javascript dependencies

npm install

1. Start the active development server

npm run dev

Standard Access Credentials

For initial testing, the system pre-populates a primary administrator account: - Identifier: admin@habibi.com - Passphrase: admin

Structural Organization

asset-portfolio-nexus-901/
├── backend/              # FastAPI Service Layer
│   ├── app/              # Core logical code
│   │   ├── api/          # Endpoint definitions
│   │   ├── core/         # Foundational elements (settings, security protocols)
│   │   ├── crud/         # Data manipulation routines (Create, Read, Update, Delete)
│   │   ├── db/           # Data persistence initialization
│   │   ├── models/       # SQLAlchemy structural definitions
│   │   ├── schemas/      # Pydantic data contract definitions
│   │   ├── services/     # Business logic modules
│   │   └── main.py       # Application bootstrap file
│   ├── migrations/       # Database schema version control
│   └── tests/            # Backend validation suite
├── src/                  # React User Interface
│   ├── api/              # Network request abstraction
│   ├── components/       # Reusable UI elements
│   ├── contexts/         # State sharing mechanisms
│   ├── hooks/            # Custom reusable frontend logic units
│   ├── layouts/          # Page structure templates
│   ├── lib/              # General utility functions
│   └── pages/            # Top-level view components
├── docker-compose.yml    # Orchestration script
├── Dockerfile.frontend   # Frontend image definition
└── backend/Dockerfile    # Backend image definition

Validation Procedures

Backend Assertions

cd backend
pytest

Frontend Assertions

npm test

Production Deployment Strategy

Containerized Rollout

The system is designed for deployment using Docker Compose, requiring minor configuration adjustments for a live environment:

1. Modify environment variables within docker-compose.yml:
2. Establish a cryptographically robust SECRET_KEY value
3. Specify authorized BACKEND_CORS_ORIGINS hostnames

4. Configure production-grade database access credentials

5. Build and activate the production containers:

docker-compose -f docker-compose.yml -f docker-compose.prod.yml up -d

Hostinger Cloud Automation

This architecture incorporates automated deployment pipelines via GitHub Actions targeting Hostinger Cloud infrastructure. Pushing updates to the primary branch triggers:

1. Compilation of the application assets
2. Transfer of finalized files to the Hostinger environment utilizing FTP credentials

Required Deployment Credentials

Ensure the following sensitive parameters are securely stored as repository secrets:

• FTP_SERVER: Hostinger FTP endpoint address
• FTP_USERNAME: Designated Hostinger FTP access identifier
• FTP_PASSWORD: Corresponding Hostinger FTP secret

Project Governance

This software is distributed under the terms of the MIT License – consult the LICENSE file for comprehensive details.