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
Describe the bug
The setup.sh script does not work on macOS out-of-the box due to old command paths and syntax.
To Reproduce
Steps to reproduce the behavior:
Follow the Mac installation steps
Run setup.sh as instructed
Expected behavior
The script should configure the site databases.
Instead, the sqlcmd commands in the Docker container fail due to a path error, and the dotnet-episerver commands sometimes fail due to the command not being found, particularly when dotnet is installed with homebrew. (See #825 )
Screenshots
Desktop (please complete the following information):
OS: macOS
Because these errors occur when calling dotnet commands and while setting up the Docker container, I assume these errors also occur with Linux when running the same setup.sh script.
Additional context
It looks like the script has old paths set for sqlcmd. In addition, the site appsettings is set to always trust the SQL Server certificates, but the sqlcmd commands fail on a certificate trust issue. Finally, the dotnet episerver commands appear to be using an older syntax (dash vs space) that can fail in some cases.
Previous issues such as #825 also mention difficulty running the script in the default zsh shell.
The text was updated successfully, but these errors were encountered:
Describe the bug
The setup.sh script does not work on macOS out-of-the box due to old command paths and syntax.
To Reproduce
Steps to reproduce the behavior:
setup.sh
as instructedExpected behavior
The script should configure the site databases.
Instead, the
sqlcmd
commands in the Docker container fail due to a path error, and thedotnet-episerver
commands sometimes fail due to the command not being found, particularly whendotnet
is installed withhomebrew
. (See #825 )Screenshots
Desktop (please complete the following information):
dotnet
commands and while setting up the Docker container, I assume these errors also occur with Linux when running the samesetup.sh
script.Additional context
It looks like the script has old paths set for
sqlcmd
. In addition, the siteappsettings
is set to always trust the SQL Server certificates, but thesqlcmd
commands fail on a certificate trust issue. Finally, thedotnet episerver
commands appear to be using an older syntax (dash vs space) that can fail in some cases.Previous issues such as #825 also mention difficulty running the script in the default zsh shell.
The text was updated successfully, but these errors were encountered: