Re: help with gitlab on buster

2020-02-19 Thread tomas
On Wed, Feb 19, 2020 at 10:03:04AM +0200, Andrei POPESCU wrote: > On Ma, 18 feb 20, 12:25:40, john doe wrote: > > > > Don't forget that the repositories on a server/remote repositories are > > to be 'bare' and 'ending with '.git'. > > Using a bare as remote has some advantages in case you don't a

Re: help with gitlab on buster

2020-02-19 Thread john doe
On 2/19/2020 9:03 AM, Andrei POPESCU wrote: > On Ma, 18 feb 20, 12:25:40, john doe wrote: >> >> Don't forget that the repositories on a server/remote repositories are >> to be 'bare' and 'ending with '.git'. > > Using a bare as remote has some advantages in case you don't actually > need a working

Re: help with gitlab on buster

2020-02-19 Thread Andrei POPESCU
On Ma, 18 feb 20, 12:25:40, john doe wrote: > > Don't forget that the repositories on a server/remote repositories are > to be 'bare' and 'ending with '.git'. Using a bare as remote has some advantages in case you don't actually need a working tree "there", it is however not a requirement. Kind

Re: help with gitlab on buster

2020-02-18 Thread john doe
On 2/18/2020 11:14 AM, Graham Seaman wrote: > > On 17/02/2020 22:41, David Wright wrote: >> On Mon 17 Feb 2020 at 15:27:06 (+), Graham Seaman wrote: >>> I hadn't thought of running a VM clone of the server - might be >>> generally useful. But the server's main jobs are as a router, >>> firewall

Re: help with gitlab on buster

2020-02-18 Thread Graham Seaman
On 17/02/2020 22:41, David Wright wrote: On Mon 17 Feb 2020 at 15:27:06 (+), Graham Seaman wrote: I hadn't thought of running a VM clone of the server - might be generally useful. But the server's main jobs are as a router, firewall, dnsmasq, mail server, which is where the main problems u

Re: help with gitlab on buster

2020-02-17 Thread David Wright
On Mon 17 Feb 2020 at 15:27:06 (+), Graham Seaman wrote: > On 17/02/2020 06:30, john doe wrote: > > On 2/16/2020 11:45 PM, Graham Seaman wrote: > > > > > Of course, though this would be easier if I was more sure where > > > everything was. But the data's no use without the software to read it.

Re: help with gitlab on buster

2020-02-17 Thread Graham Seaman
On 17/02/2020 06:30, john doe wrote: On 2/16/2020 11:45 PM, Graham Seaman wrote: Of course, though this would be easier if I was more sure where everything was. But the data's no use without the software to read it. https://docs.gitlab.com/ee/raketasks/backup_restore.html Thanks - bit embaras

Re: help with gitlab on buster

2020-02-16 Thread john doe
On 2/16/2020 11:45 PM, Graham Seaman wrote: > > On 14/02/2020 17:39, john doe wrote: >> On 2/14/2020 5:42 PM, Graham Seaman wrote: >>> I run a debian house server for firewall, routing etc. The last few >>> years I've also run gitlab on it, which I use to manage text files I >>> work on from an ass

Re: help with gitlab on buster

2020-02-16 Thread Graham Seaman
On 14/02/2020 17:39, john doe wrote: On 2/14/2020 5:42 PM, Graham Seaman wrote: I run a debian house server for firewall, routing etc. The last few years I've also run gitlab on it, which I use to manage text files I work on from an assortment of laptops/PCs; I have a lot of these files (curre

Re: help with gitlab on buster

2020-02-14 Thread deloptes
john doe wrote: > First off, backup your data! :) also no one upgrades production stuff without testing the procedure - right?!

Re: help with gitlab on buster

2020-02-14 Thread john doe
On 2/14/2020 5:42 PM, Graham Seaman wrote: > I run a debian house server for firewall, routing etc. The last few > years I've also run gitlab on it, which I use to manage text files I > work on from an assortment of laptops/PCs; I have a lot of these files > (currently around 12 Gb) and really don'