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

Box Sync ignores files that start with a dot #807

Closed
katherinelim opened this issue Apr 27, 2016 · 10 comments · Fixed by #1530
Closed

Box Sync ignores files that start with a dot #807

katherinelim opened this issue Apr 27, 2016 · 10 comments · Fixed by #1530

Comments

@katherinelim
Copy link

Mackup creates the backup folder in the Box Sync local folder properly and all dot files (.bash_profile, .bashrc, .gitconfig, etc.) are copied there but they are never synced to Box, which means that after the local Box Sync folder is deleted, the dot files will not be restored from Box.

This is due to Box Sync ignoring files that start with a dot "." as hidden files.

Documented here: https://community.box.com/t5/Box-Sync/Which-File-Types-Are-Ignored-Or-Blocked-In-Box-Sync/ta-p/117

The way around this could involve copying the files to names that do not start with a dot and creating symlinks back to the original dot file names, e.g., .bashrc -> Box Sync/Mackup/bashrc.txt

@lra
Copy link
Owner

lra commented Apr 27, 2016

Wow, that's really stupid...

OK, I guess the box engine needs to rename those files to something line .bashrc -> box_dot_bashrc_.
That could work for individual files, but if a linked folder contains dotfiles, mackup cannot help here.

Not sure if there are a lot of dotfiles in folders, but it's a possible source of bugs and confusion.

Also what about dot folders? Same behavior? Sounds like there is no easy fix on mackup side. Is there a way to ask box if they could make this an option? (ignoring dot files)

@lra lra added the Discussion label Apr 27, 2016
@katherinelim
Copy link
Author

It looks messy to implement. Given that Dropbox is ok with dotfiles, am happy to close this as a dontfix and take it up with Box.

@lra
Copy link
Owner

lra commented Apr 28, 2016

The problem is that it's a valid issue... Should we just drop Box's support?

@katherinelim
Copy link
Author

Dropping Box support would suffice, but leave a note as to why, it's going to become a frequently asked question. 👍

@guillaumealgis
Copy link
Contributor

Just realized this is why my preferences were always out of sync between my Macs. This issue really needs to be added to the readme. Box is listed as "Supported Storage", but in real-world usage it won't work properly.

@silvamerica
Copy link

Are there any updates that might make this work? Box is still listed as Supported Storage.

@lra
Copy link
Owner

lra commented Feb 27, 2020

I'm on it, I'm removing Box support.

@lra lra closed this as completed in #1530 Feb 27, 2020
lra added a commit that referenced this issue Feb 27, 2020
@brandondrew
Copy link

Wow, adding Box to my mental shit list of products to avoid in general. How can a file storage product be any good that ignores a huge class of important files? This is really mind-boggling.

@SeniorMars
Copy link

Could you readd it back? I am sure it works as I have used it with rclone.

@lra
Copy link
Owner

lra commented Jun 27, 2024

A contributor could, but it would require tests to make sure this works, as I can't spend the time on testing it.

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

Successfully merging a pull request may close this issue.

6 participants