-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
many people have asked for the ability to "synchronize" a folder of rel files (and maybe data?) with a database.
following are some notes on design work is needed before implementing the command/s.
design issues:
- fully recursive? or designated folder only? (or options for both?)
- eg: rai sync ./rel/*.rel or ./rel/... or ?
- do we recognize when files have been changed on server to avoid overwrite (w/o warning)
- consider recording sha256 of model file when its installed by cli, which we can then use to detect when it doesnt match currently installed model (meaning updated elsewhere) and/or where it doesnt match local file? (maybe this is too much mechanism)
- .. if we do go down this path, we may need to compute hierarchical hashes (like git) for perf? maybe a slippery slope?
- explicit pull/push vs. "smart" sync? (maybe both?)
- pull/push would overwrite (possibly with warning), sync would synchronize folder and directory with latest in each?