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

The command make setup_env may not work properly on windows #377

Open
elmq0022 opened this issue Feb 19, 2021 · 1 comment
Open

The command make setup_env may not work properly on windows #377

elmq0022 opened this issue Feb 19, 2021 · 1 comment
Labels
difficulty: easy priority: critical Critical feature - needs attention right away type: bug

Comments

@elmq0022
Copy link
Contributor

Problem:
Steps say that we should run make setup_env before spinning up docker for the first time. This did not work on windows.

Requirements:
Solution needs to work on windows, linux, and MacOS.

@elmq0022 elmq0022 added type: bug priority: critical Critical feature - needs attention right away difficulty: easy labels Feb 19, 2021
@spark-c
Copy link
Contributor

spark-c commented Sep 14, 2021

Just for other newbies, since it took me a minute to realize what was happening:

This step is meant to copy the file "docker/docker.env.sample" (default settings for the project) to "docker/docker.env". On Windows, it results in:

...\chipy.org> make setup_env

'##' is not recognized as an internal or external command,
operable program or batch file.
make: *** [Makefile:8: setup_env] Error 1

That make setup_env command attempts to run cp -n docker/docker.env.sample docker.docker.env || true which doesn't work on Windows due to it not recognizing the -n flag and || true bit at the end.

In the meantime, using cp docker/docker.env.sample docker/docker.env in Powershell from the .\chipy.org directory should work. Alternatively, you can copy + rename the file manually in File Explorer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficulty: easy priority: critical Critical feature - needs attention right away type: bug
Projects
None yet
Development

No branches or pull requests

2 participants