“Failed to initialize the database” error when using PostgreSQL in FluentCMS
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start at the /setup flow and FluentCmsDbContext initialization, then inspect the FluentCMS.Repositories.EFCore.PostgreSQL package for its migrations and embedded Setup.sql resource. Reproduce the initialization failure and verify that the provider's schema resources are packaged and discoverable, or document the supported migration path.
Written by the indexing model from the issue text.
Description
When using PostgreSQL with FluentCMS, the setup process fails during the /setup step with the message “Failed to initialize the database.” The PostgreSQL connection is successful and FluentCmsDbContext is properly initialized, but a System.InvalidOperationException occurs afterward.
It appears that the NuGet package FluentCMS.Repositories.EFCore.PostgreSQL does not include EF Core migration files, and the SQL initialization script (Setup.sql) might be missing from the embedded resources. The exception log shows that the file 'FluentCMS.Repositories.EFCore.PostgreSQL.Setup.sql' cannot be found, suggesting it was not packaged correctly.
Could you please confirm whether the PostgreSQL provider intentionally excludes migration scripts, or if there is a recommended way to initialize the schema (e.g., through a provided SQL script or manual migration process)?
- Dominant language
- HTML
- Stars
- 6
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
CopilotKit/aimock#491 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
deepset-ai/haystack#13092 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
dani-garcia/vaultwarden#7801 ·
Maintainers usually reply within 1 day
-
🐛 Bug supabase/cli
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
area/auth comp/gateway P2 sweeper:risk-message-delivery type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
NousResearch/hermes-agent#131962 ·
Maintainers usually reply within 1 day