As there's a concept of "application" for perkeep, I'd vote for using perkeep as is through the pkg/client lib - like github.com/tgulacsi/camproxy/camutil
alimoeeny <[email protected]> ezt írta (időpont: 2018. máj. 26., Szo, 14:15): > Hey Perkeep people, > > I want to use Perkeep's, blob storage + indexing + search inside a larger > service. > I want to have my own auth and access control and CDN in front. > > I of course want to keep up to date with all the progress you are and will > be making, > > Does it make more sense to use perkeep as libraries and build my services > on top, or would it make more sense to run per keep as is behind my service > and have my service call perkeep api and act a some sort of proxy ? > > My question is more about your longer term plans, do you expect people to > use Perkeep as library(ies) and will keep your "internal" api rather > stable? or you'd rather be free to make changes to your internal api > frequently and break things but keep your "external" api more stable? > > Am I making sense? > > Ali > > -- > You received this message because you are subscribed to the Google Groups > "Perkeep" 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. > -- You received this message because you are subscribed to the Google Groups "Perkeep" 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.
