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

clone repo & history to disconnected server

From
KSKermit Short <heraldstorm@gmail.com>
Date
Sep 7, 2017, 16:50 UTC
Message-ID
<CABjWGHx5VQaLubeWsqWJzufDU3vt9BSS0=LpwgOtMDYhje=qMA@mail.gmail.com>

Greetings! I have to set up a workflow where I'll be developing and testing on one network, and then deploying to production on a disconnected network. I'd like to be able to have the full commit history for all branches, tags, etc. on the disconnected side, in case I need to perform a roll-back, create a hot-fix, etc.

Most of the solutions I see involve creating a mirror clone that is then merged with a different repository. My problem is that my servers are on two separate networks and I am unable to talk to both repos from the same computer. I'd need to be able to transport the files using sneaker net prior to importing on the second repo. I need to keep the production repo in full working sanity...i.e. import only new changes or completely overwrite the repository such that the full project history is intact and working.

Does anyone have any suggestions? I've been looking at the archive command but I'm not sure it would bring out the full project history. Thanks in advance for your help!!

Next: Stefan Beller
Message 1 of 3 in “clone repo & history to disconnected server”
  1. Kermit ShortSep 7, 2017
  2. Stefan BellerSep 7, 2017
  3. Kermit ShortSep 7, 2017

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.