Re: GSOC git push pull to plone.app.theming
Dylan Jay <djay-n0pU0XVUApFWk0Htik3J/[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <CANyGbvfCNqxvH8BizPpS7-C3BAJMAf65YV_eW5PJFLvJnW9cnw@mail.gmail.com> |
On 8 Mar 2014 21:01, "Rok Garbas" <[email protected]> wrote: > > Quoting Dylan Jay (2014-03-07 23:48:47) > > > > On 8 Mar 2014 09:25, "Rok Garbas" <[email protected]> wrote: > > > > > > Quoting Martin Aspeli (2014-03-07 15:20:14) > > > > 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? > > > > > > > > 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 :) > > > > > > > > > > I think saner approach would be to have in browser editor with git support > > once > > > js-git is ready [1][2]. > > > > How does that help many people collaborate on the same code? > > > > you clone a repo, when ready you push it to wherever you host your git code. it > makes little sense to create our own git server. and since all editing happens > in browser (we dont touch plone) when theme is ready we can create zip file > (also you can do that with javascript) and upload it to plone. > > That's not really the use case. Some users edit their theme inside plone and some don't. Some edit it on a production server or across many production servers. Currently we manage this by constantly exporting a theme via a zip and checking it in and merging into a repo all the time, which is a pain. Imagine how nstead you could push and pull directly with plone like you can with heroku. > > -- > Rok Garbas - http://www.garbas.si ------------------------------------------------------------------------------ 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