Well, many folks use puppet in serverless configuration pushing the
manifest from a central git server via cron and applying locally the
configuration fetched. In this sense git IS used for deployement. And,
for a configuration management system as puppet this could be a
sensible thing to do - reduce load, scalability ecc.
2012/7/21, David Aguilar <dav...@gmail.com>:
> On Fri, Jul 20, 2012 at 4:28 PM, Martin Langhoff
> <martin.langh...@gmail.com> wrote:
>> On Fri, Jul 20, 2012 at 6:54 PM, Randal L. Schwartz
>> <mer...@stonehenge.com> wrote:
>>>>>>>> "Darek" == Darek Bridges <darek.brid...@me.com> writes:
>>> Darek> I use git for many things, but I am trying to work out the
>>> Darek> workflow to use git for deployment.
>> Heh. Best to keep in mind that it just doesn't work very well.
>> git-bigfiles, git-annex might help you, but look at the docs and
>> caveats carefully.
>> Perhaps use rsync, unison work better for you.
> I'm not sure if it was the "big files" part that Randal was responding
> to. IIUC it was the "using git for deployment" part.
> Packaging tools (Makefiles, .rpm, .deb, etc) are a better suited for
> deploying software.
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Inviato dal mio dispositivo mobile
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html