3 ms·
I have to do this too because I work for different client and every client have their own gitlab which they only give access to account with their corporate ema
by maeln 7y ago
I have to do this too because I work for different client and every client have their own gitlab which they only give access to account with their corporate email.
So i have to commit under myname@client1.com for client 1, my.name@client2.fr for client 2 and so on.
Since I usually have to work on several repositories, I usually do what OP presented. I have one directory per client with each their own configuration and their repositories.
- pampa 7y agoI used to have the client per directory setup too. But then took it one step further. Now for every client i set up a separate VMWare Workstation virtual machine with all the relevant git config files, ssh keys, software and build dependencies etc. That way every client is compartmentalized and there is limited chance of data or code leaking between clients. And i can always mid-session put the VM on pause, switch to another client and then resume right where i left, with all the editor windows open and services running. I call it the container approach to workspaces.
- chrisweekly 7y agoSounds good. +1 for writing it up and sharing dets! :)
- p_l 7y agoSounds a bit like what Qubes does