Re: GSOC git push pull to plone.app.theming

So implementing git protocol as zodb blob  is possible.a single large blob
stores this entire diazo theme and some additional git objects

There will not be any problem in converting this blob file and storing it
in memory when we want to make changes to our theme.The changes made to the
theme will be written to the memory objects and when we save them-the diazo
theme and git objects will be converted back to zodb blob and stored in the
zodb database.

The zeo can then transfer this blob safely to our server storage.Dulwich
includes all the classes and features required for this purpose.

We are using this blob file as a backup for the theme.there will be two
copies of the theme one that is used in the site only diazo theme files
without git objects and second one is the blob backup discussed above.when
ever the developer makes changes they will be made to the theme as it is
done currently at the same time the blob storage brought to memory will
also get changed,git objects make recording to track the change whenever we
want to pull to previous state the changes are reflected in the original
diazo theme as well so maintaining the dated copies without making much
changes to existing mechanism is achieved.




On Sat, Mar 8, 2014 at 5:18 AM, Dylan Jay [via Plone] <
ml-node+s293351n7570477h73-PKuAHvtXa09l57MIdRCFDg@public.gmane.org> wrote:

>
> On 8 Mar 2014 02:20, "Martin Aspeli" <[hidden email]<http://user/SendEmail.jtp?type=node&node=7570477&i=0>>
> wrote:
> >
> > Not sure I've grokked all of the use cases here, but maybe it would be
> better to allow manipulation of file system files (eg resources/theme/*) in
> the theme editor (which would be pretty easy but will require careful
> security considerations) and use dulwch on those?
> >
>
> Unfortunately that approach isn't so scalable as it wouldn't work for more
> than one server. You could use NFS or similar but you'd have to deal with
> locking etc. You'd have to make sure the edit transactions were linked with
> got commits. Could end up being just as complex.
> Its about tracking changes to online code in a public cloud.
>
> > Trying to implement the git protocol with zodb blobs as backing storage
> sounds inanely complicated and error probe and unlikely to remain
> maintainable. git talks files :)
> >
>
> https://www.samba.org/~jelmer/dulwich/apidocs/dulwich.repo.MemoryRepo.html
>
> > Martin
> > --
> > Sent from Mailbox for iPhone
> >
> >
> > On Fri, Mar 7, 2014 at 4:14 PM, Guido Stevens <[hidden email]<http://user/SendEmail.jtp?type=node&node=7570477&i=1>>
> wrote:
> >>
> >> On 07/03/14 04:08, krishnatejaperannagari wrote:
> >> > Sorry sir,i got some misconceptions regarding the idea,So i am
> >> > sending this mail to see if i got the idea right.its a bit lengthy
> >> > because i want to check if i am correct or not:
> >>
> >> There's a few issues with your approach. Especially:
> >>
> >> > 5.Git also uses the object based storage approach and hence it
> >> > doesnt create any problems when used in combination with zodb or zeo.
> >>
> >> This is a "heroic assumption" i.e. very likely untrue.
> >>
> >> Git is a file-based object store. Dulwich uses that file-based object
> >> store. Plone uses ZODB which is also a file-based object store, but
> it's
> >> a *different* object store. Incompatible.
> >>
> >> You cannot manipulate Data.fs as if it was just a file in git. Well you
> >> can but that doesn't make sense. You cannot manipulate git files in the
> >> ZODB.
> >>
> >> The most sane route would be possibly to manipulate the git trees
> >> outside of the ZODB. And maybe use git replication, not ZEO
> replication,
> >> at a later stage.
> >>
> >> :*CU#
> >> --
> >> Guido Stevens | +31.43.3618933 | http://cosent.nl
> >>
> >> s o c i a l k n o w l e d g e t e c h n o l o g y
> >>
> >>
> >>
> ------------------------------------------------------------------------------
>
> >> Subversion Kills Productivity. Get off Subversion & Make the Move to
> Perforce.
> >> With Perforce, you get hassle-free workflows. Merge that actually
> works.
> >> Faster operations. Version large binaries. Built-in WAN optimization
> and the
> >> freedom to use Git, Perforce or both. Make the move to Perforce.
> >>
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> >> _______________________________________________
> >> Plone-developers mailing list
> >> [hidden email] <http://user/SendEmail.jtp?type=node&node=7570477&i=2>
> >> https://lists.sourceforge.net/lists/listinfo/plone-developers
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > Subversion Kills Productivity. Get off Subversion & Make the Move to
> Perforce.
> > With Perforce, you get hassle-free workflows. Merge that actually works.
> > Faster operations. Version large binaries.  Built-in WAN optimization
> and the
> > freedom to use Git, Perforce or both. Make the move to Perforce.
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> > _______________________________________________
> > Plone-developers mailing list
> > [hidden email] <http://user/SendEmail.jtp?type=node&node=7570477&i=3>
> > https://lists.sourceforge.net/lists/listinfo/plone-developers
> >
>
>
> ------------------------------------------------------------------------------
>
> Subversion Kills Productivity. Get off Subversion & Make the Move to
> Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works.
> Faster operations. Version large binaries.  Built-in WAN optimization and
> the
> freedom to use Git, Perforce or both. Make the move to Perforce.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> _______________________________________________
> Plone-developers mailing list
> [hidden email] <http://user/SendEmail.jtp?type=node&node=7570477&i=4>
> https://lists.sourceforge.net/lists/listinfo/plone-developers
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://plone.293351.n2.nabble.com/GSOC-git-push-pull-to-plone-app-theming-tp7564752p7570477.html
>  To unsubscribe from GSOC git push pull to plone.app.theming, click here<http://plone.293351.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=7564752&code=a3Jpc2huYXRlamFwZXJhbm5hZ2FyaUBnbWFpbC5jb218NzU2NDc1MnwtMTY2ODkwNzE1Mw==>
> .
> NAML<http://plone.293351.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>



-- 
krishna teja perannagari




--
View this message in context: http://plone.293351.n2.nabble.com/GSOC-git-push-pull-to-plone-app-theming-tp7564752p7570479.html
Sent from the Core Developers mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk

_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers