Hi, Magnus, The Enterprise I'm working at has separated its DEV, TEST, and PRODUCTION environments with firewalls.
Code may be PUSHed to a Code Management System in DEV ONLY. In the TEST and PRODUCTION environments, the CMS repository MUST (cf. RFC-2119) be PULL ONLY. In proposing a CMS, I MUST include the possibility that the same user has access to the same project from more than one environment, so controlling access by user won't work. If the same user has the same access to the same repository in DEV and TEST, what stops that user from adding code via the TEST environment? Thanks! David > On Jan 7, 2016, at 02:59, Magnus Therning <mag...@therning.org> wrote: > > What do you mean by "enviroment" here? > > It's common to authorize by user, or by group, but I simply don't > understand what you mean by "environment". > -- David - Offbeat dafydd - Online http://pgp.mit.edu/ ----5----1----5----2----5----3----5----4----5----5----5----6----5----7-- Werner Heisenberg is driving down the autobahn. A police officer pulls him over. The officer says, "Excuse me, sir, do you know how fast you were going?" "No," replies Dr. Heisenberg, "but I know where I am." -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
