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

Fix the docker run command in README.md #278

Closed
wants to merge 1 commit into from

Conversation

rursache
Copy link

@rursache rursache commented Feb 14, 2023

What type of PR is this?

  • cleanup
  • documentation

What this PR does / why we need it:

Include volume mounting, time zone, -d and better formatting in the README.md

Which issue(s) this PR fixes:

none

Release Notes

Updated README.md to include a more complete `docker run` command

Include volume mounting, time zone, -d and better formatting
Copy link

@fkrivsky fkrivsky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM :)

--restart unless-stopped \
-p 3100:7745 \
-e TZ=Europe/Bucharest \
-v ${HOME}/.homebox:/data \
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do you think should it be a bind mount instead of a volume?

--

I'm not sure I want to advocate people use their home directory over the named volume.

Given

VOLUME [ "/data" ]

the data should be persistent anyways

🤷

Copy link
Author

@rursache rursache Feb 16, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you should mount the volume in a defined location for easy backups and access. home directory makes sense as there are the... user directories, configs and data. all backup solutions include the home directory by default.

if you really don't want to use the home directory as example, you can use -v /path/to/data/folder:/data \ in the docker run, like linuxserver guys do it.

hay-kot added a commit that referenced this pull request Mar 21, 2023
hay-kot added a commit that referenced this pull request Mar 21, 2023
@hay-kot hay-kot closed this in #362 Mar 21, 2023
hay-kot added a commit that referenced this pull request Mar 21, 2023
* fix potential memory leak with time.After

* add new background service to manage scheduled notifications

* update docs

* remove old js reference

* closes #278

* tidy
OrellBuehler pushed a commit to thechosenlan/homebox that referenced this pull request Jun 24, 2023
* fix potential memory leak with time.After

* add new background service to manage scheduled notifications

* update docs

* remove old js reference

* closes hay-kot#278

* tidy
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 this pull request may close these issues.

None yet

3 participants