I recommend the Git book, when you have several hours free. I also
recommend making lots of commits. I keep forgetting to commit often
enough, then it's a bit of a pain to split up the changes I've made into
the right commits. You can easily join multiple commits into one bigger
one, but it can
On 17 September 2014 22:31:28 BST, Bruno Girin wrote:
>On 17 September 2014 20:47, Gareth France
>wrote:
>
>>
>> Not helpful for solving the immediate problem I know, but for the
>>> future the issue would be easy to solve if you kept a master copy of
>>> your source in a version control syste
On 17 September 2014 20:47, Gareth France wrote:
>
> Not helpful for solving the immediate problem I know, but for the
>> future the issue would be easy to solve if you kept a master copy of
>> your source in a version control system such as git. Then if the site
>> becomes compromised you can
On 17/09/14 21:52, Colin Law wrote:
On 17 September 2014 20:47, Gareth France wrote:
Not helpful for solving the immediate problem I know, but for the
future the issue would be easy to solve if you kept a master copy of
your source in a version control system such as git. Then if the site
beco
On 17 September 2014 20:47, Gareth France wrote:
>
>> Not helpful for solving the immediate problem I know, but for the
>> future the issue would be easy to solve if you kept a master copy of
>> your source in a version control system such as git. Then if the site
>> becomes compromised you can j
Not helpful for solving the immediate problem I know, but for the
future the issue would be easy to solve if you kept a master copy of
your source in a version control system such as git. Then if the site
becomes compromised you can just replace it with the correct code.
Git is trivially easy t
On 17 September 2014 14:08, Gareth France wrote:
> I understand. In which case the big issue would be weeding out old redundant
> files and ensuring no hidden files exist from this recent hack before
> creating this system.
I did say it did not help you in your current predicament, but may
help i
On 17 September 2014 14:08, Gareth France wrote:
> I understand. In which case the big issue would be weeding out old redundant
> files and ensuring no hidden files exist from this recent hack before
> creating this system.
You're right, we're really talking hypotheticals that don't help you
out
I understand. In which case the big issue would be weeding out old
redundant files and ensuring no hidden files exist from this recent hack
before creating this system.
On 17 Sep 2014 14:01, "Daniel Llewellyn" wrote:
> On 17 September 2014 08:25, Gareth France wrote:
> > Sounds great. My backup
On 17 September 2014 08:25, Gareth France wrote:
> Sounds great. My backups are stored on a hard drive here so can't be
> compromised but I'd love to find a way to automate it. I'll look into this
> later.
I think the point that Colin is trying to convey is that
version-control is NOT a backup st
Sounds great. My backups are stored on a hard drive here so can't be
compromised but I'd love to find a way to automate it. I'll look into this
later.
On 17 Sep 2014 08:21, "Colin Law" wrote:
> On 17 September 2014 07:34, Gareth France wrote:
> > I do keep regular backups however the issue is t
On 17 September 2014 07:34, Gareth France wrote:
> I do keep regular backups however the issue is that this has been sitting
> silently for some time and changes made since the last clean backup would
> have been lost.
A VCS is much more than a set of backups. Since the master resides
away from
12 matches
Mail list logo
