# Full-Stack Personal Website & Self-Hosted Infrastructure

A personal website and content management backend built with Next.js, ASP.NET Core and PostgreSQL, combining modern web development with self-hosted infrastructure and Cloudflare services.

Technologies: Next.js, TypeScript, ASP.NET Core, Entity Framework Core, PostgreSQL, Docker, Cloudflare Tunnel, Cloudflare R2, Netlify

View the public website

Overview

I designed and developed a personal website supported by a self-hosted backend, allowing projects, technical articles and other content to be stored in PostgreSQL and retrieved through an ASP.NET Core REST API.

The project combines frontend development, relational database design, API development and infrastructure management. Rather than relying entirely on a hosted content management service, I built and deployed the backend myself.

Architecture

The platform separates the public website from its backend services.

  • Frontend: Next.js and TypeScript, deployed as a static website on Netlify.
  • Backend: ASP.NET Core REST API responsible for exposing structured content to the frontend.
  • Database: PostgreSQL, using Entity Framework Core for data access and database migrations.
  • Media storage: Cloudflare R2 for storing website images and other assets.
  • Containerisation: Docker for running and managing backend services.
  • Networking: Cloudflare Tunnel for securely exposing the API without opening inbound ports on the host.

This separation allows the frontend and backend to be developed and deployed independently.

Content Management & Database Design

The content model supports different types of entries, including projects and technical articles, through a shared PostgreSQL table.

Each entry contains a unique identifier, content type, slug, title, description and full content. Optional fields support an image and an external destination URL.

PostgreSQL uses a custom enum to distinguish content types, while tags are stored in a separate table and associated with posts through a many-to-many relationship.

The database schema is managed through Entity Framework Core migrations, allowing structural changes to be tracked alongside application development.

API Development

I developed an ASP.NET Core backend to expose website content through REST endpoints.

The API retrieves structured content from PostgreSQL, including associated tags, and provides it to the frontend without requiring the website to connect directly to the database.

The publicly deployed API focuses on content retrieval. Content creation and modification are currently handled through database operations and SQL scripts rather than a dedicated administration interface.

Self-Hosted Infrastructure

The backend runs on infrastructure I manage myself, using Docker to containerise application services and their dependencies.

Cloudflare Tunnel provides connectivity between the public API hostname and the internally hosted application, avoiding the need to expose inbound ports directly to the internet.

Cloudflare R2 provides object storage for media, keeping static assets separate from application content stored in PostgreSQL.

This setup has given me practical experience with container deployment, application configuration, database administration and troubleshooting across multiple services.

Continued Development

The platform also serves as an environment for exploring alternative backend implementations and improving my understanding of ASP.NET Core.

My ongoing work includes experimenting with Npgsql and Dapper for direct PostgreSQL access, repository and service abstractions, parameterised SQL queries and more flexible content management endpoints.

These changes are part of continued development rather than features already deployed to the public platform.

What the Project Demonstrates

This project demonstrates my ability to deliver and operate a complete web application, from designing the frontend and modelling relational data to developing APIs and deploying services on self-managed infrastructure.

It has also provided a practical foundation for exploring different approaches to backend architecture, database access and content management.