Re: [gitorious] Migrating gitorious to another machine

[Marius Mårnes Mathiesen]

On Thu, Sep 27, 2012 at 11:49 PM, Thomas Kjeldahl Nilsson <
tho...@gitorious.org> wrote:

> Hm, not sure what the issue could be then. Marius, do you have any insight
> here?
>

Could it be that the hooks aren't symlinked correctly into the repository
itself?
If you look inside a repository.git, you should see something like this:

hooks -> ../../.hooks

That link will usually point to a .hooks symlink in your repository root,
which again is a symlink to the data/hooks directory in your Gitorious app
root. Does it?

Cheers,
- Marius

-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com

Re: [gitorious] Migrating gitorious to another machine

[Thomas Kjeldahl Nilsson]

Hm, not sure what the issue could be then. Marius, do you have any insight 
here? 

-- 
Best regards / vennlig hilsen
Thomas Kjeldahl Nilsson
http://gitorious.com



On Thursday, September 27, 2012 at 11:45 PM, Luis Tiago C Eterovick wrote:

> Yes:
> 
> /var/www/gitorious/data/hooks# ls -la
> total 80
> drwxr-xr-x 2 git git 4096 Sep 27 17:34 .
> drwxr-xr-x 4 git git 4096 Sep 27 12:49 ..
> lrwxrwxrwx 1 git git 6 Sep 27 12:49 .hooks -> .hooks
> -rw-r--r-- 1 git git 441 Sep 27 12:49 applypatch-msg
> -rw-r--r-- 1 git git 781 Sep 27 12:49 commit-msg
> -rwxr-xr-x 1 git git 1530 Sep 27 12:49 custom-post-receive.sample
> -rwxr-xr-x 1 git git 1409 Sep 27 12:49 custom-pre-receive.sample
> -rwxr-xr-x 1 git git 1266 Sep 27 12:49 custom-update.sample
> -rw-r--r-- 1 git git 1777 Sep 27 12:49 messaging.rb
> -rw-r--r-- 1 git git 152 Sep 27 12:49 post-commit
> -rwxr-xr-x 1 git git 2239 Sep 27 12:49 post-receive
> -rwxr-xr-x 1 git git 207 Sep 27 12:49 post-update
> -rw-r--r-- 1 git git 388 Sep 27 12:49 pre-applypatch
> -rw-r--r-- 1 git git 1696 Sep 27 12:49 pre-commit
> -rw-r--r-- 1 git git 4262 Sep 27 12:49 pre-rebase
> -rwxr-xr-x 1 git git 4377 Sep 27 12:49 pre-receive
> -rw-r--r-- 1 git git 2346 Sep 27 12:49 pre_receive_guard.rb
> -rw-r--r-- 1 git git 233 Sep 27 12:49 rails_env.rb
> -rwxr-xr-x 1 git git 1736 Sep 27 12:49 update
> 
> 2012/9/27 Thomas Kjeldahl Nilsson  (mailto:tho...@gitorious.org)>
> > And the data/hooks/pre-receive hook is executable and owned by the git user?
> > 
> > --
> > Best regards / vennlig hilsen
> > Thomas Kjeldahl Nilsson
> > http://gitorious.com
> > 
> > 
> > 
> > On Thursday, September 27, 2012 at 11:42 PM, Luis Tiago C Eterovick wrote:
> > 
> > > We have made a new installation using ubuntu 12.04. The http url seems to 
> > > be ok now, but we're still getting that fatal error:
> > > 
> > > FATAL -- : The pre-receive hook is not executable
> > > 
> > > We've tried creating the folder git-shell-commands with help and list but 
> > > it didn't work.
> > > 
> > > Any help please?
> > > 
> > > 2012/9/21 Luis Tiago C Eterovick  > > (mailto:lu...@syst.com.br) (mailto:lu...@syst.com.br)>
> > > > What about the wrong url in http? How could i fix that?
> > > > 
> > > > 
> > > > 2012/9/21 Thomas Kjeldahl Nilsson  > > > (mailto:tho...@gitorious.org) (mailto:tho...@gitorious.org)>
> > > > > Hm, don't have any further suggestions just off the top of my head. 
> > > > > Marius, any bright ideas?
> > > > > 
> > > > > --
> > > > > Best regards / vennlig hilsen
> > > > > Thomas Kjeldahl Nilsson
> > > > > http://gitorious.com
> > > > > 
> > > > > 
> > > > > 
> > > > > On Friday, September 21, 2012 at 9:49 PM, Luis Tiago C Eterovick 
> > > > > wrote:
> > > > > 
> > > > > > The hooks dir seems fine and gitorious_user is set to git:
> > > > > > 
> > > > > > http://pastie.org/4775055
> > > > > > 
> > > > > > Although i have one proc running as root. Is that problem? No idea 
> > > > > > how to fix that...
> > > > > > 
> > > > > > 2012/9/21 Thomas Kjeldahl Nilsson  > > > > > (mailto:tho...@gitorious.com) (mailto:tho...@gitorious.com) 
> > > > > > (mailto:tho...@gitorious.com)>
> > > > > > > Things to check: could it be an issue with permissions on your 
> > > > > > > gitorious files? What's the current permissions on the 
> > > > > > > data/hooks/pre-receive file (and other files in same directory?) 
> > > > > > > Verify that they are owned by the gitorous user (usually the user 
> > > > > > > with username 'git'). Also, please check that they are still 
> > > > > > > executable.
> > > > > > > 
> > > > > > > Here's an example of how the permissions look in a correctly 
> > > > > > > configured Gitorious instance:
> > > > > > > https://dl.dropbox.com/u/1858732/data-hooks-dir.png
> > > > > > > 
> > > > > > > Generally, the whole gitorous directory structure should be owned 
> > > > > > > by the same user that owns all the processes etc, the same user 
> > > > > > > defined as gitorious_user in config/gitorious.yml.
> > > > > > > 
> > > > > > > cheers,
> > > > > > > Thomas
> > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > > On 09/21/2012 08:54 PM, Luis Tiago C Eterovick wrote:
> > > > > > > > Hey i had to configure Gitorious on a third machine. I got the 
> > > > > > > > same problem with the URLs missing, but i fixed it deleting 
> > > > > > > > all.js and copying it again. The clear script didnt work.
> > > > > > > > 
> > > > > > > > Now i have this problem when cloning/pushing projects (works 
> > > > > > > > only using git url, but not http, which is accessing 
> > > > > > > > git.gitorious.metasysdevel.com.br 
> > > > > > > > (http://git.gitorious.metasysdevel.com.br) 
> > > > > > > > (http://git.gitorious.metasysdevel.com.br) 
> > > > > > > > (http://git.gitorious.metasysdevel.com.br) instead of just 
> > > > > > > > gitorious.metasysdevel.com.br 
> > > > > > > > (http://gitorious.metasysdevel.com.br) 
> > > > > > > > (http://gitorious.metasysdevel.com.br) 
> > > > > > > > (http://gitorio

Re: [gitorious] Migrating gitorious to another machine

[Thomas Kjeldahl Nilsson]

And the data/hooks/pre-receive hook is executable and owned by the git user? 

-- 
Best regards / vennlig hilsen
Thomas Kjeldahl Nilsson
http://gitorious.com



On Thursday, September 27, 2012 at 11:42 PM, Luis Tiago C Eterovick wrote:

> We have made a new installation using ubuntu 12.04. The http url seems to be 
> ok now, but we're still getting that fatal error:
> 
> FATAL -- : The pre-receive hook is not executable
> 
> We've tried creating the folder git-shell-commands with help and list but it 
> didn't work.
> 
> Any help please?
> 
> 2012/9/21 Luis Tiago C Eterovick  (mailto:lu...@syst.com.br)>
> > What about the wrong url in http? How could i fix that?
> > 
> > 
> > 2012/9/21 Thomas Kjeldahl Nilsson  > (mailto:tho...@gitorious.org)>
> > > Hm, don't have any further suggestions just off the top of my head. 
> > > Marius, any bright ideas?
> > > 
> > > --
> > > Best regards / vennlig hilsen
> > > Thomas Kjeldahl Nilsson
> > > http://gitorious.com
> > > 
> > > 
> > > 
> > > On Friday, September 21, 2012 at 9:49 PM, Luis Tiago C Eterovick wrote:
> > > 
> > > > The hooks dir seems fine and gitorious_user is set to git:
> > > > 
> > > > http://pastie.org/4775055
> > > > 
> > > > Although i have one proc running as root. Is that problem? No idea how 
> > > > to fix that...
> > > > 
> > > > 2012/9/21 Thomas Kjeldahl Nilsson  > > > (mailto:tho...@gitorious.com) (mailto:tho...@gitorious.com)>
> > > > > Things to check: could it be an issue with permissions on your 
> > > > > gitorious files? What's the current permissions on the 
> > > > > data/hooks/pre-receive file (and other files in same directory?) 
> > > > > Verify that they are owned by the gitorous user (usually the user 
> > > > > with username 'git'). Also, please check that they are still 
> > > > > executable.
> > > > > 
> > > > > Here's an example of how the permissions look in a correctly 
> > > > > configured Gitorious instance:
> > > > > https://dl.dropbox.com/u/1858732/data-hooks-dir.png
> > > > > 
> > > > > Generally, the whole gitorous directory structure should be owned by 
> > > > > the same user that owns all the processes etc, the same user defined 
> > > > > as gitorious_user in config/gitorious.yml.
> > > > > 
> > > > > cheers,
> > > > > Thomas
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > On 09/21/2012 08:54 PM, Luis Tiago C Eterovick wrote:
> > > > > > Hey i had to configure Gitorious on a third machine. I got the same 
> > > > > > problem with the URLs missing, but i fixed it deleting all.js and 
> > > > > > copying it again. The clear script didnt work.
> > > > > > 
> > > > > > Now i have this problem when cloning/pushing projects (works only 
> > > > > > using git url, but not http, which is accessing 
> > > > > > git.gitorious.metasysdevel.com.br 
> > > > > > (http://git.gitorious.metasysdevel.com.br) 
> > > > > > (http://git.gitorious.metasysdevel.com.br) instead of just 
> > > > > > gitorious.metasysdevel.com.br 
> > > > > > (http://gitorious.metasysdevel.com.br) 
> > > > > > (http://gitorious.metasysdevel.com.br), nor ssh, which gives me 
> > > > > > fatal error):
> > > > > > 
> > > > > > $ git clone 
> > > > > > git://gitorious.metasysdevel.com.br/autolog-2-0/autolog-2-0.git 
> > > > > > (http://gitorious.metasysdevel.com.br/autolog-2-0/autolog-2-0.git) 
> > > > > > (http://gitorious.metasysdevel.com.br/autolog-2-0/autolog-2-0.git)
> > > > > > Cloning into 'autolog-2-0'...
> > > > > > remote: Counting objects: 68, done.
> > > > > > remote: Compressing objects: 100% (46/46), done.
> > > > > > remote: Total 68 (delta 15), reused 0 (delta 0)
> > > > > > Receiving objects: 100% (68/68), 12.70 KiB, done.
> > > > > > Resolving deltas: 100% (15/15), done.
> > > > > > 
> > > > > > 
> > > > > > $ git clone 
> > > > > > https://git.gitorious.metasysdevel.com.br/autolog-2-0/autolog-2-0.git
> > > > > > Cloning into 'autolog-2-0'...
> > > > > > error: Couldn't resolve host 'git.gitorious.metasysdevel.com.br 
> > > > > > (http://git.gitorious.metasysdevel.com.br) 
> > > > > > (http://git.gitorious.metasysdevel.com.br)' while accessing 
> > > > > > https://git.gitorious.metasysdevel.com.br/autolog-2-0/autolog-2-0.git/info/refs
> > > > > > fatal: HTTP request failed
> > > > > > 
> > > > > > $ git clone g...@gitorious.metasysdevel.com.br 
> > > > > > (mailto:g...@gitorious.metasysdevel.com.br):autolog-2-0/autolog-2-0.git
> > > > > >  
> > > > > > (mailto:g...@gitorious.metasysdevel.com.br:autolog-2-0/autolog-2-0.git)
> > > > > > Cloning into 'autolog-2-0'...
> > > > > > 
> > > > > > == Gitorious: 
> > > > > > ==
> > > > > > Fatal error, please contact support
> > > > > > 
> > > > > > 
> > > > > > fatal: The remote end hung up unexpectedly
> > > > > > 
> > > > > > Logs gave me this for this last case:
> > > > > > 
> > > > > > ==> gitorious_auth.log <==
> > > > > > I, [2012-09-21 16:15:22#2590] INFO -- : Co

Re: [gitorious] Migrating gitorious to another machine

[Thomas Kjeldahl Nilsson]

Hm, don't have any further suggestions just off the top of my head. Marius, any 
bright ideas? 

-- 
Best regards / vennlig hilsen
Thomas Kjeldahl Nilsson
http://gitorious.com



On Friday, September 21, 2012 at 9:49 PM, Luis Tiago C Eterovick wrote:

> The hooks dir seems fine and gitorious_user is set to git:
> 
> http://pastie.org/4775055
> 
> Although i have one proc running as root. Is that problem? No idea how to fix 
> that...
> 
> 2012/9/21 Thomas Kjeldahl Nilsson  (mailto:tho...@gitorious.com)>
> > Things to check: could it be an issue with permissions on your gitorious 
> > files? What's the current permissions on the data/hooks/pre-receive file 
> > (and other files in same directory?) Verify that they are owned by the 
> > gitorous user (usually the user with username 'git'). Also, please check 
> > that they are still executable. 
> > 
> > Here's an example of how the permissions look in a correctly configured 
> > Gitorious instance:
> > https://dl.dropbox.com/u/1858732/data-hooks-dir.png
> > 
> > Generally, the whole gitorous directory structure should be owned by the 
> > same user that owns all the processes etc, the same user defined as 
> > gitorious_user in config/gitorious.yml.
> > 
> > cheers,
> > Thomas
> > 
> > 
> > 
> > 
> > On 09/21/2012 08:54 PM, Luis Tiago C Eterovick wrote:
> > > Hey i had to configure Gitorious on a third machine. I got the same 
> > > problem with the URLs missing, but i fixed it deleting all.js and copying 
> > > it again. The clear script didnt work. 
> > > 
> > > Now i have this problem when cloning/pushing projects (works only using 
> > > git url, but not http, which is accessing 
> > > git.gitorious.metasysdevel.com.br 
> > > (http://git.gitorious.metasysdevel.com.br) instead of just 
> > > gitorious.metasysdevel.com.br (http://gitorious.metasysdevel.com.br), nor 
> > > ssh, which gives me fatal error): 
> > > 
> > > $ git clone 
> > > git://gitorious.metasysdevel.com.br/autolog-2-0/autolog-2-0.git 
> > > (http://gitorious.metasysdevel.com.br/autolog-2-0/autolog-2-0.git) 
> > > Cloning into 'autolog-2-0'...
> > > remote: Counting objects: 68, done.
> > > remote: Compressing objects: 100% (46/46), done.
> > > remote: Total 68 (delta 15), reused 0 (delta 0)
> > > Receiving objects: 100% (68/68), 12.70 KiB, done.
> > > Resolving deltas: 100% (15/15), done.
> > > 
> > > 
> > > $ git clone 
> > > https://git.gitorious.metasysdevel.com.br/autolog-2-0/autolog-2-0.git 
> > > Cloning into 'autolog-2-0'...
> > > error: Couldn't resolve host 'git.gitorious.metasysdevel.com.br 
> > > (http://git.gitorious.metasysdevel.com.br)' while accessing 
> > > https://git.gitorious.metasysdevel.com.br/autolog-2-0/autolog-2-0.git/info/refs
> > > fatal: HTTP request failed
> > > 
> > > $ git clone 
> > > g...@gitorious.metasysdevel.com.br:autolog-2-0/autolog-2-0.git 
> > > (mailto:g...@gitorious.metasysdevel.com.br:autolog-2-0/autolog-2-0.git) 
> > > Cloning into 'autolog-2-0'...
> > > 
> > > == Gitorious: == 
> > > Fatal error, please contact support
> > > 
> > > 
> > > fatal: The remote end hung up unexpectedly 
> > > 
> > > Logs gave me this for this last case: 
> > > 
> > > ==> gitorious_auth.log <== 
> > > I, [2012-09-21 16:15:22#2590] INFO -- : Connection from "192.168.0.3 
> > > 34894 22" (git): git-upload-pack 'autolog-2-0/autolog-2-0.git'
> > > I, [2012-09-21 16:15:22#2590] INFO -- : Accepted "git" for 
> > > "git-upload-pack 
> > > '/work/repo/git/repositories/autolog-2-0/autolog-2-0.git'"
> > > F, [2012-09-21 16:15:22#2590] FATAL -- : The pre-receive hook is not 
> > > executable
> > > 
> > > 
> > > Can i get some help please? 
> > > 
> > > 2012/8/31 Luis Tiago C Eterovick  > > (mailto:lu...@syst.com.br)>
> > > > Well... the clones and pushes are working now!! 
> > > > 
> > > > Just the URLs aren't appearing on the project pages. This is a source 
> > > > code from one of the pages: http://pastie.org/4640444 
> > > > I'm not really into this css thing, but there are many references to 
> > > > the URLs on the code... 
> > > > 
> > > > 
> > > > 2012/8/31 Thomas Kjeldahl Nilsson  > > > (mailto:tho...@gitorious.com)>
> > > > > Hello again Luis,
> > > > > 
> > > > > every gitorious instance has a single url, configured in 
> > > > > gitorious_host, which it expects clients to use for login etc (as a 
> > > > > security measure). 
> > > > > 
> > > > > In other words, for the single installation you can use a single 
> > > > > DNSed domain to reach that installation. So set gitorious_host to be 
> > > > > the actual url your users will see/use ( gitorious.metasys.com.br 
> > > > > (http://gitorious.metasys.com.br/) ?)
> > > > > 
> > > > > Finally, you can generally leave gitorious_client_host as 
> > > > > "localhost", as it's only used internally by the Gitorious 
> > > > > installation.
> > > > > 
> > > > > -t
> > > > > 
> > > > > (BTW this won'

Re: [gitorious] Migrating gitorious to another machine

[luist]

http://pastie.org/4610103

There you go!

Em quarta-feira, 29 de agosto de 2012 03h43min33s UTC-3, Thomas Kjeldahl 
Nilsson escreveu:
>
>  Hi Luist,
>
> could you run the following two oneliners (from your Gitorious root 
> directory ie. where you find Rakefile, /config etc) and tell me what the 
> output is?
>
> RAILS_ENV=production bundle exec script/runner "puts Site.first.title"
>
> RAILS_ENV=production bundle exec script/runner "puts 
> Site.first.wiki_git_path"
>
> cheers,
> Thomas
>
>
> On 08/29/2012 12:20 AM, luist wrote:
>  
> Ok I'm almost there i guess... 
>
>  This is my current diagnostics:
> http://pastie.org/4606368
>  
>  When i load the site, it shows a part of the gitorious layout and a 500 
> internal error.
>
>  This is the end of my production.log:
> http://pastie.org/4606320
>
>  Any help?
>
> Em segunda-feira, 27 de agosto de 2012 17h18min29s UTC-3, Thomas Kjeldahl 
> Nilsson escreveu: 
>>
>>  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 
>>>
>>>  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)
 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
> 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 gito...@googlegroups.com 
>> > To unsubscribe from this group, send email to 
>> > gitorious+...@googlegroups.com 
>>
>>>

Re: [gitorious] Migrating gitorious to another machine

[Thomas Kjeldahl Nilsson]

Hm well off the top of my head, did you make sure to migrate your db 
after bringing in data from your old Gitorious instance? Ie:


RAILS_ENV=production bundle exec rake db:migrate

-t


On 08/29/2012 03:17 PM, luist wrote:

http://pastie.org/4610103

There you go!

Em quarta-feira, 29 de agosto de 2012 03h43min33s UTC-3, Thomas 
Kjeldahl Nilsson escreveu:


Hi Luist,

could you run the following two oneliners (from your Gitorious
root directory ie. where you find Rakefile, /config etc) and tell
me what the output is?

RAILS_ENV=production bundle exec script/runner "puts Site.first.title"

RAILS_ENV=production bundle exec script/runner "puts
Site.first.wiki_git_path"

cheers,
Thomas


On 08/29/2012 12:20 AM, luist wrote:

Ok I'm almost there i guess...

This is my current diagnostics:
http://pastie.org/4606368

When i load the site, it shows a part of the gitorious layout and
a 500 internal error.

This is the end of my production.log:
http://pastie.org/4606320

Any help?

Em segunda-feira, 27 de agosto de 2012 17h18min29s UTC-3, Thomas
Kjeldahl Nilsson escreveu:

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 

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
)
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

What am i missing?

Em segunda-feira, 27 de agosto de 2012
07h49min47s UTC-3, Thomas Kjel

Re: [gitorious] Migrating gitorious to another machine

[luist]

Ok I'm almost there i guess...

This is my current diagnostics:
http://pastie.org/4606368

When i load the site, it shows a part of the gitorious layout and a 500 
internal error.

This is the end of my production.log:
http://pastie.org/4606320

Any help?

Em segunda-feira, 27 de agosto de 2012 17h18min29s UTC-3, Thomas Kjeldahl 
Nilsson escreveu:
>
>  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 
>>
>>  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)
>>> 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
 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 gito...@googlegroups.com 
> > To unsubscribe from this group, send email to 
> > gitorious+...@googlegroups.com 
>
>
> -- 
> best regards, 
> Thomas Kjeldahl Nilsson 
> http://gitorious.com 
>
>   

 -- 
 best regards,
 Thomas Kjeldahl Nilssonhttp://gitorious.com

   
>>>
>>> -- 
>>> best regards,
>>> Thomas Kjeldahl Nilssonhttp://gitorious.com
>>>
>>>   
>>
>> -- 
>> best regards,
>> Thomas Kjeldahl Nilssonhttp://gitorious.com
>>
>>   
>
> -- 
> best regards,
> Thomas Kjeldahl Nilssonhttp://gitorious.com
>
>  

-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com

Re: [gitorious] Migrating gitorious to another machine

[Thomas Kjeldahl Nilsson]

Hi Luist,

could you run the following two oneliners (from your Gitorious root 
directory ie. where you find Rakefile, /config etc) and tell me what the 
output is?


RAILS_ENV=production bundle exec script/runner "puts Site.first.title"

RAILS_ENV=production bundle exec script/runner "puts 
Site.first.wiki_git_path"


cheers,
Thomas


On 08/29/2012 12:20 AM, luist wrote:

Ok I'm almost there i guess...

This is my current diagnostics:
http://pastie.org/4606368

When i load the site, it shows a part of the gitorious layout and a 
500 internal error.


This is the end of my production.log:
http://pastie.org/4606320

Any help?

Em segunda-feira, 27 de agosto de 2012 17h18min29s UTC-3, Thomas 
Kjeldahl Nilsson escreveu:


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 

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
)
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 
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.

Re: [gitorious] Migrating gitorious to another machine

[luist]

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 
>
>  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)
>> 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
>>> 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 gito...@googlegroups.com 
 > To unsubscribe from this group, send email to 
 > gitorious+...@googlegroups.com 


 -- 
 best regards, 
 Thomas Kjeldahl Nilsson 
 http://gitorious.com 

   
>>>
>>> -- 
>>> best regards,
>>> Thomas Kjeldahl Nilssonhttp://gitorious.com
>>>
>>>   
>>
>> -- 
>> best regards,
>> Thomas Kjeldahl Nilssonhttp://gitorious.com
>>
>>   
>
> -- 
> best regards,
> Thomas Kjeldahl Nilssonhttp://gitorious.com
>
>  

-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com

Re: [gitorious] Migrating gitorious to another machine

[Thomas Kjeldahl Nilsson]

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 

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
)
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 
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
gito...@googlegroups.com
> To unsubscribe from this group, send email to
> gitorious+...@googlegroups.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




--
best regards,
Thomas Kjeldahl Nilsson
http://gitorious.com

--
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr..

Re: [gitorious] Migrating gitorious to another machine

[Thomas Kjeldahl Nilsson]

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

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
)
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

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
gito...@googlegroups.com
> To unsubscribe from this group, send email to
> gitorious+...@googlegroups.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 gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com

Re: [gitorious] Migrating gitorious to another machine

[luist]

Well.. looks like it doesn't have diagnostics: 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)
> 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
>> 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 gito...@googlegroups.com 
>>> > To unsubscribe from this group, send email to 
>>> > gitorious+...@googlegroups.com 
>>>
>>>
>>> -- 
>>> best regards, 
>>> Thomas Kjeldahl Nilsson 
>>> http://gitorious.com 
>>>
>>>   
>>
>> -- 
>> best regards,
>> Thomas Kjeldahl Nilssonhttp://gitorious.com
>>
>>   
>
> -- 
> best regards,
> Thomas Kjeldahl Nilssonhttp://gitorious.com
>
>  

-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com

Re: [gitorious] Migrating gitorious to another machine

[Thomas Kjeldahl Nilsson]

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)
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

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 gito...@googlegroups.com
> To unsubscribe from this group, send email to
> gitorious+...@googlegroups.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 gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com

Re: [gitorious] Migrating gitorious to another machine

[luist]

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)
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
> 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 gito...@googlegroups.com 
>> > To unsubscribe from this group, send email to 
>> > gitorious+...@googlegroups.com 
>>
>>
>> -- 
>> best regards, 
>> Thomas Kjeldahl Nilsson 
>> http://gitorious.com 
>>
>>   
>
> -- 
> best regards,
> Thomas Kjeldahl Nilssonhttp://gitorious.com
>
>  

-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com

Re: [gitorious] Migrating gitorious to another machine

[luist]

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
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 gito...@googlegroups.com 
> > To unsubscribe from this group, send email to 
> > gitorious+...@googlegroups.com  
>
>
> -- 
> best regards, 
> Thomas Kjeldahl Nilsson 
> http://gitorious.com 
>
>

-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com

Re: [gitorious] Migrating gitorious to another machine

[Thomas Kjeldahl Nilsson]

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

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 gito...@googlegroups.com

> To unsubscribe from this group, send email to
> gitorious+...@googlegroups.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 gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com

Re: [gitorious] Migrating gitorious to another machine

[Thomas Kjeldahl Nilsson]

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 gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com



--
best regards,
Thomas Kjeldahl Nilsson
http://gitorious.com

--
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com