git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git with large files...

From
KLKalle Launiala <kalle.launiala@gmail.com>
Date
Jul 23, 2012, 07:23 UTC
Message-ID
<CAHLTmjknX3g08Huv6iyV8uVc9mXjRY_rSBAKVPGwOqDk-O7GTA@mail.gmail.com>
In-Reply-To
<CAMK1S_hO5g5p4NjoVcxYFTt_KZ-wBRJk=OCveeszwr8U2LeZbg@mail.gmail.com>
2012/7/23 Sitaram Chamarty <sitaramc@gmail.com>:
Show 18 quoted lines
> On Mon, Jul 23, 2012 at 2:24 AM, Junio C Hamano <gitster@pobox.com> wrote:
>> merlyn@stonehenge.com (Randal L. Schwartz) writes:
>>
>>>>>>>> "Darek" == Darek Bridges <darek.bridges@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.
>>>
>>> Don't.
>>
>> Yeah, "don't think 'git checkout' is a way to 'deploy'".  Using Git
>> as a transport measure is probably fine.
>
> You can also try
> http://sitaramc.github.com/the-list-and-irc/deploy.html.  Whether it's
> saying you *can* use git for deploying something, or you *can* but
> *should not*, or you *cannot*, will depend on your own thoughts on the
> matter ;-)
Nice summary list of options!
If you combine that with several key concepts:
1. You plan and design to deploy - hence you have separate deploy
repositories dedicated for that
2. You design for modularity and complete audit trail, hence you have this:
http://abstractiondev.files.wordpress.com/2011/12/git-distribution-overview.png

You can combine the staging with any approach, that *tries* to maintain the local version copy. But if any problem arises in pull/fetch, simply trash that part and get it from fresh (or just use the git archive approach).

Now this model would introduce complete and as detailed security enforcement - as the deployment can validate with certificates (from the additional catalogue-metadata binding, whether there is authorized party confirmed signature available for the wished deployable version).

I don't see much overhead in any of the steps here - and the deployment is as detailed and as securely controlled as desired. With just Git (and well, possibly GnuPG or alike common tool for digital certificate work).

Everything is also transparent - which is very important in having that complete control and audit trail.

Previous: Sitaram ChamartyNext: Drew Northup
Message 14 of 15 in “git with large files...”
  1. Darek BridgesJul 20, 2012
  2. Randal L. SchwartzJul 20, 2012
  3. Martin LanghoffJul 20, 2012
  4. David AguilarJul 21, 2012
  5. Elia PintoJul 21, 2012
  6. Martin LanghoffJul 21, 2012
  7. Elia PintoJul 21, 2012
  8. Elia PintoJul 22, 2012
  9. Kalle LaunialaJul 22, 2012
  10. NickJul 21, 2012
  11. Martin LanghoffJul 21, 2012
  12. Junio C HamanoJul 22, 2012
  13. Sitaram ChamartyJul 23, 2012
  14. Kalle LaunialaJul 23, 2012
  15. Drew NorthupJul 29, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.