You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am big fan of Schema Spy and had been using it extensively. I am trying to generate the schema spy view using the mysql instance running in a docker container. With the explanation provided in the repository regarding generating the schemaspy it is not clear how it will be generated or if it is applicable for the scenario where we have an existing mysql running instance and can use schemaspy to get the report out ?
I am new to docker so any assistance would be of great help.
The text was updated successfully, but these errors were encountered:
Hiya,
This implementation generates the output in /app/output and runs a lightweight webserver to display it, so you should be able to browse to localhost:8080 and see the generated content when it's running. We run it alongside other docker containers to provide API documentation. If you want to extract the output I think you can just mount a volume at /app/output, although I haven't tested that.
Thanks for the response. Today i was able to connect and run schemaspy via standard way ie via command line however was not able to see any graphs of relationships even though i have the graphViz in the classpath. I was wondering how your schemaspy container will be of help to us and what extra the container is doing when compare to the standard process.
Hi cywolf,
I am big fan of Schema Spy and had been using it extensively. I am trying to generate the schema spy view using the mysql instance running in a docker container. With the explanation provided in the repository regarding generating the schemaspy it is not clear how it will be generated or if it is applicable for the scenario where we have an existing mysql running instance and can use schemaspy to get the report out ?
I am new to docker so any assistance would be of great help.
The text was updated successfully, but these errors were encountered: