Add automatic database initialization using EnsureCreated

[Copilot]

The Readings DbSet was added to AppDbContext without database initialization, causing "no such table: Readings" runtime errors when hitting the new endpoints.

Changes:

• Added automatic database creation on startup via dbContext.Database.EnsureCreated() in Startup.Configure()
• Updated .gitignore to exclude SQLite temporary files (*.db-shm, *.db-wal) and Migrations folder

public void Configure(IApplicationBuilder app, IWebHostEnvironment env, AppDbContext dbContext)
{
    // Ensure database is created on startup
    dbContext.Database.EnsureCreated();
    // ...
}

Database schema is created automatically from the EF Core model on first run without requiring migration files.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[joaoferreira-dev]

@copilot I think it is not supposed to commit the Migrations folder neither app.db-shm nor aapp.db-wal

[Copilot]

@copilot I think it is not supposed to commit the Migrations folder neither app.db-shm nor aapp.db-wal

You're correct. I've removed the Migrations folder and the SQLite temporary files (app.db-shm, app.db-wal) from the repository.

Updated approach:

• Changed from Database.Migrate() to Database.EnsureCreated() for automatic database creation
• Updated .gitignore to exclude Migrations folder and SQLite temp files (*.db-shm, *.db-wal)
• Database schema is now created directly from the EF Core model on startup

Fixed in commit c7ac9ac.