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

Archive/Location Policies #28

Open
seandenigris opened this issue Jul 29, 2021 · 0 comments
Open

Archive/Location Policies #28

seandenigris opened this issue Jul 29, 2021 · 0 comments

Comments

@seandenigris
Copy link
Owner

Use case: I have Launcher GT templates. In over a year, I've never had to go back and use an old one, but since they've already been semi-manually created, it might be useful to keep the history around. However, I don't need it locally, but want to back the deprecated templates up to a server.

  • What to do if the server is not available? I was thinking about maybe queuing move commands and clearing the queue on next mounting/connection.
  • Design? How do we signal the library? Whose responsibility is the move primarily? Library? Resource? Collaboration?
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

No branches or pull requests

1 participant