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
The current Docker Compose configuration expects that the MS SQL Server database is called "jhipstertest", which of course doesn't work by default.
Unfortunately, it is not possible to create a MS SQL Server database schema at startup, see microsoft/mssql-docker#2
We could do it by using a complex Docker configuration like we have for MongoDB or Couchbase, but to have a much simpler setup my idea is to use the default "tempdb" that is created by the MS SQL Server Docker image.
this will make Docker Compose work
if the application is used outside Docker, it will continue to use the "normal" database name, which is the name of the app (as usual with JHipster)
the only case that's a bit strange is if you run your app locally, but want to connect to a MS SQL Server instance inside Docker, as in this case you will need to configure the "tempdb" database in the connection String in the application-*.yml configuration file(s)
Of course using "tempdb" isn't good for production use, but I don't think you are allowed to use those images in production (by the Microsoft terms of service), and anyway it's not a recommended use of Docker.
The text was updated successfully, but these errors were encountered:
This was found while working on #7245
The current Docker Compose configuration expects that the MS SQL Server database is called "jhipstertest", which of course doesn't work by default.
Unfortunately, it is not possible to create a MS SQL Server database schema at startup, see microsoft/mssql-docker#2
We could do it by using a complex Docker configuration like we have for MongoDB or Couchbase, but to have a much simpler setup my idea is to use the default "tempdb" that is created by the MS SQL Server Docker image.
application-*.yml
configuration file(s)Of course using "tempdb" isn't good for production use, but I don't think you are allowed to use those images in production (by the Microsoft terms of service), and anyway it's not a recommended use of Docker.
The text was updated successfully, but these errors were encountered: