Hi Thomas,
Thanks for the recipe. I'm planning to do a install next week and simulate
a few disaster scenarios. I love blowing stuff up when nothing really gets
hurt. :)
Carlos
On Jul 26, 2012 5:39 AM, "Thomas Kjeldahl Nilsson"
wrote:
> Hello Carlos (& Bilal),
>
> backing up a Gitorious ins
Hello all,
I have this scritp for take dump the mysql, I hope you can try!
#!/bin/bash
PORT="3306"
USER="root"
PASSWORD="Password"
mysql=/usr/bin/mysql
mysqldump=/usr/bin/mysqldump
TABLES=`$mysql -P $PORT -u $USER --password=$PASSWORD --execute="SHOW
DATABASES;" |awk '{print($1)}' |grep -v "Data
Hello Carlos (& Bilal),
backing up a Gitorious instance entails the following:
1: Dump the mysql database state to file (which contains metadata about
users, projects, repos etc)
2: Make a recursive copy of the directory where repos are stored (as you
have already mentioned)
3: Ssh keys of
I have the same question, which I will divide into parts:
A. What is the process for "dumping" the full state of a gitorious
instance?
B. What is the process of (re)loading a dump to overwrite the state of a
gitorious instance?
My focus is disaster recovery. So just cloning the project repo
