Hi Eric, Have you got any sample on how to do the above? Cheers
On Thursday, April 3, 2014 at 5:52:05 PM UTC+1, Eric Drechsel wrote: > > I am not a core contributor but I'm interested in this topic. > > Camlistore is totally viable for storing content objects and "assets" that > will be composed by some outside process into a publicly facing website (or > several). > > Possible routes for integration: > > - Store and access your content objects in Camli via the FUSE filesystem. > I have a root called "Sites" and each subdirectory is a site. This is a > nice first step for a system which already has content stored as files, > since you can just add cammount to your build script. > - Access Camli via the HTTP API. Creating API bindings should be a fairly > straightforward task. I haven't looked into this yet but I was going to use > the JS bindings in server/camlistored/ui as a starting point (although > probably start clean without the Closure Lib stuff) > > And of course once you have full API access you can start storing metadata > natively using claims, and leverage the indexer's search capabilities to > fetch collections of content objects. > > Hope this is helpful > > On Thursday, April 3, 2014 2:27:13 AM UTC-7, Khaja Minhajuddin wrote: >> >> I am building a CMS (http://getsimplesite.com/) and wanted to know if >> camlistore can be used to create a distributed/redundant file store (for >> web pages and js/css/image assets). >> > -- 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.
