Re: [gitorious] Ultrasphinx no longer in next
Hi Marius, So, these will be rake tasks that need to go in crontab in the future instead of the unltrasphinx ones? Is this on the trunk yet? When is it expected to be on the trunk? Bas On 29 Oct, 2012, at 8:36 PM, Marius Mårnes Mathiesen zmalltal...@zmalltalker.com wrote: Hi all, We just removed the Ultrasphinx plugin from Gitorious in the next branch. This plugin provides an interface to the Sphinx search engine used in Gitorious. Since we still use the same search engine backend, there are no user-visible changes: all existing searches should still work like before Ultrasphinx was removed. However, if you maintain your own Gitorious server, you need to know that the ultrasphinx:* rake tasks have been replaced by similar tasks in the thinking_sphinx namespace. You probably have crontab entries and/or init scripts that reference these tasks, and these will need to be changed to keep working. The tasks you need to know about are: - `rake thinking_sphinx:configure` will generate a Sphinx configuration file that can be used by Sphinx. The resulting file will be generated as =config/$RAILS_ENV.sphinx.conf= (ie. =config/production.sphinx.conf= for production server) - `rake thinking_sphinx:index` will create/update your Sphinx index, based on the configuration file generated above - `rake thinking_sphinx:start` will start your Sphinx daemon - `rake thinking_sphinx:stop` will stop your Sphinx daemon The complete list of rake tasks along with a description follows: rake thinking_sphinx:configure # Generate the Sphinx configuration file using Thinking Sphinx's settings rake thinking_sphinx:index # Index data for Sphinx using Thinking Sphinx's settings rake thinking_sphinx:rebuild# Stop Sphinx (if it's running), rebuild the indexes, and start Sphinx rake thinking_sphinx:reindex# Reindex Sphinx without regenerating the configuration file rake thinking_sphinx:restart# Restart Sphinx rake thinking_sphinx:running_start # Stop if running, then start a Sphinx searchd daemon using Thinking Sphinx's settings rake thinking_sphinx:start # Start a Sphinx searchd daemon using Thinking Sphinx's settings rake thinking_sphinx:stop # Stop Sphinx using Thinking Sphinx's settings rake thinking_sphinx:version# Output the current Thinking Sphinx version Getting rid of Ultrasphinx was required to make Gitorious run under Rails 3, and the plugin replacing it also runs under most (if not all) Ruby versions. 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 -- 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] Diagnostics questions
Hi Marius, I'm still a bit confused. We've hosted the gitorious server on git.companyname.com for quite a while and I don't it has caused any problems and the requests have still been going over ssh (not https). Could you clarify this more and/or tell me where this happens in the gitorious code base and why this is done? Thanks! Bas On 24 Oct, 2012, at 6:08 PM, Marius Mårnes Mathiesen zmalltal...@zmalltalker.com wrote: On Tue, Oct 23, 2012 at 03:20:05PM +0800, Bas Vodde wrote: Hiya, We've been upgrading our own gitorious installation to the latest and have used the diagnostics to try to find things that could be improved. I've got a question about this: The diagnostics failed on: hostname not bound to a 'git.*' subdomain? Our gitorious installation is at git.companyname.com. Why isn't it ok to have the hostname be git.* ? (we've not had any problem with this) This will cause Gitorious to interpret all requests to be git-over-http requests (these are identified by the fqdn used in the request). IIRC, this means that all requests are processed by the metal which serves git over HTTP, but as the requests don't look like Git requests they will (probably) be passed on to the regular Rails app. 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 -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
[gitorious] Diagnostics questions
Hiya, We've been upgrading our own gitorious installation to the latest and have used the diagnostics to try to find things that could be improved. I've got a question about this: The diagnostics failed on: hostname not bound to a 'git.*' subdomain? Our gitorious installation is at git.companyname.com. Why isn't it ok to have the hostname be git.* ? (we've not had any problem with this) Thanks! Bas -- 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] What the core committers are working on right now
Simplified installation will definitively help. I assume this will also include simplified upgrade? Bas On 5 Sep, 2012, at 3:28 PM, Thomas Kjeldahl Nilsson tho...@gitorious.com wrote: Some updates on our current work. I'm most excited about the new UI and simplified installation. :) http://blog.gitorious.org/2012/09/05/what-were-currently-working-on/ Feedback welcome! -- 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 -- 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] Fedora packaging (was: Gitorious Versioning)
Hi, #3: Fedora has dropped ruby-net-ldap in favor of net-ldap. I don't yet know how much work it would be to patch Gitorious to use the net-ldap Gem. Its the same. In fact, I think I did a merge request a couple of months ago with this change. It got delayed and I need to re-do the change based on the latest but didn't upgrade to the latest. But net-ldap is just a new version of net-ruby-ldap and the change (for me) took no effort. Bas If there's anything else I should know about in terms of dependencies (present or future plans) I'm very interested. [1] https://fedoraproject.org/wiki/User:Ktdreyer/Gitorious [2] https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries [3] https://issues.gitorious.org/issues/3 -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.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] Re: SystemTimeout and Ruby 1.9.3
Hi Carlos, We had removed it in our installation and worked fine. Bas On 3 Aug, 2012, at 3:19 AM, Carlos cmu...@gmail.com wrote: Note for those who find this thread by googling: commenting out SystemTimer seems to be ok, assuming you're running Ruby 1.9 On Thursday, August 2, 2012 11:55:07 AM UTC-7, Carlos wrote: FWIW, I just commented out the SystemTimer line of group :resque in the Gemfile and bundler was happy. We'll see what happens... On Thursday, August 2, 2012 11:34:22 AM UTC-7, Carlos wrote: Hi. I understand that gitorious.org is running Ruby 1.8 for encodings. But suppose I am crazy enough to run gitorious with Ruby 1.9.3. From what I can see, the SystemTimer hack is no longer needed in Ruby 1.9.x. Even so, when I try to run bundle install it dies because it cannot build SystemTimer. What is the recommended action or alternative if I want to try gitorious with Ruby 1.9.3? Thanks! -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
[gitorious] Login yet... not logged in
Hiya, I just configured a private gitorious. The installation seems to work, but I got an interesting problem. I configured the authentication to go via LDAP. This required an upgrade of the ruby-net-ldap to net-ldap but after that, it worked. That is, I can login and it says login successfully... but then... I'm not logged in! The authentication works, but the actual logging in never happens. Interestingly enough, I have no log writings whatsoever. Not in the production.log and neither in the apache log (running through passenger). Any idea what this could be? Thanks, Bas -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
[gitorious] Specific commit merge request
Hi, Uhm, I've got a simple (stupid) question (I think). Is it possible to make a merge request from just a single commit. I cloned the gitorious code and pushed several commits to the clone, however, now I want to do a merge request with only one of these commits to keep the merge requests clean. How do I do that? Thanks, Bas -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
