Hi, sorrying for bringing back an old topic.
But I'm having the same problem.
The message:
"This repository is being created,
it will be ready pretty soon…"
Keeps showing forever.
If I set "ready" attribute in the repository table. I receive this
error when I try to access the repository in gitorious:
------------------------------------------------------------------------------
Grit::NoSuchPathError in Repositories#show
Showing app/views/repositories/_statistics.html.erb where line #54
raised:
/srv/git_repositories/c0f/d53/dab8491bfda06924923fc6eba3ce615956.git
Extracted source (around line #54):
51: <%= render :partial => "repositories/clone_urls", :locals =>
{:repository => repository} -%>
52: </td>
53: </tr>
54: <% if repository.has_commits? && !repository.git.heads.blank? -
%>
55: <tr>
56: <td class="branches" colspan="3">
57: <ul class="branch_list">
Trace of template inclusion: app/views/repositories/show.html.erb
RAILS_ROOT: /srv/gitorious
Application Trace | Framework Trace | Full Trace
/srv/gitorious/vendor/grit/lib/grit/repo.rb:36:in `initialize'
/srv/gitorious/app/models/repository.rb:212:in `new'
/srv/gitorious/app/models/repository.rb:212:in `git'
/srv/gitorious/app/models/repository.rb:217:in `has_commits?'
/srv/gitorious/app/views/repositories/_statistics.html.erb:54:in
`_run_erb_app47views47repositories47_statistics46html46erb_locals_object_repository_statistics'
/srv/gitorious/app/views/repositories/show.html.erb:29:in
`_run_erb_app47views47repositories47show46html46erb'
/srv/gitorious/app/helpers/application_helper.rb:91:in
`render_if_ready'
/srv/gitorious/app/views/repositories/show.html.erb:27:in
`_run_erb_app47views47repositories47show46html46erb'
/srv/gitorious/app/controllers/repositories_controller.rb:50:in `show'
-----------------------------------------------------------------------------------------------
I am manuall starting "stompserver" and "git daemon".
After creating a new repository the stompserver shows the following
line:
"Sending a message to /queue/GitoriousRepositoryCreation:"
And nothing more...
I've tried to use "RAILS_ENV=production script/poller start"
I'm running in production environment.
I setup Gitorious with the help of this scripts:
http://github.com/marcelomurad/rails-env-install/tree/master
Although I need some changes, I think everything in thoses scripts are
in place here.
Am I missing something? Some configuration?
Thanks in advance.
Felipe Hummel
On 29 maio, 21:27, prlawrence <[email protected]> wrote:
> Yes, that was *extremely* helpful. Thanks!
>
> Phil Lawrence
>
> On May 29, 2:47 pm, Marius Mårnes Mathiesen
>
> <[email protected]> wrote:
> > On 29. mai. 2009, at 19.06, prlawrence wrote:
>
> > > I am very confused. We saw that when I created the repository
> > > something appeared in the development.log file. So why are these in
> > > the production database? Why do I even have to have a test, dev, and
> > > prod database? I don't want to develop gitorious (at least for now).
> > > I only want to use it, in one production database.
>
> > Yes, this can be really confusing, I'll try to explain what's going on.
>
> > Rails lets you operate with several environments in the same
> > application. The most obvious example is the test environment:
> > whenever you run your unit/functional tests, Rails will delete all the
> > data in your (test) database and recreate a predictable data set for
> > you. Similarly, when you're running an application in development
> > mode, you'll want some things to behave differently (for instance, all
> > Ruby classes are reloaded on every request to the web server), and use
> > a separate database.
>
> > Thus the distinction between different environments in Rails.
>
> > Whenever Rails - or a script using Rails - is started, it will try to
> > figure out which environment you want to use.
> > - If you run the tests, using Rake, Rails will assume you want the
> > test environment
> > - Otherwise, unless you specify otherwise, Rails will load the
> > development environment - which is the default.
> > - By "specifying otherwise" I mean either setting the environment
> > variable RAILS_ENV to either test, development or production og
> > setting the environment in Ruby code
>
> > So: if you're running a server, you'll probably want to use the
> > production environment when doing so. If you run you app under
> > Passenger, this will probably be the default. But if you start a
> > script from the command line (eg. script/poller), this will load the
> > default environment (development) unless you specify something else.
> > What we do on gitorious.org is something like:
>
> > env RAILS_ENV=production script/poller start
>
> > This will load Gitorious using the production Rails environment.
>
> > Hope this helps,
> > - Marius
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Gitorious" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/gitorious?hl=en
-~----------~----~----~----~------~----~------~--~---
