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
{{ message }}
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
Would it be possible to have this not use the docker SQL server database and have it point to an existing one? I am trying to have it point to an existing 2014 SQL Server and each service comes up on its own and works fine but I can't get the docker solution to run it keeps saying that it can't find the sqlserver. I changed all of the connection strings to point to the SQL Server in the docker file but still no luck. Any pointers would be greatly appreciated.
Thanks,
Tim
The text was updated successfully, but these errors were encountered:
Hi!
You need to change the connection strings in the docker compose files.
Look at the file "docker-compose.override.yml" file and you'll see something like:
I tried that and it hasn't worked. In the connection string I changed sql.data to servername\SQLEXPRESS along with the database userid and password. It still says it can not find the database. I don't know if it is because it is running in a unix container and the SQL server is on my local.
Also, if you don't want to use an IP but a server name, you can add this convenient entry at the Docker Compose override file, pointing to the external server (your dev machine or any SQL Server): docker-compose.override.yml
Would it be possible to have this not use the docker SQL server database and have it point to an existing one? I am trying to have it point to an existing 2014 SQL Server and each service comes up on its own and works fine but I can't get the docker solution to run it keeps saying that it can't find the sqlserver. I changed all of the connection strings to point to the SQL Server in the docker file but still no luck. Any pointers would be greatly appreciated.
Thanks,
Tim
The text was updated successfully, but these errors were encountered: