-
-
Notifications
You must be signed in to change notification settings - Fork 261
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
-p password argument ignored when starting cloudcmd #64
Comments
Btw, the |
Hi @jojow,
And starting from next version you could use just: You could also try alpine build (based on alpine-node, which is much smaller then official docker image of node) with: |
Great, thanks a lot! Now it works! :-) |
Hi |
@dtk78 you can use
in docker-compose file or in env file. |
Hello, Thanks a lot for you reply. |
hello, Is it possible to setup default user for creating a file or directory ? Regards |
I have no idea :). There is no way to set
You should build your own docker image and create user. |
Hi, Do you know how I can make chown after creating a file or after copying some files ? Do I need to add a function chmod in a .js file ? Thanks for your help |
You can use |
In v7.3.0 was landed support of environment variables |
Hi,
I tried cloudcmd through Docker, using the following command:
docker run -d -p 8000:8000 coderaiser/cloudcmd:5.2.3 npm start -- --root /data -u admin -p sOmEpAsSwOrD
However, the -p password parameter seems to be ignored. cloudcmd runs perfectly, but I can access it without giving any password. So, everyone can access.
Is this a bug or did I miss anything?
Thanks!
Johannes
The text was updated successfully, but these errors were encountered: