-
Notifications
You must be signed in to change notification settings - Fork 97
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
Readme: Fixing it #646
Readme: Fixing it #646
Conversation
README.md
Outdated
# Compare it | ||
diff kitty.jpg kitty2.jpg | ||
# Starting the sample FTP server | ||
docker run --rm -d -p 2121-2130:2121-2130 -v $(pwd):/app fclairamb/ftpserver |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason for not including the /tmp
path to the files
directory you created above.
To make the data persistent
docker run --rm -d -p 2121-2130:2121-2130 -v $(pwd)/files:/tmp -v $(pwd):/app fclairamb/ftpserver
Am I missing something in the documentation ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, I hesitated and left the files
directory and dropped the -v $(pwd)/files:/tmp... Because /tmp
is not the smartest path for persistence 😬 and I would like to keep the local & docker config common for the demo.
But I guess I can keep it that way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes you are right, /tmp
for once is quite ambiguous in certain sense.
Docker sample usage: Binding files directory to /tmp
@dunefro good for you now ? |
@fclairamb Yes |
Fixes #629