Operations grimoire/Git operations in production containers

From Nasqueron Agora
Revision as of 02:17, 24 March 2018 by Dereckson (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

📕📁📜 Old technical information :: content warning

⌛ This Nasqueron Operations Grimoire page hasn't been updated for a long time.

☣ As our infrastructure evolves quickly, there is a good chance this information is outdated or now inaccurate. Be careful and consider update it.

➡️ To assert the information is still up-to-date or not, you can check the history of the relevant role in our Operations repository.

Sometimes, there is a need to use Git from a container.

If you're on Dwellers and not inside a container, you're interested by Dwellers to DevCentral.

This is not a good practice

Fill a task on Phabricator and explains why you need to do this.

These should be addressed and eliminated as a goal.

When deployed code diverge than upstream

  1. Create a production branch to store any edited code
  2. Document on the grimoire the need to rebase this production branch against upstream relevant branch (generally master)

Git configuration

If you need to quickly use Git in production, use the following commit references if you use a shared ops account:

$ cat > ~/.gitconfig
[user]
        email = ops-noreply@nasqueron.org
        name = Nasqueron Operations

Known current cases

  • Rebase a production branch against a master branch: we should use instead allow two containers for the same service, to be prepare a new container from a new image instead of rebase the code in the prod container directly.