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

More "backup-proof" tokens #33

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

felixchenier
Copy link

Good morning Jeremy

I first want to thank you for this very solid program to make Trello backups. I was increasingly fearing a catastrophic failure since I always have more data and more information on Trello, and with your software, I know that a catastrophic failure would still be very bad, but not completely catastrophic :-)

I took the liberty to modify the behaviour of your software when using the tokenize option. First, I think that tokens should be independent on the location of the list, card or attachment. If it isn't (current behaviour), then moving an element around would change its resulting file name or folder, which would result in a duplicata if the backup is launched with the "incremental" option. So I removed the "id_" prefix when using "tokenize".

The next modification is to also use the token for the board name, for a similar reason: changing the board name would break incremental backups and generate duplicate boards, whereas using the token works.

Finally, I changed the backup list folders for use their full id, not just the short url, to be coherent with the other elements that do use the full id.

I understand that it breaks the previous behaviour of your perfectly fine software and I understand it you'd reject this pull request, but I just wanted to give back if this interests you.

Thank you again,

Cordially,

Felix

… instead of shortlinks, for more "coherent" behaviour.
…hy (where every element is updated but never deleted); and name-based simlinks that point to these tokens, which are reset on each backup to reflect the current board/list/cards structures and names.
@felixchenier
Copy link
Author

I also added the "symlinks" option, to create both a token-based file hierarchy (where every element is updated but never deleted); and name-based symlinks that point to these tokens, which are reset on each backup to reflect the current board/list/cards structures and names. I think this has a lot of potential, and it sure solves a problem for me.

I realize that the project now seems unmaintained, but here it is if it can help.

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.

1 participant