Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Andrespeerez/porfolio-blog/llms.txt

Use this file to discover all available pages before exploring further.

This guide walks you through everything needed to get Porfolio & Blog CMS running on your local machine. By the end you will have a fully functional Blazor Server application backed by a SQLite database, with an admin account ready to use — all in under five minutes.

​
Prerequisites

Before you begin, make sure the following are installed:
  • .NET 10 SDK — the project targets net10.0. Verify with dotnet --version.
  • dotnet-ef tool (version 10.0.9) — required to apply EF Core database migrations. Install it globally with:
dotnet tool install --global dotnet-ef --version 10.0.9
If you prefer to use the local tool manifest already included in the repository (dotnet-tools.json), run dotnet tool restore after cloning instead.

​
Running the App

1

Clone the repository

Download the source code from GitHub and navigate into the project directory.
git clone https://github.com/Andrespeerez/porfolio-blog.git
cd porfolio-blog
2

Restore dependencies

Restore all NuGet packages declared in porfolio-blog.csproj. This includes EF Core 10, the SQLite provider, EF Core Tools, and ASP.NET Core Identity.
dotnet restore
3

Apply database migrations

Run EF Core migrations to create the blog.db SQLite file in the project root. The Default connection string in appsettings.json points to this file (Data Source=blog.db).
dotnet ef database update
After this step a blog.db file will appear in the porfolio-blog/ directory.
4

Run the application

Start the Blazor Server application using the .NET CLI. The default launch profile uses HTTP.
dotnet run
To use HTTPS instead, specify the profile explicitly:
dotnet run --launch-profile https
5

Open the app in your browser

Navigate to http://localhost:5058 (HTTP) or https://localhost:7140 (HTTPS) in your browser. You should see the home page of the portfolio site.In Development mode, AdminUserSeeder automatically creates an admin account on first run using the credentials defined in appsettings.Development.json:
FieldValue
Emailadmin@andresblog.com
PasswordAdmin123!
Use these credentials at /login to access the protected /admin page.
The seed credentials in appsettings.Development.json (admin@andresblog.com / Admin123!) exist for local development convenience only. Before deploying to any public or production environment, remove the Seed section from your configuration and provision an admin account through a secure out-of-band process. Leaving default credentials in a deployed application is a serious security risk.

​
Next Steps

Architecture

Understand how the five Clean Architecture layers interact and where to add new features.

Authentication

Learn how cookie authentication and the admin seeder work together to protect the admin area.

Build docs developers (and LLMs) love

Get started for freeTalk to us