I suggest you read through the code in the backup.rake file, and apply
what you see there: you'll basically just need to make a recursive copy
of the repository base directory as well as an mysqldump of the db
(where users and metadata is stored.) Based on the repos and db you'll
be able to restore most of the state of your Gitorious instance at
another installation (but again, read and consider the backup.rake file)
cheers,
Thomas
On 08/27/2012 10:01 PM, luist wrote:
Ok the diagnostics worked!
Can i have some instructions on how to backup and restore my gitorious
manually?
Em segunda-feira, 27 de agosto de 2012 14h05min32s UTC-3, Thomas
Kjeldahl Nilsson escreveu:
The CLI diagnostics rake task was added just a week or two ago, so
it's fairly recent: if the installation isn't constrained by
having to run on a stable tag/version, then you can just git pull
the latest changes from gitorious mainline. If you have to sit on
a stable tag you'll have to wait until we tag a new minor version
of Gitorious (probably very soon).
cheers,
Thomas
On 08/27/2012 06:59 PM, luist wrote:
Well.. looks like it doesn't have diagnostics:
http://pastie.org/4598245 <http://pastie.org/4598245>
What exactly should i update?
Em segunda-feira, 27 de agosto de 2012 13h50min36s UTC-3, Thomas
Kjeldahl Nilsson escreveu:
First off, doublecheck that you're running the rake task from
the root dir of your gitorious installation ie. where you
find Rakefile, /config, /log, etc. If so, then try running
this to see which rake tasks are actually available on your
installation:
sudo su git -c "RAILS_ENV=production bundle exec rake -T"
-thomas
On 08/27/2012 06:32 PM, luist wrote:
That worked... now i got this:
$ sudo su git -c "RAILS_ENV=production bundle exec rake
diagnostics:summary"
(in /var/www/git.metasys.com.br/gitorious
<http://git.metasys.com.br/gitorious>)
rake aborted!
Don't know how to build task 'diagnostics:summary'
(See full trace by running task with --trace)
Em segunda-feira, 27 de agosto de 2012 12h56min29s UTC-3,
Thomas Kjeldahl Nilsson escreveu:
Hello again,
Running bundle install straight up only installs the
dependency gems in a path specific to your current user,
not the gitorious "git" user. So you probably just need
to run it for the gitorious user as well, if you have
not already done so:
sudo su git -c "bundle install"
cheers,
Thomas
On 08/27/2012 05:31 PM, luist wrote:
Hello. This seems to be very useful, but the old
machine has some problems and I can only access it
read-only to backup the data manually.
I checked the new resource to diagnose the new
instalation. I tried to use it but got this:
http://pastie.org/4597818 <http://pastie.org/4597818>
What am i missing?
Em segunda-feira, 27 de agosto de 2012 07h49min47s
UTC-3, Thomas Kjeldahl Nilsson escreveu:
Hi Luist,
I recently added a pair of Rake tasks to make
snapshotting/restoring
Gitorious state simpler. Pull from mainline, and
check out
/lib/tasks/backup.rake (documentation included in
the source code of the
rake tasks.)
best regards,
Thomas
On 08/24/2012 11:17 PM, luist wrote:
> Hello,
>
> I'm having many problems configuring a new
machine to run gitorious
> and migrating the data from the old one.
>
> Can anyone point me what should i backup and what
should i re-do from
> scratch?
> Where are the user/login information stored?
> --
> To post to this group, send email to
[email protected]
> To unsubscribe from this group, send email to
> [email protected]
--
best regards,
Thomas Kjeldahl Nilsson
http://gitorious.com
--
best regards,
Thomas Kjeldahl Nilsson
http://gitorious.com
--
best regards,
Thomas Kjeldahl Nilsson
http://gitorious.com
--
best regards,
Thomas Kjeldahl Nilsson
http://gitorious.com
--
best regards,
Thomas Kjeldahl Nilsson
http://gitorious.com
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
