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

Client Rice Updating #54

Open
Luminarys opened this issue Apr 16, 2015 · 1 comment
Open

Client Rice Updating #54

Luminarys opened this issue Apr 16, 2015 · 1 comment

Comments

@Luminarys
Copy link
Contributor

Assuming the hash based system is implemented, whenever a client is updated, it should compare it's hash of a rice to the server's hash. If they differ, it will ask the user if they'd like to update. There should also be options for archiving old rices so they are not lost or if the new rice is broken it can easily be rolled back.

@Luminarys
Copy link
Contributor Author

I think the more proper way to do this would really be to just git clone the github repository and when updating is needed, symlinks will be removed, git repo will be updated, and then symlinks will be recreated.

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

No branches or pull requests

1 participant