Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

setup.sh has out-date-command paths and syntax #972

Open
nsideras opened this issue Jan 27, 2025 · 1 comment · May be fixed by #973
Open

setup.sh has out-date-command paths and syntax #972

nsideras opened this issue Jan 27, 2025 · 1 comment · May be fixed by #973

Comments

@nsideras
Copy link

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:

  1. Follow the Mac installation steps
  2. 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

Image

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.

@nsideras nsideras linked a pull request Jan 27, 2025 that will close this issue
@nsideras
Copy link
Author

I've added PR #973 that fixes these issues, and as best as I can test on my machines gets setup.sh working out-of-the-box again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant