I usually create/modify permanode files/dirs through cammount, which takes care of setting camliContent for you. I just created a ticket to add some usage examples to the docs: https://github.com/camlistore/camlistore/issues/789
On Wed, May 25, 2016 at 7:54 PM, Alok Parlikar <[email protected]> wrote: > > >> > (a) camput file $PATH creates a static (deduplicated) snapshot of >>> the >>> >> > path. >>> >> > It's great for backups, and is the foundation on which the other >>> mode is >>> >> > built. You can restore with camget -o $OUTDIR $REF. >>> >> > (b) camput file -filenodes $PATH creates a mutable "permanode" for >>> each >>> >> > file/directory under the path. This mode is appropriate when you >>> plan to >>> >> > treat Camlistore as the source of truth going forward. Unlike (a), >>> the >>> >> > command isn't idempotent; each run creates a new set of permanodes. >>> >> > Eric, I didn't quite understand what you meant by "treat Camlistore as the > source of truth going forward". What would be a use case where one would do > that? (Is it the first backup -- but in that case, it would be tricky to > add camliContent attr to each permanode.. ) > > Alok > > -- > You received this message because you are subscribed to the Google Groups > "Camlistore" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- best, Eric eric.pdxhub.org <http://pdxhub.org/people/eric> -- You received this message because you are subscribed to the Google Groups "Camlistore" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
