Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running the EventHub.DbMigrator project did not create and seed the database #134

Open
justinfraz opened this issue Aug 23, 2023 · 5 comments

Comments

@justinfraz
Copy link

No description provided.

@EngincanV
Copy link
Member

Did you follow the How to run? section in the README.md file? Before running the db migrator, you should run the docker images.

If you did the steps as stated in the documentation, please provide some details about your problem.

@justinfraz
Copy link
Author

Yes, I have performed these steps before running the db migrator project:

Execute dotnet build /graphBuild command in the root folder of the solution.
Execute etc/docker/up.ps1 to run the depending services.

@EngincanV
Copy link
Member

I tried just before running the DbMigrator project and it ran as expected:

image

You can check your configurations, ensure docker containers are up and running, and also ensure Redis or Postgresql are not running on your PC locally.

@justinfraz
Copy link
Author

But when I run this command in the up.ps1 file:

docker-compose -f docker-compose.infrastructure.yml -f docker-compose.infrastructure.override.yml up -d --remove-orphans

It starts the docker containers but it also starts Redis or Postgresql:

up ps1 output

@justinfraz
Copy link
Author

Here are some new error messages from the output window when I run the db migrator project:

db migrator output1

db migrator output2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants