Sync db scheme development and production#30
Conversation
roschaefer
left a comment
roschaefer
left a comment
There was a problem hiding this comment.
I did run the changes this time but I think this should be OK. @matthib can you double check the bash script please before merge?
| 2. Go to the newly created Clock-of-Change-API directory (`cd Clock-of-Change-API` in the console) | ||
| 3. Run `docker-compose up`. This will build the Docker container on first startup and run it. This can take a while, but after some time you should see the Clock of Change ticking. | ||
| 4. To create an initial API key and sample entries, run `docker-compose exec db seed.sh`. The initial API key you can use with your requests will have the value `secret`. | ||
| 4. To create an initial API key and sample entries, run `docker-compose exec db bash seed.sh`. The initial API key you can use with your requests will have the value `secret`. |
There was a problem hiding this comment.
This looks wrong. You sync seed.sh in a folder under $PATH making seed.sh an executable program.
There was a problem hiding this comment.
Can change it back, if that is better.
Unfortunately I get the error:
OCI runtime exec failed: exec failed: container_linux.go:344: starting container process caused "no such file or directo
ry": unknown
when trying to run it from $PATH directly. With running first bash and then passing seed.sh as an argument, the seed.sh can successfully be found in the $PATH.
This could be a problem with my local environment, as I use the Windows Git Bash as my console.
matboehm
changed the title
|
@roschaefer Changed back the command in the Readme.md. If the rest of the code seems ok, please merge. Thanks! 👍 |
2 participants
Close #29
Synchronize the Docker MySQL database with the Production live database.