from:"Christian Johansen"

 Am I correct that gitorious currently can only be installed at the
 root of a site?

Yes. Installing with a context path will mostly work, but the app has
not been tested extensively in a setup like this.

 Poking through the code, it appears that at least the e-mail sending
 functionality is not aware of a path (would need a :path as option in
 url_for(...))

Correct. There may also be other places, but to be honest I'm not really
sure how much needs to change.

 Are there any plans to support this functionality?

Not really. However, I would be happy to assist you with any questions
and then eventually merge in the required changes if you or someone else
wants to take a stab at it.

Christian

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

--- 
You received this message because you are subscribed to the Google Groups 
Gitorious group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitorious+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gitorious] config file re-read?

 I'm attempting to move the location of the gitorious.yml file so I can
 have more than one gitorious installation on the same machine.

I've considered this as well. I think a good approach would be for
Gitorious to recognize GITORIOUS_HOME, and use that to find
configuration etc.

 I found code in config/application.rb that loads gitorious.yml, and
 changed it so it can look for a different path. That works fine.

Which branch is this on? Changes like this should be made to the 'next'
branch, and on that branch I don't think gitorious.yml is referred in
config/application.rb?

 But apparently the gitorious.yml file is read in another place a
 second time (see stack trace below). I'm unclear why this file should
 have to be read more than once. There's also something about a method
 missing, and I'm not sure why that is either (now I'm not a ruby guy,
 this may be very obvious to somebody). For my purposes, I can patch
 config/initializers/gitorious_config.rb as well, and I have done so,
 but it seems there's duplicate / overlapping code here somewhere, and
 I thought I point that out.

On 'next', config/initializers/gitorious_config.rb uses
lib/gitorious/configuration_loader.rb to load gitorious.yml into
Gitorious::Configuration. I've worked a bit on making this the only
piece of code that reads the file. From the initializer, there is
already this call:

Gitorious::ConfigurationLoader.new(Rails.root)

Which could be replaced with something like this:

Gitorious::ConfigurationLoader.new(ENV[GIORIOUS_HOME] || Rails.root)

And then you could run the app with
`env GITORIOUS_HOME=/my/gitorious bundle exec rails server`

However, you would need to do similar work with the database
configuration (which is loaded by Rails, not entirely sure how to fix
that), and the other configuration as well.

Christian

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

--- 
You received this message because you are subscribed to the Google Groups 
Gitorious group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitorious+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gitorious] 'next' install issues

 in data/hooks:
   lrwxr-xr-x 1 jernst staff 6 Mar 15 10:08 .hooks - .hooks
 to itself?

Hah. It's been there since 2009. Marius? Thomas?

 ActionView::Template::Error (No such file or directory - Asset file not found 
 at 
 '/usr/cldstr/cldstr.com/gitorious/ws/mainline/public/javascripts/lib/spin.js/spin.js'):
 23: %= include_stylesheets :common %
 24: link href=//fonts.googleapis.com/css?family=Nobileamp;v1 
 type=text/css rel=stylesheet
 25: %= favicon_link_tag %
 26: %= include_javascripts -%
 27: %  if @atom_auto_discovery_url -%
 28:   %= auto_discovery_link_tag(:atom, @atom_auto_discovery_url,
 29:   :title = @atom_auto_discovery_title) 
 -%
   app/helpers/application_helper.rb:509:in `include_javascripts'
   app/views/layouts/_common_head.html.erb:26:in 
 `_app_views_layouts__common_head_html_erb__1099690639031229068_54356280'
   app/views/layouts/application.html.erb:28:in 
 `_app_views_layouts_application_html_erb__4020206816622032450_51612840'
   app/controllers/site_controller.rb:73:in `render_public_timeline'
   app/controllers/site_controller.rb:104:in `render_global_index'
   app/controllers/site_controller.rb:34:in `index'

 Is that repeated spin.js/spin.js correct?

Yes. Did you run `git submodule update --init`?

 In gitorious.yml.tmpl:

 #git_http_port: 80
 #git_http_scheme: https

 Perhaps that should be 443? I realize it's commented out.

Good call, fixed.

 In gitorious.yml.tmpl:

 Comment says about frontend_server: The default value is 'nginx',
 but it appears from the code the default value is actually apache?

No, see line 178 in lib/gitorious.rb. Where did you get the apache
default from? It is the default in the upgrade script, because apache
was the default frontend on Gitorious 2.x

Christian

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

--- 
You received this message because you are subscribed to the Google Groups 
Gitorious group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitorious+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gitorious] V3.0 status

 makes sense! So based on what you said, I've been plunging into trying
 to get 'next' to run today, and as I (hopefully) make progress, I'll
 be reporting / asking about any problems I encounter. With the caveat
 that I'm not a ruby guy, so some things may be very obvious to
 everybody other than me...

Johannes, there's no requirement to be a ruby guy to run Gitorious, so
anything you stumble on is very helpful for us to know about.

 To get this started: mysql vs mysql2, apparently that got upgraded.
 But when doing a 'bundle install', I'm getting:

 *** Exception LoadError in PhusionPassenger::Rack::ApplicationSpawner
 (Please install the mysql adapter: `gem install
 activerecord-mysql-adapter` (mysql is not part of the bundle. Add it
 to Gemfile.))

 activerecord-mysql-adapter is not listed in the Gemfile. I tried to
 add activerecord-mysql2-adapter to stay with mysql2, but that does not
 make it better. So I added activerecord-mysql-adapter, which then also
 requires mysql, which seems to mean that I have now two versions of
 the same database driver? That does not seem to be right.

 Here's the stack trace via Passenger. What might be wrong here?

Uhm, this is odd. You should not have to change the Gemfile. You should
only change the name of your database adapter in config/database.yml
from mysql to mysql2. The adapter should ship with Rails. Did you
make any other changes?

Christian

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

--- 
You received this message because you are subscribed to the Google Groups 
Gitorious group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitorious+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gitorious] Log graph issues

2013-03-12 Thread Christian Johansen

Hi Scott,

I tracked this down to refnames with dots being sanitized and have the
dots stripped. I changed the GitShell implementation to use Shellwords
to properly escape the refnames, and now it works again.

If you didn't have dots in the refnames where you didn't see a graph,
let me know.

On 2.x-stable: 
https://gitorious.org/gitorious/mainline/commit/941646757d0f9ac7732ee98cf966156f19ced6ef
On next: 
https://gitorious.org/gitorious/mainline/commit/28af76c7e26b7af525199626111ffb22996d631e

Christian

Scott Allen writes:

 On an internal private instance, user's have noticed that certain branches
 are not being displayed with log graph feature, while other are. I found
 I was able to reproduce this on gitorious.org. Are others seeing this issue?

 https://gitorious.org/gitorious/mainline/graph/2.x-stable

 -scott


 --

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

--- 
You received this message because you are subscribed to the Google Groups 
Gitorious group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitorious+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gitorious] Log graph issues

2013-03-12 Thread Christian Johansen

 Wouldn't it have been simpler (and more generic) to keep the
 original prototype for graph_log() and then just change:

   command  sanitize(options.join( ))

 to:

   command  options.shelljoin

Interesting. `shelljoin` is new to me. The reason I had to change it
around is that we don't really want to shell escape our own (safe)
arguments, only the ref name. Doing that would break our use of
`pretty=format:...`.

Christian

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

--- 
You received this message because you are subscribed to the Google Groups 
Gitorious group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitorious+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gitorious] https push support progress / status?

2013-02-26 Thread Christian Johansen

Hi Andrew,

 New user of gitorious here. Awesome project, thank you so much.

 I apologize if this has already been covered somewhere else. I did a search
 of the group and found a few postings about it from 2011 but nothing
 current. I know git supports http push via the git-http-backend/fetch/push

 Does gitorious support pushing via http(s) protocol with it's auth
 model

Unfortunately, no. But it is high on our list of features to add.

Christian

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

--- 
You received this message because you are subscribed to the Google Groups 
Gitorious group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitorious+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gitorious] gitorious-poller won't start - ActiveMessaging (NameError)

2013-02-26 Thread Christian Johansen

Hi Kent,

No, you don't need the poller. The diagnostics on the CE installer is in
need of an upgrade. Sorry about that, we will fix it soon.

Christian

Kent Holloway writes:

 Fresh install of CE Gitorious v2.4.9 (yesterday) on a fresh Redhat 6.3 OS
 install throws the errors below when starting the poller.

 Do I even need the poller?
 The only place it even mentions it being a problem is via the
 '/admin/diagnostics' link on my running instance.

 The main Gitorious app seems to run/work properly and I have no other
 visible errors anywhere.
 I'm using the

 --Install guide that I followed--
 http://getgitorious.com/installer

 --Start command--
 cd /var/www/gitorious/app  RAILS_ENV=production bundle exec script/poller
 start

 --Errors--
 poller: process with pid 15492 started.
 NOTE: Gem.source_index is deprecated, use Specification. It will be removed
 on or after 2011-11-01.
 Gem.source_index called from
 /var/www/gitorious/app/vendor/bundle/ruby/1.8/gems/rails-2.3.17/lib/rails/gem_dependency.rb:21.
 /var/www/gitorious/app/vendor/bundle/ruby/1.8/gems/activesupport-2.3.17/lib/active_support/dependencies.rb:469:in
 `load_missing_constant': uninitialize
 d constant ActiveMessaging (NameError)
 from
 /var/www/gitorious/app/vendor/bundle/ruby/1.8/gems/activesupport-2.3.17/lib/active_support/dependencies.rb:106:in
 `const_missing'
 from
 /var/www/gitorious/app/vendor/bundle/ruby/1.8/gems/activesupport-2.3.17/lib/active_support/dependencies.rb:118:in
 `const_missing'
 from /var/www/gitorious/app/lib/gitorious/messaging/stomp_poller.rb:12
 from
 /var/www/gitorious/app/vendor/bundle/ruby/1.8/gems/daemons-1.1.0/lib/daemons/application.rb:203:in
 `load'
 from
 /var/www/gitorious/app/vendor/bundle/ruby/1.8/gems/daemons-1.1.0/lib/daemons/application.rb:203:in
 `start_load'
 from
 /var/www/gitorious/app/vendor/bundle/ruby/1.8/gems/daemons-1.1.0/lib/daemons/application.rb:292:in
 `start'
 from
 /var/www/gitorious/app/vendor/bundle/ruby/1.8/gems/daemons-1.1.0/lib/daemons/controller.rb:70:in
 `run'
 from
 /var/www/gitorious/app/vendor/bundle/ruby/1.8/gems/daemons-1.1.0/lib/daemons.rb:143:in
 `run'
 from
 /var/www/gitorious/app/vendor/bundle/ruby/1.8/gems/daemons-1.1.0/lib/daemons/cmdline.rb:112:in
 `call'
 from
 /var/www/gitorious/app/vendor/bundle/ruby/1.8/gems/daemons-1.1.0/lib/daemons/cmdline.rb:112:in
 `catch_exceptions'
 from
 /var/www/gitorious/app/vendor/bundle/ruby/1.8/gems/daemons-1.1.0/lib/daemons.rb:142:in
 `run'
 from script/poller:30


 --Gem list--
 Gems included by the bundle:
   * SystemTimer (1.2.3)
   * actionmailer (2.3.17)
   * actionpack (2.3.17)
   * activemessaging (0.7.1)
   * activerecord (2.3.17)
   * activeresource (2.3.17)
   * activesupport (2.3.17)
   * acts-as-taggable-on (2.0.6)
   * after_commit (1.0.10)
   * builder (3.0.0)
   * bundler (1.2.4)
   * capillary (1.0.2)
   * chronic (0.3.0)
   * cocaine (0.3.2)
   * daemons (1.1.0)
   * diff-lcs (1.1.2)
   * echoe (4.3.1)
   * eventmachine (1.0.0)
   * exception_notification (1.0.20090728)
   * foreman (0.60.2)
   * gemcutter (0.7.1)
   * geoip (0.8.9)
   * hodel_3000_compliant_logger (0.1.0)
   * hoe (2.8.0)
   * json (1.7.7)
   * json_pure (1.7.5)
   * just_paginate (0.0.6)
   * kgio (2.7.4)
   * mime-types (1.16)
   * mysql (2.8.1)
   * net-ldap (0.3.1)
   * nokogiri (1.5.0)
   * oauth (0.4.4)
   * paperclip (2.7.4)
   * proxymachine (1.2.4)
   * rack (1.1.6)
   * rails (2.3.17)
   * raindrops (0.10.0)
   * rake (0.8.7)
   * rdiscount (1.3.1.1)
   * rdoc (3.12)
   * redis (2.2.2)
   * redis-namespace (0.7.0)
   * resque (1.9.8)
   * revo-ssl_requirement (1.1.0)
   * riddle (1.5.3)
   * ruby-hmac (0.4.0)
   * ruby-openid (2.2.2)
   * ruby-yadis (0.3.4)
   * rubyforge (2.0.4)
   * sinatra (1.2.8)
   * state_machine (0.9.4)
   * stomp (1.1)
   * stompserver (0.9.9)
   * thin (1.5.0)
   * thinking-sphinx (1.4.13)
   * thor (0.16.0)
   * tilt (1.3.3)
   * unicorn (4.3.1)
   * validates_url_format_of (0.1.1)
   * vegas (0.1.11)
   * will_paginate (2.3.15)

 --OS and Ruby info--
 Kernel:
   Linux myfakehostname 2.6.32-279.19.1.el6.x86_64 #1 SMP Sat Nov 24
 14:35:28 EST 2012 x86_64 x86_64 x86_64 GNU/Linux

 OS:
   Red Hat Enterprise Linux Server release 6.3 (Santiago)

 Ruby Version:
   ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]


 --Running processes related to Gitorious install--
 redis 4535 1  0 Feb20 ?00:00:48 /usr/sbin/redis-server
 /etc/redis.conf
 233   4756 1  0 Feb20 ?00:00:04 memcached -d -p 11211 -u
 memcached -m 64 -c 1024 -P /var/run/memcached/memcached.pid
 root  4825 1  0 Feb20 ?00:00:00 /bin/sh
 /usr/bin/mysqld_safe --datadir=/var/lib/mysql
 --socket=/var/lib/mysql/mysql.sock --pid-file=/va
 mysql 4914  4825  0 Feb20 ?00:00:45 /usr/libexec/mysqld
 --basedir=/usr --datadir=/var/lib/mysql --user=mysql
 --log-error=/var/log/mysqld.lo
 git   7947 1  0 11:35 ?00:00:06 unicorn master -c
 config/unicorn.rb -D
 git   7955 1  0 11:35 ?

Re: [gitorious] testing gitorious in Fedora buildsys

2013-02-22 Thread Christian Johansen

 1) Make Gitorious support SQLite ;-)

That would be nice, but I suspect it is non-trivial. I know Marius has
run Gitorious mostly successfully with PostgreSQL locally, so maybe it
is possible? Marius would probably know more than me here.

 2) Mock all MySQL interactions (probably not feasible at all),

Not really.

 3) Figure out a way to at least run a subset of tests that do not
 require a live instance of mysqld,

On next, you can! `bin/micro-tests`

I recently did some work to extract as many tests as possible to
test/micros - these are tests that do not depend on the Rails framework.
Going forward I want this to encompass the bulk of the tests.

 4) Skip the test suite altogether (not ideal, but it is the easy way
 out)

I don't think that is _that_ bad, given that we do put some work into
securing our releases. Should problems arise we still have the
opportunity to work with people to have them run tests for diagnostics
at a later point. But having them run automatically would of course be
nice.

 Since there's so many variations of package combinations on Fedora in
 particular, I was really hoping that the test suite would provide some
 assurances that everything was still working properly. If we can't run
 the test suite automatically during the RPM build process, that's a
 bummer.

Let's wait for Marius to chip in (he's gone until Tuesday) and hope for
the SQLite possibility.

Christian

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

--- 
You received this message because you are subscribed to the Google Groups 
Gitorious group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitorious+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gitorious] which ruby's interpreter should I use for gitorious 2.x ?

2013-02-15 Thread Christian Johansen

You can use standard Ruby 1.8.7. When Gitorious 3 is released in a few
weeks, we will be recommending 1.9.3.

Christian

Chiku Linu writes:

 Hi,

 I only just noticed now that ree is end-of-life since 2012-02.
 So which ruby do you suggest me to use instead of ?
 or just use standard one MRI ?

 --

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

--- 
You received this message because you are subscribed to the Google Groups 
Gitorious group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitorious+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[gitorious] 2.4.9 fixes regression in yesterday's 2.4.8 release

2013-02-13 Thread Christian Johansen

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Sorry for this, but it seems I inadvertantly broke creating new projects
with yesterday's 2.4.8 release. I have deployed a fix on gitorious.org,
and just tagged 2.4.9.

We made some sweeping changes yesterday, by changing attr_protected
(which was the recent target of a Rails vulnerability) to
attr_accessible - basically changing from black-listing to white-listing
in what parameters can be posted to Gitorious and set on DB-backed
models. It seems that one case was not covered by automatic tests, and
was not discovered immediately.

Sorry for the inconvenience.

On behalf of the Gitorious team,
Christian
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.13 (GNU/Linux)

iQEcBAEBAgAGBQJRG5ucAAoJEKwDTN/JAKQJj3wH/1FXk04vLQwwiexiBwEt0LYE
/9N24XSoV1teQ0m8ulk6dPKKeb+6lYnAs5rCI8WJXP+7RKplMKVbcxNfbA3AUkZw
S2b2Zg1zRFmGbnSYvqzI6uzR0HID3gwgUcnTNn8r002gGT/CwTM2k+iiSsDUrsQ/
2DAaI1laZe9nfHDbbk20stgpsnSfmJWLRJ6dnMplqfppRUwuSAXgZaQuPg1RG6aK
jpYffZTAATudvFUcmfhgmEimYk1GFf5nmk9O5Cqa+H2DuqmAkxXHFKqhXY/7FOT3
OZHUCgFaTKz1UuqBScrc9qTPyYWTMPD4WrbL99U5iQO66pGSiSMhYNosTMOWpK0=
=tfa5
-END PGP SIGNATURE-

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

--- 
You received this message because you are subscribed to the Google Groups 
Gitorious group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitorious+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gitorious] Upgrade from v2.3.2 to v.2.4.7

2013-02-11 Thread Christian Johansen

FWIW, I also added some of the untracked files to our updated
.gitignore file.

Christian

Thomas Kjeldahl Nilsson writes:

 Andrew,

 - We're releasing an upgraded version of the installer this week,
 including the latest Gitorious version and improvements in how/what it
 installs. We'll announce it on the gitorious blog once it's up and
 available.

 - Regarding rake tasks etc, this has been more fiddly than necessary and
 we've taken steps to make gitorious less Rails-y for admins installing
 it. One of the things we've done is to create new scripts under bin/ in
 the gitorious src code, which hides rails environments, makes sure you
 are running the commands with the correct user/permissions etc.

 sorry you had to fight so much with your installation, hope jumping
 straight to 2.4.7 makes life easier.

 cheers,
 Thomas


 On 02/10/2013 04:20 PM, Andrew Kerr wrote:
 I just install gitorious on a clean CentOS 6 machine using the
 installation script located here: http://getgitorious.com/installer.
 I assume this is the supported method?

 Surprisingly, this installed a pretty old version - v2.3.2, and not
 the most recent.

 I've spent many hours trying to upgrade to v2.4.7, following the
 directions here
 https://gitorious.org/gitorious/pages/Upgrading#Upgrading+from+2.3.2+to+2.4.1++

 For starters, the merge fails because I have locally updated files.
 Surprising, since I just ran the installer and haven't touched anything:
 [root@XXX /var/www/gitorious/app]# git status
 # On branch my-version
 # Changed but not updated:
 #   (use git add file... to update what will be committed)
 #   (use git checkout -- file... to discard changes in working
 directory)
 #
 #modified:   db/schema.rb
 #modified:   db/seeds.rb
 #
 # Untracked files:
 #   (use git add file... to include in what will be committed)
 #
 #.bundle/
 #log/git-proxy.log1
 #log/gitorious_auth.log-20130210
 #log/message_processing.log-20130210
 #log/pre_receive_guard.log-20130210
 #log/production.log-20130210
 #log/sphinx.log-20130210
 #public/javascripts/capillary.js
 #public/stylesheets/all.css
 #public/stylesheets/gts-external.css
 #tmp/bundles_installed
 #tmp/database_populated
 #tmp/ownership
 #vendor/bundle/

 So I git stash the two files in the db directory.  Then I can do the
 git merge, which seems to work but still reports Automatic merge
 failed; fix conflicts and then commit the result.

 After this I can run the rest of the tasks, although only if I
 pre-pend env RAILS_ENV=production bundle exec.  From everything I've
 read this is the proper way to run the rake tasks, so I can't see why
 the upgrade docs would ignore them - or how/if they'd even work?

 So the next issue is that, while the upgrade completely fails to
 mention this, per the changelog The Ultrasphinx plugin has been
 replaced by ThinkingSphinx.  So the init script that the installer
 created,  /etc/init.d/git-ultrasphinx, obviously doesn't work.  The
 problem is that nothing anywhere tells you how to appropriately change
 this.  Also, doc/templates/centos/ still contains the old ultrasphinx
 script.  I don't know what to change here to make it work.

 I assume I'm doing the right thing by using the supported installer,
 but I could sure use some help getting on the latest 2.4.x release.
 Has anyone else done this on a CentOS 6 system? If so, I could use use
 some help!

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

 ---
 You received this message because you are subscribed to the Google
 Groups Gitorious group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to gitorious+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.




 --
 Best regards,
 Thomas Kjeldahl Nilsson,
 Partner  Programmer,
 Gitorious AS
 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

--- 
You received this message because you are subscribed to the Google Groups 
Gitorious group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitorious+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gitorious] buster-core dependency

2013-01-31 Thread Christian Johansen

Ken,

 For now I'm planning to simply package the Gitorious.org buster-core
 distribution as-is. I'm trying to wrap my mind around what will happen
 long-term.

As it happens, I am one of two principal Buster.JS developers.
buster-core is basically deprecated because it's been split up into
different packages. I've been meaning to fix this for a while - thanks
for prodding me.

I have now replaced this module with bane, which provides the
functionality needed for Capillary (the JavaScript git graph module).
It's still a submodule, but the Gitorious repo for it has been updated
etc.

The module is also available through Node's package manager, npm. I
don't know if that makes it any easier for you?

I've fixed both the next and 2.x-stable branches.

Christian

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

--- 
You received this message because you are subscribed to the Google Groups 
Gitorious group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitorious+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gitorious] buster-core dependency

2013-01-31 Thread Christian Johansen

 Yes, thank you for your work on this!

:)

 I'm wondering if Gitorious or GitHub is the canonical repo for the
 buster project? Is one a mirror of the other?

The intention is to keep both in sync (I use two urls for the 'origin'
remote). Gitorious uses the bane repository on gitorious.org for the
submodule.

 The Fedora Project is working on Node.js packaging standards, but I'm
 thinking those don't cover client-side libraries... I'm sure this will
 be an evolving process as I move along :)

I'm sure it will :) JavaScript client-side packaging is complete chaos.
I don't think it'll improve until ES6 is out and widely supported (in
other words - not for a long time).

Christian

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

--- 
You received this message because you are subscribed to the Google Groups 
Gitorious group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitorious+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gitorious] Disable Check In's via command line

2013-01-30 Thread Christian Johansen

Chris,

sounds like what you really need is a branching model where you don't
cut releases from the same branch that people are working from. We're
using http://nvie.com/posts/a-successful-git-branching-model/

Our master is the current release, which is also in production on
gitorious.org. 'next' is our main development branch. When there's a
release coming up, we will make a branch e.g. release-2.4.7. Only bug
fixes go onto that branch. When it's ready for deployment, we merge it
into master, tag/deploy, and then back to 'next'. Any commits happening
in the release process would go to 'next', and thus not interfere with
the release process.

You don't have to follow this route exactly, but I do believe your
problem is a social one, not a technical one - i.e. you need _some_
system to protect releases, and branches are the perfect tool.

Christian

Chris Holden writes:

  Marius

 Yes I meant pushing to remote sorry.  We have a group of devs who have 
 interrupted releases by checking in during the release.

 Instead of waiting they want to fix it programmatically.

 Thank you!

 Sent from my iPhone

 On Jan 30, 2013, at 4:41 AM, Marius Mårnes Mathiesen 
 marius.mathie...@gmail.com wrote:


 Chris Holden writes:
 Is it possible to disable checkin's for a repo via the command line during
 a release and then renable it after the release is finished?

 Since Git is distributed, there's no way you can control what individual
 users do to their local clones of a repository, but it should be
 possible to temporarily stop yourself from committing to your clone
 (although it seems a little strange). If you're referring to temporarily
 restricting access to a remote being pushed to, that's not something
 that's supported by Gitorious.


 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

 ---
 You received this message because you are subscribed to the Google Groups 
 Gitorious group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to gitorious+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.



 --

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

--- 
You received this message because you are subscribed to the Google Groups 
Gitorious group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitorious+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gitorious] Create Project and Repository by script

2013-01-23 Thread Christian Johansen

Hi,

It might please you that Gitorious will soon-ish have an HTTP Api for
this.

Until then, here are some clues to find your way around the console:

* Use save! (with the exclamation mark) to get an exception that tells
  you what went wrong
* You can see if a project is valid by doing p.valid?. If it's not
  valid, see what p.errors.inspect gives you

Chrisitian

chevdor writes:

 Hello,

 I am trying to find a solution to create new Projects and Respositories by
 script.

 So, from the console, I have tried:

 u = User.find(3)
 p=Project.create(:title = 'junk', :slug = 'junk', :description =
 'junk', :owner = u)


 This returns:

 = #Project id: nil, title: junk, description: junk, user_id: nil,
 created_at: nil, updated_at: nil, slug: junk, license: nil, home_url:
 nil, mailinglist_url: nil, bugtracker_url: nil, owner_id: 3, owner_type:
 User, wiki_enabled: true, site_id: nil, merge_requests_need_signoff:
 false, oauth_signoff_key: nil, oauth_signoff_secret: nil,
 oauth_signoff_site: nil, oauth_path_prefix: nil,
 merge_request_custom_states: nil, suspended_at: nil


 and p.save returns false.
 How is the 'id' generated?

 Is the method above the right one to create a new project?

 --

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

[gitorious] UI upgrade and Rails 3

2012-10-26 Thread Christian Johansen

Good people,

During my work with the new UI, we have decided to take the detour through
Rails 3. See the blog post
for further information:
http://blog.gitorious.org/2012/10/26/ui-upgrade-and-rails-3/

TL;DR: New source code browser is done, Rails 3 upgrade lands next week, UI
work continues after that.

-- 
MVH
Christian

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

[gitorious] Upgraded Rails for Gitorious

2012-10-18 Thread Christian Johansen

I've now pushed commits to mainline:next that upgrades our Rails version:

- Unvendor Rails (i.e. rm -fr vendor/rails, configure Rails in Gemfile)
- Upgrade from 2.3.5 to 2.3.14

This means we're no longer on a completely ancient version of Rails. There
has been
some non-trivial changes in Rails between the two versions, so please
report if you
find any oddities. The two main things to look out for are:

1) Strangely translated text (I made quite a few changes to how our
internationalization
was implemented, to accommodate newer versions of I18N)
2) Over-eager HTML escaping. Will likely manifest as broken UI. Our tests
does not
cover the HTML generation very exhaustingly, but I've surfed through
quite a bit, and
it looks OK to me.

Please beware that the next branch with this change is on the risky side.
We'll be using
it on our internal setup for a little while before merging to master and
deploying on
gitorious.org. If you have setups that can take a visual bug or two, please
try it out and
help us find bugs.

How does this upgrade help us?

1) Lots and lots of bug fixes from the Rails team, including security
patches
2) Tackled some deprecated APIs and flat out failing things that will help
us move
on to Rails 3
3) Solves a dependency deadlock involving Rack, that has made my integrating
the new code browser, uhm, challenging
4) Solves the problem of your rubygems is to new, please downgrade

For end users the upgrade is unlikely to bring any visual changes.

-- 
MVH
Christian

-- 
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] Changes to our branching model

2012-10-16 Thread Christian Johansen


 My one suggestion is to make this policy crystal clear to new
 developers. Whenever I write a patch for a project I want to know
 what branch do I base this on in order to get it accepted ASAP? If
 you make it very clear in the HACKING file, and in the wiki, that
 patches should be proposed against next in the form of Gitorious
 merge requests, then it will be much simpler for contributors to join.


 Ken,
 Thanks for the feedback, I'm definitely adding a note to the HACKING file.


Suggestion: Let's put this post on getgitorious.com, put a small note in
the HACKING file, and also link to the full outline in the docs.

Christian

-- 
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: Dolt repo browser 0.4.0 available

2012-10-04 Thread Christian Johansen

On Thu, Oct 4, 2012 at 9:28 AM, Wari Wahab wari.wa...@gmail.com wrote:

 Dolt does not seem to support cucumber features, as well as scripts that
 does not have an extension, and starts with #!/usr/bin/env ruby for
 example.


Well, Gherkin is under Pygment's supported language list:
http://pygments.org/languages/ Do you have a sample cucumber file with the
extension you're using so I can try it?

I have added shebang language detection, which seems to not work for you:
https://gitorious.org/gitorious/dolt/blobs/master/lib/dolt/view/syntax_highlight.rb#line90
Will try with that exact shebang and figure it out.

Thanks for the feedback. Btw, I just put out a new version that supports
submodules.

Christian

-- 
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: Dolt repo browser 0.4.0 available

2012-10-04 Thread Christian Johansen

Thanks,

Turns out I was loading the syntax highlighting language wrong. Fixed that,
and then Cucumber features works. Will push yet another update later today.

Any chance you can share the repo that caused the crash?

Christian

On Thu, Oct 4, 2012 at 11:10 AM, Wari Wahab wari.wa...@gmail.com wrote:

 I was about to test submodules later in the day. Kudos to adding that
 support before I can come around to it.

 The feature file is a simple text file:

 features/myfeature.feature
 -
 Feature: I want moolah
   In order to be rich
   As a poor old lad
   I need to rob a bank

   Scenario: Grab some weapons
 When I head to my stash area
 Then I pick my guns up
 I should be able to cause massive damage
 ---

 PS: a move up one level back button would be great, pressing back just
 don't work as well ;)

 I did get the server to crash when browsing one directory:

  Thin web server (v1.5.0 codename Knife)
  Maximum connections set to 1024
  Listening on 0.0.0.0:3000, CTRL+C to stop
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/json-1.7.5/lib/json/common.rb:223:in
 `encode': \xC3 from ASCII-8BIT to UTF-8
 (Encoding::UndefinedConversionError)
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/json-1.7.5/lib/json/common.rb:223:in
 `generate'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/json-1.7.5/lib/json/common.rb:223:in
 `generate'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/bin/../views/tree_history.erb:1:in
 `evaluate_source'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/tilt-1.3.3/lib/tilt/template.rb:209:in
 `instance_eval'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/tilt-1.3.3/lib/tilt/template.rb:209:in
 `evaluate_source'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/tilt-1.3.3/lib/tilt/template.rb:144:in
 `cached_evaluate'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/tilt-1.3.3/lib/tilt/template.rb:127:in
 `evaluate'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/tilt-1.3.3/lib/tilt/template.rb:76:in
 `render'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/template_renderer.rb:42:in
 `render'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/sinatra/actions.rb:99:in
 `block in tree_history'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/repo_actions.rb:72:in
 `call'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/repo_actions.rb:72:in
 `block in repo_action'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/eventmachine-1.0.0/lib/em/deferrable.rb:151:in
 `call'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/eventmachine-1.0.0/lib/em/deferrable.rb:151:in
 `set_deferred_status'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/eventmachine-1.0.0/lib/em/deferrable.rb:191:in
 `succeed'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/git/repository.rb:49:in
 `block (2 levels) in tree_history'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/eventmachine-1.0.0/lib/em/deferrable.rb:151:in
 `call'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/eventmachine-1.0.0/lib/em/deferrable.rb:151:in
 `set_deferred_status'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/eventmachine-1.0.0/lib/em/deferrable.rb:191:in
 `succeed'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/git/repository.rb:70:in
 `block in build_history'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/eventmachine-1.0.0/lib/em/deferrable.rb:151:in
 `call'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/eventmachine-1.0.0/lib/em/deferrable.rb:151:in
 `set_deferred_status'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/eventmachine-1.0.0/lib/em/deferrable.rb:191:in
 `succeed'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/async/when.rb:28:in
 `resolve'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/async/when.rb:57:in
 `resolve'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/async/when.rb:103:in
 `block in all'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/async/when.rb:112:in
 `call'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/async/when.rb:112:in
 `block in all'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/async/when.rb:123:in
 `call'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/async/when.rb:123:in
 `block (2 levels) in wait_for_all'
 from

Re: [gitorious] Re: Dolt repo browser 0.4.0 available

2012-10-04 Thread Christian Johansen

Just released 0.5.0.

   - Path/breadcrumb of files always has a clickable leading slash, taking
   you back to the root
   - Tree path always has a clickable leading slash
   - Tree limits how wide it nests when you descend into nested directories
   (try surfing more than three directories deep to see)
   - Fixed lexer loading, so lots more file types should now be correctly
   highlighted

With this release, my todo-list is proper empty, so report whatever you
find.
Christian

On Thu, Oct 4, 2012 at 12:08 PM, Christian Johansen
christ...@cjohansen.nowrote:

 Thanks,

 Turns out I was loading the syntax highlighting language wrong. Fixed
 that, and then Cucumber features works. Will push yet another update later
 today.

 Any chance you can share the repo that caused the crash?

 Christian


 On Thu, Oct 4, 2012 at 11:10 AM, Wari Wahab wari.wa...@gmail.com wrote:

 I was about to test submodules later in the day. Kudos to adding that
 support before I can come around to it.

 The feature file is a simple text file:

 features/myfeature.feature
 -
 Feature: I want moolah
   In order to be rich
   As a poor old lad
   I need to rob a bank

   Scenario: Grab some weapons
 When I head to my stash area
 Then I pick my guns up
 I should be able to cause massive damage
 ---

 PS: a move up one level back button would be great, pressing back just
 don't work as well ;)

 I did get the server to crash when browsing one directory:

  Thin web server (v1.5.0 codename Knife)
  Maximum connections set to 1024
  Listening on 0.0.0.0:3000, CTRL+C to stop
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/json-1.7.5/lib/json/common.rb:223:in
 `encode': \xC3 from ASCII-8BIT to UTF-8
 (Encoding::UndefinedConversionError)
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/json-1.7.5/lib/json/common.rb:223:in
 `generate'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/json-1.7.5/lib/json/common.rb:223:in
 `generate'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/bin/../views/tree_history.erb:1:in
 `evaluate_source'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/tilt-1.3.3/lib/tilt/template.rb:209:in
 `instance_eval'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/tilt-1.3.3/lib/tilt/template.rb:209:in
 `evaluate_source'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/tilt-1.3.3/lib/tilt/template.rb:144:in
 `cached_evaluate'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/tilt-1.3.3/lib/tilt/template.rb:127:in
 `evaluate'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/tilt-1.3.3/lib/tilt/template.rb:76:in
 `render'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/template_renderer.rb:42:in
 `render'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/sinatra/actions.rb:99:in
 `block in tree_history'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/repo_actions.rb:72:in
 `call'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/repo_actions.rb:72:in
 `block in repo_action'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/eventmachine-1.0.0/lib/em/deferrable.rb:151:in
 `call'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/eventmachine-1.0.0/lib/em/deferrable.rb:151:in
 `set_deferred_status'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/eventmachine-1.0.0/lib/em/deferrable.rb:191:in
 `succeed'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/git/repository.rb:49:in
 `block (2 levels) in tree_history'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/eventmachine-1.0.0/lib/em/deferrable.rb:151:in
 `call'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/eventmachine-1.0.0/lib/em/deferrable.rb:151:in
 `set_deferred_status'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/eventmachine-1.0.0/lib/em/deferrable.rb:191:in
 `succeed'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/git/repository.rb:70:in
 `block in build_history'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/eventmachine-1.0.0/lib/em/deferrable.rb:151:in
 `call'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/eventmachine-1.0.0/lib/em/deferrable.rb:151:in
 `set_deferred_status'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/eventmachine-1.0.0/lib/em/deferrable.rb:191:in
 `succeed'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/async/when.rb:28:in
 `resolve'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/async/when.rb:57:in
 `resolve'
 from 
 /home/wari/.rvm/gems/ruby-1.9.3-p194@myhome/gems/dolt-0.4.2/lib/dolt/async/when.rb:103:in
 `block in all'
 from

[gitorious] Dolt repo browser 0.4.0 available

2012-10-03 Thread Christian Johansen

Hey people,

Dolt, our new repository/code browser has now been released in version
0.4.0.
It's roughly complete at this point, incorporating the features we wanted
for
the first version. There are some minor niceties still to fix, but none that
have high priority.

We need as much input as possible on using this with real projects in
various
languages. If you find strange syntax highighting etc, please report. If you
can post a public repo to reproduce strange behavior, even better.

Please try it out and let me know if you experience any issues:

gem install dolt

# Browse a single repo
dolt path/to/repo

# Browse many repos (will list all git repos in given directory)
dolt ~/projects

I will now start integrating this back into Gitorious.

-- 
MVH
Christian

-- 
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] accept merge request via web ui

2011-12-22 Thread Christian Johansen

On Tue, Dec 13, 2011 at 23:23, Vasiliy Tolstov v.tols...@selfip.ru wrote:

 Hello.  I'm install gitorious on my own server - its work's fine! Thank's
 for greate product.
 But one no - how can i accept merge request via web ui? If my users not
 able to run git commands... ?


Hi Vasiliy,

Unfortunately there's no way to do that right now, but it's on our want
list.

Christian

-- 
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] private gitorious server with ssh only help please

2011-12-22 Thread Christian Johansen


 When i try to push to it it tries to get me to ssh to the server as
 the git user instead of using the ssh key.

 If i try to login the git user password i get the error

 fatal: 'test/test.git' does not appear to be a git repository
 fatal: The remote hung up unexpectedly.


This may indicate that the keys have not been added to the git users
authorized_keys. Check the file on disk (~/.ssh/authorized_keys).

Christian

-- 
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: How do you delete a gitorious account?

2011-12-21 Thread Christian Johansen

Just send an email to supp...@gitorious.org with your username, and we'l
ask you to confirm before deleting it. Sorry about the manual stuff - if
someone wants to add automatic deletion to the code base, I'd be happy to
deploy it :)

On Sun, Dec 18, 2011 at 12:36, Ruslan Kiyanchuk zores...@gmail.com wrote:

 Is the account deletion still manual process? If so, what info should
 mention in email in order to get it deleted?

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




-- 
MVH
Christian

-- 
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] Contributing

2011-12-09 Thread Christian Johansen

Hi Rafaen,

Happy to hear you're satisfied and want to contribute! My best tip would be
to start with some resources on Rails. You will probably pick up on the
language, and learning about Rails (2.3 in our case, until we can upgrade)
will teach you about the flow of control, which is not always visible from
staring at the code.

The Rails guides are the best resource I know of online:
guides.rubyonrails.org/
Others may have other tips.

Christian

On Fri, Dec 9, 2011 at 03:38, ' Rafael . dexter...@hotmail.com wrote:

   Hi,

  I have been using a gitorious instance on my server. I have to say It’s
 really great software, I would like to compliment all the team who worked
 on it. I wish I could help in the future. I am Java/PHP developer. So I
 came here to asking suggestions for starting developing ruby. What topics
 should I dominate? For example: Ruby X.X , RoR 3, Copoments, Libraries...

  I would be thankful for the help.

  Regards,

  Rafael



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




-- 
MVH
Christian

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

[gitorious] Private repositories

2011-12-08 Thread Christian Johansen

Hi everyone,

We've started a fund-raiser for private repositories:
http://blog.gitorious.org/2011/12/08/private-repositories/

Feedback/donations welcome!

-- 
MVH
Christian

-- 
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: Push and Clone urls

2011-11-30 Thread Christian Johansen

Did you also clear out old assets? rake assets:clear

On Sat, Nov 26, 2011 at 13:00, DodoFXP felipes...@gmail.com wrote:

 git submodule init  git submodule update did not fix it for me.
 What other debugging steps should I take?
 Felipe

 On Nov 19, 4:55 pm, Mark Ramos mramos1...@gmail.com wrote:
  How did you fix this?
 
  On Oct 18, 5:59 pm, Stephen Johnson st...@thatbytes.co.uk wrote:
 
 
 
 
 
 
 
   Nm fixed it after talking to some people on the irc channel git
   submodule init  git submodule update
 
   On Oct 18, 10:37 am, Stephen Johnson st...@thatbytes.co.uk wrote:
 
Actually it looks like all javascript on the instance is broken i
 have
removed public/stylesheets/all.css public/javascripts/all.js and it
still seems to have a problem.
 
On Oct 17, 1:58 pm, Stephen Johnson st...@thatbytes.co.uk wrote:
 
 I have just setup and new instance from the mainline repos and the
 push and clone urls are not populated. As well as this other
 javascript items are also not working such as the help function on
 that page and the add a group to collaborators.
 Just wondering if this is a know issue if so how do i over come it.

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




-- 
MVH
Christian

-- 
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] directory structure in projects

2011-11-30 Thread Christian Johansen

Nope, just a list of repositories.

Christian

On Wed, Nov 23, 2011 at 22:08, Curtis curtis.wethe...@gmail.com wrote:

 Just wondering if Gitorious supports a directory tree structure
 inside
 projects? Seems it's a flat list of repos?

 ie something like this

 SomeProject
 --device
   --device1.git
   --device2.git
 --app
   --tools
 --Web
   --Sometool.git

 Thanks

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




-- 
MVH
Christian

-- 
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] local gitorious in private mode doesn't require login to view diffs

2011-11-23 Thread Christian Johansen

Hi,

This is a bug in Gitorious. The fix is avilable here:
https://gitorious.org/gitorious/mainline/commit/9e79ab559066252fe6291f24fc35d1d1f0298849

Sorry about that!

Christian

On Thu, Nov 10, 2011 at 22:47, Brendan Cully bren...@kublai.com wrote:

 Hi,

 I'm running a local gitorious with public_mode set to false. This
 seems to mostly work, but I've discovered that the diff viewer (i.e.,
 http://host/proj/repo/commit/source/diff/dest) doesn't
 require a login. I find this a bit disturbing. Does anyone have a fix?

 I'm running off of gitorious mainline
 a5d39d67510f7676b391f8ced06e5937897d774a

 Thanks,
 Brendan

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




-- 
MVH
Christian

-- 
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] permission to view pojects

2011-11-22 Thread Christian Johansen

Hi,

If you are looking for fine-grained permissions, then no. We are currently
working on specifying such a feature, and if funding falls into place, we
will implement this early next year.

Christian

On Tue, Nov 22, 2011 at 10:18, Jhonathas jhonat...@gmail.com wrote:

 Good morning.

 I would like to know if you have permission to view only a few
 projects to login, login now realize that one registered in the system
 is allowed to see all the projects and their commits.

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




-- 
MVH
Christian

-- 
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] Problem changing display/hide url settings

2011-11-04 Thread Christian Johansen

Wiping your database is very unlikely to be helpful. Can you use a tool
like Firebug or the web inspector in Chrome and see if there is a
JavaScript error on the page (where the URLs are missing)?

Christian

On Thu, Nov 3, 2011 at 13:22, Ricardo Gladwell
ricardo.gladw...@gmail.comwrote:

 Hi Christian

 Thanks for the feedback. I believe I've updated the production section in
 the gitorious.yml.

 I also tried running :

 RAILS_ENV=production bundle exec rake assets:clear  touch tmp/restart.txt

 But still no joy :( Should I just restart with a clean database?

 Any advice would be gratefully received.

 TIA...

 -- Ricardo Gladwell



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




-- 
MVH
Christian

-- 
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: tarball download got 'The archive is currently being generated, try again later'

2011-10-31 Thread Christian Johansen

If the tarball is not being built, make sure the poller is running - it is
responsible for starting the job of creating the archive.

Christian

On Fri, Oct 28, 2011 at 19:50, franciscom francisco.manca...@gmail.comwrote:

 Thanks, I have followed your link and others.
 I've installed apache mod configured but still nothing

 There is a way to check if tarball creation is launched ?
 I've found no tarball under /var/www/gitorious/tarball

 any help will be apreciated.

 let me know if you need some info like dir permissions and son on

 On Oct 28, 11:08 am, Wari Wahab wari.wa...@gmail.com wrote:
  Search the group for Xsendfile, I solved a similar problem.. Seehttp://
 groups.google.com/group/gitorious/browse_thread/thread/8f1fa3a...
 
  On 28/10/2011 02:36, franciscom wrote:
 
 
 
 
 
 
 
   Hi:
   have installed two weeks ago gitoriuos on ubuntu 11.04 following:
 
  http://coding-journal.com/installing-gitorious-on-ubuntu-11-04/
 
   I'm able to create repos and commit, but when I try to get tarball I
   got message:
 
   'The archive is currently being generated, try again later'
 
   and nothing happens
 
   There is any way I can try to debug what is happening ?
   Any hint to solve this ?
 
   regards

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




-- 
MVH
Christian

-- 
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] LDAP permissions

2011-10-25 Thread Christian Johansen

Hi,

To prevent unauthorized users from browsing your repositories, you need to
do a couple of things:

   - Set private_mode to true in config/gitorious.yml
   - Disable HTTP pull (these are anonymous by design, and a user could pull
   repos by guessing URLs). This is done by not serving the
   git.yourdomain.com alias to the site (which Gitorious uses for HTTP by
   default)
   - Disable git:// pulls. Same as above. This is achieved by simply not
   running the git daemon.

Christian

On Tue, Oct 25, 2011 at 18:25, Wari Wahab wari.wa...@gmail.com wrote:

  1. is there a way to prevent not authorized users of reading the source
 code?

 Not sure if this would answer for number 2 or not, but number 1 is possible
 if you allow 401 authentication in Apache. I've not tested this, so please
 don't blame me if it totally fails on your side.

 For example, in your /etc/apache2/sites-available/gitorious (or
 gitorious-ssl?), add the following in between the VirtualHosts bits:

   AuthBasicProvider ldap
   AuthName ldap auth
   AuthType Basic
   AuthBasicAuthoritative Off
   AuthLDAPURL ldap://
 some-ldap-site.company.com:389/dc=company,dc=com?sAMAccountName?sub?(objectClass=*)http://some-ldap-site.company.com:389/dc=company,dc=com?sAMAccountName?sub?%28objectClass=*%29
 
   AuthLDAPBindDN COMPANY\someaccounttoauthbind
   AuthLDAPBindPassword this is a very secure password
   Require valid-user

 Of course you will probably need the required apache modules, namely
 auth_ldap, and if you need a certain group to access, you probably need to
 change the AuthLDAPURL line to something appropriate, or have AuthLDAPBindDN
 to some user than can only authenticate some group of people.

 One problem with this though is that your user will have to login twice,
 one to apache, and one to Gitorious.

 If Gitorious allows apache site authentications, i.e. the REMOTE_USER
 variable to login, then authenication mechanisms can be made through apache,
 NTLM, Kerberos, Mysql, LDAP, AD, etc. That would be sweet ;)

 Again, I've not tested this, but this is the kind of configuration we use
 on SVN and other services.


 On Tue, Oct 25, 2011 at 11:24 PM, IronMania ironmani...@googlemail.comwrote:

 Hi,

 1. is there a way to prevent not authorized users of reading the
 source code?
 2. if there is a way, could that be easily combined with LDAP user
 groups?

 Thank you for your Help!
 Joerg

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




-- 
MVH
Christian

-- 
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] Missing tag 2.1.0 in mainline?

2011-10-21 Thread Christian Johansen

Tag is out! https://gitorious.org/gitorious/pages/Upgrading

Christian

On Fri, Oct 21, 2011 at 14:13, Marius Mårnes Mathiesen 
marius.mathie...@gmail.com wrote:

 On Fri, Oct 21, 2011 at 12:38 PM, Wari Wahab wari.wa...@gmail.com wrote:

 **
 YES! My bad! Thanks for the clue :) Worked again for me.


 Ah, great!

 PS: Are you going to incorporate Martin's work with authenticated bind? Or
 at least allow non encrypted LDAP queries. I had to change
 lib/gitorious/authentication/ldap_authentication.rb:

 @encryption = (options[encryption] || simple_tls).to_sym

 to

 @encryption = options[encryption].to_sym if options.key?(encryption)

 In order to get auth to work for my case.


 Hmm, seems like Net::LDAP doesn't let us pass anything to disable
 encryption altogether - so your change sounds reasonable (although
 authenticating over an encrypted line doesn't :-) ). Mind submitting a merge
 request for that?

 As for the authenticated bind I will accept a merge request as long as it:
 - doesn't break any of the tests
 - contains a test case that will fail if we happen to break the
 functionality down the road

 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




-- 
MVH
Christian

-- 
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] git.js: have you seen this?

2011-08-08 Thread Christian Johansen

On Sat, Aug 6, 2011 at 02:11, Rodrigo Rosenfeld Rosas rr.ro...@gmail.comwrote:

 Have you seen this?
 https://github.com/danlucraft/**git.jshttps://github.com/danlucraft/git.js


Yup, have seen it.



 Looks promising :)


It's an interesting project, but still very early days :)

Christian

-- 
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] Using Gitorious with config.action_controller.relative_url_root

2011-08-08 Thread Christian Johansen


 1.) The methods 'configuration' and 'writable_by_query_uri' in lib/
 gitorious/ssh/client.rb construct URI references to the site root
 manually which do not apply when relative_url_root is set. For now,
 I've gotten around this by hardcoding the subpath that I'm using into
 the URI but I was wondering if there was a safer, more correct
 solution that re-used the value from relative_url_root (root_url is
 not available, but I suppose I could read from GitoriousConfig
 directly...would that be advisable?)


I think putting the URL in gitorious.yml would be the right thing to do.
From here we can set it to other relevant places.


 2.) The bigger issue, one that I haven't found a workaround for yet,
 is that the new project action (/gitorious/projects/new in my case)
 tries to redirect to /new instead of /gitorious/new. It appears that
 it is not using the relative_url_root. I've looked at various
 controllers including the project, application, and site controllers
 but haven't found what might be causing this. It also wasn't clear to
 me what in routes.rb might be causing the redirect. Note that when I
 type in myhost.com/gitorious/new manually, I can successfully reach
 the project creation view. I haven't found any other instances in
 Gitorious where this is happening.


Hmm, did you check lib/route_filters/?

I don't see any redirect from /projects/new to /new - does it only happen
when you run it under a directory alias?

Christian

-- 
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] No CSS when logged in

2011-08-08 Thread Christian Johansen

On Fri, Jul 15, 2011 at 18:47, Robert Kirchgessner asuranz...@gmail.comwrote:

 I pulled the latest gitorious mainline this morning and now the user
 logged in page has no CSS. The main site / login page has CSS and
 displays properly, but once logged in the page is just unformatted
 text.

 Where should I look to see what is causing this problem?


Hi,

This was an intermittent problem on master. Please `rm
public/stylesheets/all.css`, pull again and restart your server.

Christian

-- 
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: Your config/gitorious.yml does not have an entry for your current Rails environment.

2011-07-14 Thread Christian Johansen

On Wed, Jul 13, 2011 at 18:55, Tizzy tz3...@gmail.com wrote:

 There are actually no new lines on the secret key... They appear here
 because of how the page is formatted, but the original file I'm taking
 them from has no new lines there :(


Try showing us the configuration file using a paste service that doesn't
break formatting.

Christian

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

[gitorious] New issue tracker, versioning scheme and Gitorious 2.0.0!

Good people of the list,

Thanks to Rodrigo kicking our butts, we have finally landed a few things
we've been thinking about a long time.

Issue tracker
We now have an official issue tracker. You're welcome to report bugs and
feature requests here: https://issues.gitorious.org/projects/gitorious
Please note that I have just set it up, there's not much customization there
yet. Rodrigo also requested a roadmap of some sort, which is not there yet.
I guess we'll try to put some of the features we're working on up there as
issues, but really we have to try and learn as we go here. Any input is
highly appreciated.

Versioning scheme
We have chosen a versioning scheme. The point of it is to make the project
slightly more predictable, and maintenance easier for people who have their
own local installs. The scheme is a three digit version number, where each
number signifies the amount of expected work to upgrade between versions.
Read about it here: https://gitorious.org/gitorious/pages/Versioning

We also decided that today is the launch day for Gitorious 2.0.0. Yay! We
also built a small tool to check your version against available ones. It's
described here: https://gitorious.org/gitorious/pages/Upgrading

To help work with the versioning scheme, I have also written an upgrade
guide, available here: https://gitorious.org/gitorious/pages/Upgrading

This is just the start, we will keep working on these things. Please let us
know if you have comments/feedback/questions.

-- 
MVH
Christian

-- 
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] Bug: minor CSS tweak

Thanks, pushed!

On Wed, Jul 6, 2011 at 12:35, Stefan Hoth goo...@stefanhoth.de wrote:

 Hi,

 since I'm just starting with gitorious and git in general
 I apologize beforehand that I don't fix this problem by supplying a patch. I
 promise I'll do this for later issues when I'm more into the whole process.

 My problem is just a visual one and I noticed it just now: Screenshot of
 the issue
 http://imageshack.us/photo/my-images/827/visualcsserrorgitorious.png/

 Solution is pretty simple:

 In all.css add width: 175px to force the bar to stay within the meta-box.
 #sidebar ul.links.meta li {

1. border-bottom: none;
2. width: 175px;

 }

 I hope someone working on the themes already can mangle this in.

 Thanks,
 Stefan

 PS: I just love gitorious and I thank you very much for open sourcing it!

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




-- 
MVH
Christian

-- 
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: Bug: two little CSS minor issues

Hehe, no problem. 2.0.0 is what is running in production on
gitorious.orgnow, so I'd be surprised if it had such an extreme bug :)

On Thu, Jul 7, 2011 at 15:19, Wiz of Id trumbi...@gmail.com wrote:

 BH SHAME ON ME!

 My fault, some time ago I added the external css
 to _common_head.html.erb, and that did the bug

 Sorry guys :)

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




-- 
MVH
Christian

-- 
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: Gitorious Versioning, Roadmap, Issue Tracking: Chiliproject or Redmine

 Hey guys,

 I have now released Gitorious 2.0.0, a versioning manifesto, an upgrade
 guide and an issue tracker :) Will make a separate post to announce these
 things.


 Great work, Christian! I'm awaiting for your approval in
 issues.gitorious.org. Is there any reason why it is necessary to get the
 administrator's approval?


Hmm, did it say explicitly to wait for admin approval? That's not
intentional. I just discovered that the server had no mail configuration, so
maybe your activation mail got lost? Fixed both problems now, so you're
activated.

Christian

-- 
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] Gitorious Versioning, Roadmap, Issue Tracking: Chiliproject or Redmine

2011-07-06 Thread Christian Johansen

 So, please, take a look at ditz: http://ditz.rubyforge.org/
 It's ruby.
 It has plugable system.
 It offers UI.
 And it's a distributed issue tracking.


I have looked at it, and I find it very interesting. If memory serves me
right, I think the missing piece in Ditz was the UI. But that can be built
on top of it later anyway I guess.

Anyway, we're now concentrating on getting issues.gitorious.org up and
running, and then we'll deal with issue tracking integration for projects
later.

Christian

-- 
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] sphinx error after update of gitorious. search no more working

2011-07-04 Thread Christian Johansen

Hi,

Can you try to also regenerate the sphinx configuration? Seems like you have
stale database information. `bundle exec rake ultrasphinx:configure`

Christian

On Fri, Jul 1, 2011 at 12:22, Wiz of Id trumbi...@gmail.com wrote:

 Hello.

 Almost a week ago:
 - fetched the latest master branch of gitorious
 - reinstalled the gem bundle
 - run rake db:migrate
 - restarted apache
 - fixed some minor issues

 all worked but the search

 Whenever i try to reindex, here's the error and a useless 0 bytes index:

 git-user@myserver:~$ cd /var/www/gitorious.host/gitorious  rake
 ultrasphinx:index RAILS_ENV=production
 (in /var/www/gitorious.host/gitorious)
 $ indexer --config
 '/var/www/gitorious.host/gitorious/config/ultrasphinx/production.conf'
 --rotate --all
 Sphinx 0.9.8.1-release (r1533)
 Copyright (c) 2001-2008, Andrew Aksyonoff

 using config file
 '/var/www/gitorious.host/gitorious/config/ultrasphinx/production.conf'...
 indexing index 'main'...
 ERROR: index 'main': sql_range_query: Unknown column 'base_tags.name' in
 'field list'
 (DSN=mysql://mysqluser:***@localhost:3306/gitorious_production).
 total 0 docs, 0 bytes
 total 0.013 sec, 0.00 bytes/sec, 0.00 docs/sec
 Index rotated ok

 Can't figure out what to do... I did rake db:migrate on top of the
 gitorious folder when I updated

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




-- 
MVH
Christian

-- 
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] Push via http/https?

2011-07-04 Thread Christian Johansen

Hi Ed,

As Rodrigo says, we are almost finished with HTTP push. The missing piece is
the hooks - JGit (which is used in our new Git HTTP server) does not execute
the hook shell scripts, so we are refactoring to be able to use the same
code in the shell scripts and in the JGit hook APIs. We're hoping to have
this done before we go on vacation, but I can give no guarantees.

Christian

On Sun, Jul 3, 2011 at 23:44, Rodrigo Rosenfeld Rosas rr.ro...@gmail.comwrote:

I must say you're lucky, Ed.

If you asked for https push some while ago, the answer would be that you
need SSH for writing to repositories...

There has been work lately on providing push support over https, although
it is not merged to master yet.

Take a look at this recent discussion in this list:

http://groups.google.com/**group/gitorious/browse_thread/**
thread/8a35d92e6f86f7b5#http://groups.google.com/group/gitorious/browse_thread/thread/8a35d92e6f86f7b5#

Good luck!

Em 03-07-2011 12:46, ejs escreveu:

I've set up a gitorious server that is working locally. For our remote
offices, our firewall will only pass https, not SSH or git protocols.
I see that's it's possible to clone via http, and I'm currently
working on getting that working. If http- https is an issue we can
use a proxy to address that, so cloning should be covered. How about
push? Can that be done with only https? Are there any other git
operations that would not work solely via http/https?

Thanks!

--Ed

--
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscribe@**googlegroups.comgitorious%2bunsubscr...@googlegroups.com

--
MVH
Christian

--
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] Problems with private copy of Gitorious

2011-07-04 Thread Christian Johansen

Hi,


 * The login/register screen does not render properly:
  - http://momentum.subtlehints.net/stuff/LoginScreen.png
  - http://momentum.subtlehints.net/stuff/RegisterScreen.png


This was fixed earlier today. Please update from master.



 * I can't create tarballs directly from gitorious:
  - Please Wait - generating tarball appears, but
  - there's nothing on the tarballs-work or tarballs-cache directory
  - you wait forever


Is your poller running? Are jobs being picked off from the queue?

Cheers,
Christian

-- 
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] release checkpoints

2011-07-03 Thread Christian Johansen




 That being said, we will start versioning Gitorious in the very near future
 (http://blog.gitorious.org/2011/01/10/versioning-gitorious/). Even if the
 master branch works, from time to time dependencies are added (or better,
 removed) from Gitorious, and just pulling the branch won't tell you that you
 need to make other changes to your system. By versioning Gitorious we will
 document what kind of changes you need to do on your system to go from
 version x to y.

 I suppose we should really start versioning Gitorious as soon as possible
 We seem to agree on using semantic versioning (http://semver.org), so the
 only thing we really need to determine is which version to start on, maybe
 we could get some inspiration from:
 - The Linux kernel going 3.0 without adding any new features
 - Slackware's 13.37 version

 Any ideas?


Suggestion: We dub the next gitorious.org deploy 2.0.0. Then we start
documenting changes from there, upping the minor and patch versions as
suitable.

Christian

-- 
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: searching quit working for no reason here is the errors I get when I try and start the git-ultrasphinx service

2011-07-03 Thread Christian Johansen

Hi,

It looks like you installed Rails 3.0? Are you using Gitorious with Bundler?
E.g. `bundle exec [script]`? If you do that, the app should run in a
sandboxed environment and you should be fine. If you're using an older
version of Gitorious, you probably need to uninstall Rails 3.0 from the
environment Gitorious is running in.

Christian

On Thu, Jun 30, 2011 at 20:47, Jarrod Roberson jarrod.rober...@gmail.comwrote:

 Here is what is installed on this machine

 [Thu Jun 30 14:46:42] [root]@[dev] /etc/init.d
 # gem list

 *** LOCAL GEMS ***

 abstract (1.0.0)
 actionmailer (3.0.1)
 actionpack (3.0.1)
 activemodel (3.0.1)
 activerecord (3.0.1)
 activeresource (3.0.1)
 activesupport (3.0.1)
 arel (1.0.1)
 BlueCloth (1.0.1)
 builder (3.0.0, 2.1.2)
 bundler (1.0.10, 1.0.3)
 cgi_multipart_eof_fix (2.5.0)
 chronic (0.3.0)
 daemon_controller (0.2.5)
 daemons (1.1.0)
 diff-lcs (1.1.2)
 echoe (4.3.1)
 erubis (2.6.6)
 eventmachine (0.12.10)
 factory_girl (1.3.3)
 fastthread (1.0.7)
 file-tail (1.0.5)
 gem_plugin (0.2.3)
 gemcutter (0.6.1)
 geoip (0.8.9, 0.8.7)
 hoe (2.8.0, 2.6.2)
 json (1.5.0, 1.4.6)
 json_pure (1.5.1, 1.5.0, 1.4.6)
 mail (2.2.9)
 mime-types (1.16)
 mocha (0.9.10, 0.9.9)
 mongrel (1.1.5)
 mysql (2.8.1)
 oauth (0.4.4)
 paperclip (2.2.9.2)
 passenger (3.0.0)
 polyglot (0.3.1)
 rack (1.0.1)
 rack-mount (0.6.13)
 rack-test (0.5.6)
 rails (3.0.1)
 railties (3.0.1)
 rake (0.8.7)
 rdiscount (1.3.1.1)
 RedCloth (4.2.3)
 riddle (1.2.2)
 rspec (2.0.1)
 rspec-core (2.0.1)
 rspec-expectations (2.0.1)
 rspec-mocks (2.0.1)
 rspec-rails (2.0.1)
 ruby-hmac (0.4.0)
 ruby-openid (2.1.8)
 ruby-yadis (0.3.4)
 rubyforge (2.0.4)
 rubygems-update (1.8.5, 1.3.7)
 shoulda (2.9.2)
 spruz (0.2.0)
 sqlite3-ruby (1.3.2)
 state_machine (0.9.4)
 stomp (1.1)
 stompserver (0.9.9)
 thor (0.14.3)
 treetop (1.4.8)
 tzinfo (0.3.23)
 ultrasphinx (1.11)

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




-- 
MVH
Christian

-- 
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] Migration from restful_authentication to Devise status update

2011-06-27 Thread Christian Johansen

   Fix Gemfile.lock
   Duplicated (redundant) oauth dependency in Gemfile
   Removes unused partial view
   Use 2 spaces instead of tabs in sessions/new.html.erb
   Remove vendored state-machine plugin as it was already included in
 Gemfile
   refactoring: replace vendored hodel_3000_compliant_logger with its
 gem
   make reserved? implementation clearer and faster in some cases
   Fix typo
   Only caches url reservations after Rails initialization completes

 You don't need to cherry-pick if you agree with all of them. Just merge
 with Only caches... for instance... I've just rebased to master.


Right. Reviewed, tested and pushed to master!

Christian

-- 
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: Proper protocol

On Fri, Jun 24, 2011 at 11:51, August Lilleaas augustlille...@gmail.comwrote:

 I have a concern with the practicality of using client certificates
 over https instead of SSH.

 You can tell git which key and cert to use for client cert https
 connections. This is done via git-config, so it can be set both
 globally (--global, stored in ~/.gitconfig) and per project (/path/to/
 project/.git/config). Say you're using multiple Gitorious
 installations on a daily basis, i.e. gitorious.org, git.myserver.com,
 git.mycompany.com, etc. Wouldn't each Gitorious installation require a
 separate client cert? If so, you'd have to configure the key and cert
 on a per-repo basis. With SSH, you can use the same ssh keypair for
 all those sites, not requiring any per-repo config, since there's no
 ident info in the public key other than that you was logged in to
 gitorious.org when you added it.


This is definitely a valid concern, and we will investigate accordingly. If
it does have to be configured on a per-repo basis, we could ease this
process by providing a small cli to help out. But ideally, it would just
work. Basically - if we cannot make the experience secure AND easy to use,
we will not drop easier alternatives.

Christian

-- 
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] Proper protocol

 First, I would like you to congratulate you and Johan for the good work and
 efforts you both put on this feature.


Thanks, but my name is Christian. Johan stepped down, remember? :)


  Then, I would like to say that I would be really really sad if SSH support
 was deprecated. I think that providing your public key from a user's point
 of view is really simple and I would to keep that behavior. This would also
 easy the adoption for most people that are already used to Github.


We definitely want to keep the end-user experience nice and simple, no
worries.


  Also, we don't use git over HTTP at all in our company: just git:// and
 SSH.


If you could have well-performing, secure and easy-to-use HTTP pull/push,
then why wouldn't you use it?


  Regarding simplifying installation, I would go with an official automated
 installation recipe using either Opscode Chef or Puppet. As I already
 created a Chef's recipe for installing Gitorious in Debian in about 15
 minutes if internet speed is good enough, it would be a matter of making it
 official so that others can include support for non Debian/Ubuntu systems
 too.


The recipes are great when you can spare an entire server. However, for more
low-end environments, I think it would be awesome to simply `gem install
gitorious-light` to get a bare, but working, system up an running (and one
that could later be migrated to the full Gitorious solution).


 Then, comes my main concern. Until about an year ago, when I tried the git
 plugin for Netbeans, which used JGit if I remember correctly, I had several
 problems with corrupted git repository when using submodules. Even if they
 corrected this, I don't trust the idea of re-writing the git tools for Java.
 I would feel much more comfortable if they had written a Cgit front-end
 instead, just like Grit does. And even that happens, Grit is used in
 Gitorious just to read the file system, not to write to it.


JGit is under heavy development, and I don't have any trouble trusting it.
Also, we're only using it for a very limited set of functionality, which is
fairly easy to test and verify that works correctly. Grit also does stuff on
its own (i.e. in Ruby), and is not always right on the mark either.


 As long as SSH support is kept, I don't mind adding HTTPS push support
 because I won't enable it anyway in our local installation. But I wouldn't
 like to use gitorious.org for hosting my projects if I share them with
 someone else and I can't make sure if he/she will use HTTPS for pushing.
 Probably I wouldn't provide write access to anyone else just to make sure
 only SSH will be used for pushing...


As I've already said many times, we will not deprecate a working solution in
favor of a less capable one, so this shouldn't be a concern. Apart from
that, I don't really get the sceptic attitude against HTTPS push? Why is it
important that only SSH is used for pushing? (Given that the usability issue
can be solved).


 I really don't trust JGit and I don't trust current Java developers either
 after lots of Java code I've been reading lately in largely used Java
 libraries... It is like almost every good Java developers that existed have
 now migrated to some better language, many of them still running on JVM with
 languages like Scala, Closure, Groovy, JRuby, etc...


Take a peak at the JGit code. The parts I've looked at are surprisingly good
;)



 Well, that is my opinion. If the difficult of installing Gitorious is the
 reason for dropping SSH support, I would reply that just writing an official
 Chef's recipe would solve this problem.

 Thanks for asking this on this list!


And thanks for responding - your feedback is greatly appreciated.

Christian

-- 
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] Proper protocol

 So - although I still think that ssh should stay and that GUI client
 support is a valid point: I cannot ignore the thought that I might be
 just a lazy bum that wants to keep it as it is, for the sake of it.


:) No worries. You are definitely right in that we want to reach a wider
audience, but we also want to collaborate with the existing community. It's
not like we're looking for a new audience, we're just trying to improve
Gitorious, and sometimes improvement means change and even stripping things
down.

Christian

-- 
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] Proper protocol


  Thanks, but my name is Christian. Johan stepped down, remember? :)


 Right, sorry, Christian. It is just the new age's effect :)


;)


  If you could have well-performing, secure and easy-to-use HTTP pull/push,
 then why wouldn't you use it?


 Because I want all my repository submodules URL to use git:// protocol
 instead of HTTP and HTTP is enabled by default and I don't want to have to
 worry about that explaining this to my coworkers. We don't have firewall
 issues related to git:// protocol in our company. I find the git protocol to
 be more lightweight than HTTP and usually supported out-of-the-box by git
 tools and I want they to think that Gitorious is just a web interface and
 that we could do everything without Gitorious using other tools if we
 wanted...

 It is important for me that they understand the concepts behind usual Git
 workflow...


For us too, we're not trying to divert anyone from that. Keep in mind that
smart HTTP is part of Git. The reason we cannot use it directly is the path
translation from URLs to hashed paths. Johan once tried to suggest path
translation (or at least hooks for it) be built in to Git itself, but the
request was declined.


 This is my concern: I've lost git commits due to JGit destroying the git
 file-system. I definitely don't want to enable any write support of JGit for
 my repositories... I think Gitorious currently don't use any write support
 from Grit, right?


Understandable. We will test this very thoroughly before recommending its
wide-spread use.


 As long as SSH support is kept, I don't mind adding HTTPS push support
 because I won't enable it anyway in our local installation. But I wouldn't
 like to use gitorious.org for hosting my projects if I share them with
 someone else and I can't make sure if he/she will use HTTPS for pushing.
 Probably I wouldn't provide write access to anyone else just to make sure
 only SSH will be used for pushing...


Don't worry, we won't drop the code :)

 Changing the subject, just as a brief update, I'm almost finished with
 OpenID support with Devise. It is already working but I need to fix some
 other existent problems in Gitorious regarding flash messages that are
 currently not working correctly in the second generation layout and the
 authentication view when errors happen. Also I need to make the test pass,
 even if it means replacing it with an integration test...

 But probably I'll only be able to continue on next weekend since I'm
 leaving to a party now and will be out of town as soon as my wife and me
 wake up tomorrow, returning on Sunday night probably...


Probably better to keep it on the other thread ;) But, that is fantastic
news, cannot wait to give it a spin. If an integration test is what is
required I have no problems with that. Have a great weekend!

Christian

-- 
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: Having issues with create_admin Script

2011-06-22 Thread Christian Johansen

Hey guys,

So sorry about that. I've fixed it on mainline.

Christian

On Wed, Jun 22, 2011 at 13:24, Rodrigo Rosenfeld Rosas
rr.ro...@gmail.comwrote:

 Yes, you're right. This recent commit probably broke the script:

 http://gitorious.org/**gitorious/mainline/commit/**
 909d42da14d186e4580995f24b56aa**4223f7965fhttp://gitorious.org/gitorious/mainline/commit/909d42da14d186e4580995f24b56aa4223f7965f

 It should be fixed in the repository too.

 Cheers, Rodrigo.

 Em 21-06-2011 19:41, Mike escreveu:

  I was able to work around this by making the following change to
 script/create_admin:

 From:

 user = User.new :password =  password, :password_confirmation =
 password, :email =  email, :terms_of_use =  '1'
 user.login = 'admin'
 user.is_admin = true

 To:

 user = User.new :email =  email, :terms_of_use =  '1'
 user.login = 'admin'
 user.is_admin = true
 user.password = password
 user.password_confirmation = password

 Seems to stem from the fact the password and password_confirm are
 protected ActiveRecord properties.

 I'll try to submit a patch once I get a bit more comfortable with
 Gitorious and Ruby in general.

 Hope this helps...

 Regards,
 Mike

 On Jun 18, 7:40 am, Russell Greenwald
 rgreenw...@insourceservices.**com rgreenw...@insourceservices.com
  wrote:

 I'm having issues creating the admin user, I added a ! to user.save
 for debugging.  The error is below.  I'm using strong passwords, but
 no luck, any advice?

 Error Message

 /home/git/gitorious/vendor/**rails/activerecord/lib/active_**record/
 validations.rb:1090:in `save_without_dirty!': Validation failed:
 Password can't be blank, Password is too short (minimum is 4
 characters), Password doesn't match confirmation
 (ActiveRecord::RecordInvalid)

 Here is the create_admin script

 #!/usr/bin/env ruby
 require File.dirname(__FILE__)+'/../**config/environment'
 ActionMailer::Base.raise_**delivery_errors = false
 ActionMailer::Base.delivery_**method = :test

 if User.find_by_is_admin(true)
   puts You already have an Administrator
   exit!
 end

 puts Type in Administrator's e-mail: 
 email = gets.strip
 puts Type in Administrator's password: 
 password = gets.strip

 user = User.new :password =  password, :password_confirmation =
 password, :email =  email, :terms_of_use =  '1'
 user.login = 'admin'
 user.is_admin = true
 if user.save!
   user.activate
   puts Admin user created successfully.
 else
   puts Failed creating Admin user.
 end


 --
 To post to this group, send email to gitorious@googlegroups.com
 To unsubscribe from this group, send email to
 gitorious+unsubscribe@**googlegroups.comgitorious%2bunsubscr...@googlegroups.com




-- 
MVH
Christian

-- 
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: Having issues with create_admin Script

2011-06-22 Thread Christian Johansen

Mainline is intended to be stable. I screwed up, sorry.

Christian

On Wed, Jun 22, 2011 at 20:05, Jacob gelb...@gmail.com wrote:

 Is there a stable branch I should use instead of mainline?

 On Jun 22, 8:33 am, Christian Johansen christ...@cjohansen.no wrote:
  Hey guys,
 
  So sorry about that. I've fixed it on mainline.
 
  Christian
 
  On Wed, Jun 22, 2011 at 13:24, Rodrigo Rosenfeld Rosas
  rr.ro...@gmail.comwrote:
 
 
 
 
 
 
 
 
 
   Yes, you're right. This recent commit probably broke the script:
 
  http://gitorious.org/**gitorious/mainline/commit/**
   909d42da14d186e4580995f24b56aa**4223f7965f
 http://gitorious.org/gitorious/mainline/commit/909d42da14d186e4580995...
 
   It should be fixed in the repository too.
 
   Cheers, Rodrigo.
 
   Em 21-06-2011 19:41, Mike escreveu:
 
I was able to work around this by making the following change to
   script/create_admin:
 
   From:
 
   user = User.new :password =  password, :password_confirmation =
   password, :email =  email, :terms_of_use =  '1'
   user.login = 'admin'
   user.is_admin = true
 
   To:
 
   user = User.new :email =  email, :terms_of_use =  '1'
   user.login = 'admin'
   user.is_admin = true
   user.password = password
   user.password_confirmation = password
 
   Seems to stem from the fact the password and password_confirm are
   protected ActiveRecord properties.
 
   I'll try to submit a patch once I get a bit more comfortable with
   Gitorious and Ruby in general.
 
   Hope this helps...
 
   Regards,
   Mike
 
   On Jun 18, 7:40 am, Russell Greenwald
   rgreenw...@insourceservices.**com rgreenw...@insourceservices.com
wrote:
 
   I'm having issues creating the admin user, I added a ! to user.save
   for debugging.  The error is below.  I'm using strong passwords, but
   no luck, any advice?
 
   Error Message
 
   /home/git/gitorious/vendor/**rails/activerecord/lib/active_**record/
   validations.rb:1090:in `save_without_dirty!': Validation failed:
   Password can't be blank, Password is too short (minimum is 4
   characters), Password doesn't match confirmation
   (ActiveRecord::RecordInvalid)
 
   Here is the create_admin script
 
   #!/usr/bin/env ruby
   require File.dirname(__FILE__)+'/../**config/environment'
   ActionMailer::Base.raise_**delivery_errors = false
   ActionMailer::Base.delivery_**method = :test
 
   if User.find_by_is_admin(true)
 puts You already have an Administrator
 exit!
   end
 
   puts Type in Administrator's e-mail: 
   email = gets.strip
   puts Type in Administrator's password: 
   password = gets.strip
 
   user = User.new :password =  password, :password_confirmation =
   password, :email =  email, :terms_of_use =  '1'
   user.login = 'admin'
   user.is_admin = true
   if user.save!
 user.activate
 puts Admin user created successfully.
   else
 puts Failed creating Admin user.
   end
 
   --
   To post to this group, send email to gitorious@googlegroups.com
   To unsubscribe from this group, send email to
   gitorious+unsubscribe@**googlegroups.com
 gitorious%2Bunsubscribe@googlegrou ps.com
 
  --
  MVH
  Christian

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




-- 
MVH
Christian

-- 
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] Christian's fix didn't work

2011-06-08 Thread Christian Johansen

On Thu, Jun 9, 2011 at 03:33, Rodrigo Rosenfeld Rosas rr.ro...@gmail.comwrote:

 I would just like to point out that the commit below didn't work as
 expected:

 3f7334dd9c58d95272bbcb48b2bf82006697: Make sure repository tests start
 with no repositories

 I had the same problem again while running the tests even with the commit
 applied. I'm sorry the problem remains :(


Was it the same test failing? I'm aware that this fix is a mere
work-around. The problem is that all tests don't properly clean up after
themselves, and I didn't have time to go over every test.


 Changing the subject, I've pushed some commits today to rails-3.1-devise
 branch. Please, take a look. I didn't amend for easing your review.


Will do!

Christian

-- 
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] Migration from restful_authentication to Devise status update

2011-06-07 Thread Christian Johansen

Great work Rodrigo!

Marius and I have reviewed your work so far, and here is our feedback:

The password field changed length from 40 to 128. Is the idea here to make
encryption strategy configurable?

This comment:

  # I'm not sure if the tests are correct. TODO: verify if we really
need
  # this skip filter. Also notice that this is Devise's internal and can
  # change in future versions. It doesn't make much sense to access new
or
  # create while logged in. By default, once the user is already logged
in,
  # Trying to access them will redirect to '/' before the action is
called.

I'm not entirely sure what you mean here. What's the underlying problem?

As for the session/caching problems; I will add a test for this on master.

It appears that one of our foulest hacks (logged_in = :false) is going away,
is that right? :) If so, yuppie!

The Varnish cache/cookie stuff can be removed entirely. I suspect this was
added before properly understanding how Varnish works - Basically, as long
as the app sends a session cookie, Varnish will not touch the response.

Is the AuthenticatedSystem module going to stay around? Seems most of it has
moved inside of Devise. The only remaining parts are the remember path
related pieces, am I right?


This diff:

   def login_as(user)
-@request.session[:user_id] = user ? user_instance(user).id : nil
-@request.session_options[:expire_after] = 1.hour
+if user
+  sign_in :user, user_instance(user)
+else
+  sign_out :user
+end

This is much better than setting the :user_id manually in tests. However, I
think it might be easier to read the tests if we used `logout` rather than
`login_as nil`. What do you think?

This assertion is repeated (and thus changed) very many times in the tests:
assert_redirected_to(new_user_session_path)

I suggest we replace it with a custom assertion, something along the lines
of assert_redirected_to_login. This way we can change the login semantics
without having to touch all the tests.

Same thing goes for this snippet: assert warden.authenticated?. I'd prefer
assert authenticated?, where `authenticated?` can be defined in our
authentication test helper.


+  post :create, :user = {:email = jo...@johansorensen.com,
:password = test}
+  assert warden.authenticated? # - over specification
+  get :destroy
+  assert !warden.authenticated?

This may be a little nitpicking, but this test is over specified. The first
assertion is not necessary, because there is another test that ensures that
the `post :create` logs the user in. I suggest you just remove it.


   def controller_names_plural
-return @controller_names_plural unless
@controller_names_plural.blank?
+# don't cache while Rails didn't finish initialization
+return @controller_names_plural if
@controller_names_plural.present?  Rails.initialized?
 @controller_names_plural =
ActionController::Routing.possible_controllers.map{|s| s.split(/).first }
   end

In what cases is this snippet run before Rails is properly initialized?

This is mostly nitpicking. All over great work, Rodrigo!

Christian


On Mon, Jun 6, 2011 at 02:43, Rodrigo Rosenfeld Rosas rr.ro...@gmail.comwrote:

 Please review this branch:


 https://gitorious.org/~rosenfeld/gitorious/rosenfeld-gitorious/commits/rails-3.1-devise
 https://gitorious.org/%7Erosenfeld/gitorious/rosenfeld-gitorious/commits/rails-3.1-devise
 

 It is rebased with mainline/master. All commits can be merged to master
 except the last one, which is not completed yet.

 Currently, here are the missing bits:

 - Cookies are not marked as secure yet;
 - OpenID authentication is the only failing test and is not implemented
 yet. I still need to investigate how OpenID works in Gitorious. But this
 needs a rework for sure in the user interface with buttons pointing out to
 Google, Yahoo, etc besides the OpenID URL edit for easing its usage. Maybe
 we could do that after migrating Gitorious to Rails 3;
 - The session expire check was disabled for the SSL tests to pass. It would
 be great to add some test for verifying this cache behavior. I didn't verify
 yet if this check is necessary for Warden/Devise;
 - There is no test regarding the Varnish cache server and I don't know what
 to expect from it;

 Please review the current status and guide me with suggestions for
 achieving the missing parts and detect bugs not covered by tests as well as
 improvement suggestions to the patch.

 If someone wants to help integrate OpenID to Gitorious with Devise, one can
 start from here:


 https://gitorious.org/~rosenfeld/gitorious/rosenfeld-gitorious/commits/rails-3.1-devise-openid-temp
 https://gitorious.org/%7Erosenfeld/gitorious/rosenfeld-gitorious/commits/rails-3.1-devise-openid-temp
 

 There is nothing yet, except from new dependencies set.

 Here is an example application using Devise and the
 devise_openid_authenticable gem:

Re: [gitorious] gitorious host not being picked up

2011-06-06 Thread Christian Johansen

Cool, thanks Shane!

On Fri, Jun 3, 2011 at 17:46, ShaneOG shane.ogr...@gmail.com wrote:

 And another merge request as I'm learning more about Ruby  Gitorious: 158

 S

 On Monday, 30 May 2011 18:40:39 UTC+1, Christian Johansen wrote:

 On Mon, May 30, 2011 at 16:14, ShaneOG shane@gmail.com wrote:

 Thanks Marius,

 I've made one more change/fix which prevents browser SSL warnings when
 Gitorious is served over SSL only.
 Merge request 155.


 Pulled, thanks :)

 Christian

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




-- 
MVH
Christian

-- 
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] Problem in installing Git

2011-05-31 Thread Christian Johansen

On Mon, May 30, 2011 at 17:24, Abhijit abhijit.dw...@gmail.com wrote:

 While installing Git according to  
 http://help.github.com/win-set-up-git/
  site; i cannot understand the step 4.

 it's written that On the GitHub site Click “Account Settings”  Click
 “SSH Public Keys”  Click “Add another public key”, but where one can
 find the “Account Settings”  GitHub site.


Are you trying to use Gitorious or GitHub? If you want to use Gitorious,
paste your SSH key here: https://gitorious.org/~YOUR_USERNAME/keys/new

Christian

-- 
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] New messaging API and adapters

2011-05-31 Thread Christian Johansen

On Tue, May 31, 2011 at 12:25, Rodrigo Rosenfeld Rosas
rr.ro...@gmail.comwrote:

 Em 31-05-2011 04:38, Christian Johansen escreveu:

  Hi,

 I've just pushed the completed version of Gitorious' new messaging API:
 https://gitorious.org/gitorious/mainline/commits/unified-messaging-api We
 aim to get this merged to master in a week or so (we're currently running it
 in staging to avoid potential problems in production) - we also want to give
 you guys the opportunity to comment on this before we merge it in.

 What is this new API? Basically it's an intermediary between Gitorious and
 the concrete messaging queue implementation. It moves the previously
 obtrusive ActiveMessaging bindings out to an adapter, and makes room for
 more adapters, such as the new Sync, Test and Resque adapters.

 For developers, this change is interesting because simply by setting
 messaging_adapter: sync in your gitorious.yml, you can have everything
 processed without running a separate poller of any kind. The sync adapter
 might also work for low traffic setups where resource usage is an issue (and
 performance is not).

 For people running Gitorious, an upgrade should be painless. The default
 implementation (even if you don't update your configuration file) is the old
 Stomp adapter, and should work as expected.

 I've created a merge request for this changeset, and would love your
 comments, questions and review:
 https://gitorious.org/gitorious/mainline/merge_requests/156. Let me know
 what you think.


 I'll take a look at it and will give you my feedback. I'm specially
 interested in what app/processors became.

 Thanks for your work!


Looking forward to your review. Some of the wiring stuff is a bit sneakier
than I'd like, so if you have suggestions for improvement, that would be
much appreciated. Also, a word of warning, the ActiveMessaging consumer is
really strange, mostly due to ActiveMessaging's weird API :( Marius did a
spike earlier today that uses EventMachine and Stomp directly to consume
messages, I think we'll move to that very soon.

The processors are pretty much the same, only slightly more explicit:

class PushProcessor
  include Gitorious::Messaging::Consumer
  consumes /queue/GitoriousPush

  # ...
end

We dropped the symbolic indirection for queues, which has little value, and
ditched inheritance in favor of modules. This also brings some symmetry to
the solution as publishers do the same thing:

class SshKey  ActiveRecord::Base
  include Gitorious::Messaging::Publisher

   # ...
end

(Compared to ActiveMessaging, which includes stuff in ActiveRecord::Base).

Christian

-- 
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] fatal errors in clone over ssh resulting from internal http errors

2011-05-30 Thread Christian Johansen


  First question would then be how to best make a unified go of it [...]

 I found this also brought up before in merge request #2219 and again quite
 a long time ago at
 https://groups.google.com/group/gitorious/browse_thread/thread/8e2f965733d5d56d/8c814f3baa5ebdf0?q=root_path+gitorious+sub+uri#8c814f3baa5ebdf0...
  and these led me to notice
 ~rlandrito/gitorious/rl-mainline:non_root_url, which I guess would be a good
 place to start not reinventing the wheel (if anyone else stumbles across
 this subject again and wants next steps).


Hi,

Yes, well
https://gitorious.org/~rlandrito/gitorious/rl-mainline/commits/non_root_urlis
a good start. Configuring it from gitorious.yml makes sense. But this
branch does not (as far as I can tell) set the relative url on
ActionController as suggested by Marius on the mailing list. I'd recommend
you include that too. Other than that, if the tests pass, and you build new
tests (I suggest integration tests that 'browse' gitorious) that shows sub
uri's working, I don't have a lot of strong opinions as to how to solve the
rest.

-- 
MVH
Christian

-- 
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] gitorious host not being picked up

2011-05-30 Thread Christian Johansen

On Mon, May 30, 2011 at 16:14, ShaneOG shane.ogr...@gmail.com wrote:

 Thanks Marius,

 I've made one more change/fix which prevents browser SSL warnings when
 Gitorious is served over SSL only.
 Merge request 155.


Pulled, thanks :)

Christian

-- 
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] Rails 3.1 branch rebasing

2011-05-27 Thread Christian Johansen




 But since you're asking so critically I have to admit I'm not entirely sure
 if the session check is entirely required. However, it did seem to be the
 thing that caused all the tests to fail? Maybe Marius has better memory than
 me here?

 The only case we could think of that uses the session without the user
being logged in is in the case of flash messages. However, flash messages
are only used in actions that are POST-ed to, in which case the user should
be on https already. So I think we can remove that part.

I will fix this method on master.

Christian

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

[gitorious] New session url with Devise

2011-05-27 Thread Christian Johansen

Rodrigo,

As we discussed on irc, I checked out your devise branch and looked at the
generated URLs. However, according to `rake routes`, new_user_session
resolves to /users/sign_in, which is not the problem you reported. Do I
have to poke in a particular way to provoke the error you described?

-- 
MVH
Christian

-- 
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] gitorious host not being picked up

2011-05-27 Thread Christian Johansen


 Also, I've noticed that in app/helpers/application_helper.rb the following
 is defined:

   def dashboard_path
 root_url(:host = GitoriousConfig[gitorious_host], :protocol =
 http)
   end

 Shouldn't http in that be replaced with GitoriousConfig[scheme] ?


It probably should :) We would really appreciate your help Shane!

Christian

-- 
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] fatal errors in clone over ssh resulting from internal http errors

On Mon, May 23, 2011 at 23:40, h...@exultant.us wrote:

Right. Am I understanding this correctly that you are not exposing
Gitorious over HTTP at all? Only HTTPS?

Just so. Is there a configuration option somewhere for this that I might
have missed? (Actually, thb I'm a bit vague on why gitorious has this
indirection at all -- I suppose I could write some more rules in apache
config to allow http connections to those urls from localhost only, but it
seems like there ought to be a more direct approach to all this than making
HTTP requests after SSHing; gitorious can just call itself as ruby without
rails/passenger at that point and get the job done that way, can't it?)

We will probably move to doing this without HTTP, yes. As for your issue,
see this thread:
http://groups.google.com/group/gitorious/browse_thread/thread/36ad12033bbd651aIt's
not actually clear to me if Marius' proposed fix worked, but if you
could try it too and confirm I will push this to master.

will there be any patches coming down the line for making sub-URI
installs work a little more smoothly?

There are currently no specific plans to do so, but I'm all for it. I
don't think it will be a huge job. If anyone is up for doing it (remember
tests!) I'll be happy to merge it in.

(Another option is to fund development which would allow us to more easily
prioritise it. Sorry for the blatant sell, but we're doing Gitorious for a
living, and there's a lot to do, can't prioritise it all...)

Well, I'm liable to throw some time into it when I get copious amounts of
it free myself to come to grips with ruby, but I'm just a university
researcher and I'm afraid I haven't got that budget, and even if I could
repurpose some grant money I don't rightly think I've got a chance at
selling it to my lab without the HTTPS issues all fixed and something along
the lines of merge request 115 getting into mainline. Anyway!

Sure, I thought I'd just mention it. Something along the lines of 115 will
probably land some day, but currently this would require funding somehow, as
we're not going to use it on gitorious.org.

First question would then be how to best make a unified go of it, since
there's not currently an entry for specifying the web URI in gitorious.yml,
but quite a few parts of the system adapt just fine anyway. In other words,
I don't think it'd take me too much time to hack some more string ops
throughout, but it seems like it'd be in the best interest of the project to
make sure there's a single idiom used consistently for this (and I don't
think that's something it would be appropriate for me to be taking the lead
on per se). I see at
http://www.modrails.com/documentation/Users%20guide%20Apache.html#sub_uri_deployment_uri_fixthat
Rails comes with some functions that help with this on the actual HTML
generation side of things, but they appear to be radically overspecialized
and not so useful as a result.

I did some experimenting with Passenger sub urls a while ago. I concluded
that it only solves part of the puzzle, but unfortunately I seem to have not
taken any notes as to what the specific problems were. If we could make the
Passenger route work that would probably be the cleanest solution. I guess
the remaining problem is making sure Gitorious always gets its URLs from
Rails. This is not the case for instance in the ssh client, which pieces
together the URL as a string (because it runs without the Rails
environment). So - I suspect we need a setting in gitorious.yml anyway.

I do also have a couple tickets open at the lighthouse site that should be
specific enough to make really short work of some low-hanging fruit for
anyone already familiar with where things are in the codebase.

I will take a look.

Christian

--
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] Authentication questions

On Tue, May 24, 2011 at 14:47, Rodrigo Rosenfeld Rosas
rr.ro...@gmail.comwrote:

  I've tried asking this on IRC, but no one was there at that time, so here
 are the questions:


As I understand, this issue was resolved on IRC, and no, it's not a problem
to change the name.

Christian

-- 
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: Status update on migration from restful_authentication to Devise

First of all: great job once again Rodrigo :)


 That is all fantastic when it is finished, but I'm a bit far of finishing
 it right now. There is a lot of things to do yet.

 I need to get rid of the SessionsController and think what to do about its
 functional tests. I think we should move it to integration tests. Can I add
 the capybara gem dependency to tests?


Moving this over to integration tests seems just fine to me. Any particular
reason you could not use the Rails integration tests for this?



 Also, I guess the only reason for Gitorious to set the _logged_in cookie
 is to easy the functional tests for they knowing if the user was correctly
 authenticated. I don't like this approach very much and I'm going to remove
 it if that is ok with you. This could be set adding a Warden hook after
 successful authentication, but I really don't think this is a great approach
 for testing this. In the integration tests, I'll try to do something like
 this:

 in setup:
get '/logout' # don't remember exactly the URL...

 in the test:
try_to_log_in_with_some_method
check_for_presence_of login_name


Sounds fine.


 Or something like that... I've noticed that Gitorious tests used to be
 specs using Rspec sometime in the past. Then, there was one commit
 converting them all to Shoulda. Is there any reason why RSpec was dropped? I
 really like to read specs because they are clearer to me. For instance:

non_admin_user.should_not be_allowed_to_view('/admin')

 And then, adding a custom RSpec matcher for BeAllowedToView.


Well, basically, neither Marius nor I care much for RSpec, so going back is
not an option at this point. Anyway, it's just as easy to create helpers and
custom assertions, so I see this mostly as a matter of syntax preference.


 Getting back to strategies, the rememberable strategy will store the cookie
 for 2 weeks by default in Devise, which is the same period Gitorious
 currently use. Should I make this time span explicit in Devise config of is
 it ok for Gitorious to rely on Devise's default? Also, I needed to change
 the field names to use the user scope. For instance, input name=email
 should be changed to input name=user[email].


It would be nice to be explicit on the configuration here so we control our
own defaults. If it's not too much work you might as well add a
session_timeout config option to gitorious.yml (you don't have, just an
idea).


 Gitorious currently use the auth_token cookie for storing this setting,
 but I'll change it to authenticated_user_token (or something like that),
 which is used by the :rememberable strategy implemented by Devise for
 avoiding creating another strategy just for maintaining the same cookie
 name. Also, Devise 1.0 won't set the cookie as secure I guess. But I'm not
 worried with it right now since the newest Devise support passing options to
 generated cookies in Devise config, so we can do that later after migrating
 to Rails 3 and newest Devise. If Devise is going to be merged into master
 before we convert Gitorious to Rails 3, we'll probably need to replace the
 Rememberable strategy with a custom one anyway for keeping the cookie
 secure... I'll take a closer look at this later...


This worries me a bit, because I suspect we will take some heat for security
regressions, even if only temporary. Is there a convenient way to monkey
patch Device to add the secure option? Just while we wait for Rails 3.


 This is another thing I would like to talk about: timing for merging this.
 If we keep such a big change in a separate branch for a long while, it will
 be very hard to rebase or merge it with master as the time passes. It would
 be great if we could integrate it as soon as possible to master once it is
 finished. Is it possible?


Of course it's possible! If it works, we'll use it :) What we usually do
with changes of this magnitude is to deploy changes to an internal staging
area for a week or so before launching it on gitorious.org.



 I'll keep you updated of this progress.


Awesome stuff Rodrigo :)

Christian

-- 
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] Rails 3.1 branch rebasing

  I don't know yet why the SSL enforcing tests are failing yet. I was
 focused on getting the basic database authentication working. Now, I'm going
 to add support for OpenID and Basic HTTP Auth and then I'll take a look back
 at the SSL tests.


Ok, here's why: The ssl_required? filter in application_controller.rb checks
if the session is active. It does that by looking at
request.session_options[:expire_after]. I suspect that Device does not use
these options at all, so whatever Device uses for sessions needs to be
plugged into that method. Any ideas for a good replacement?

Christian

-- 
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: Status update on migration from restful_authentication to Devise


 Actually this is just a matter of taste, like with RSpec. I prefer to read
 specs as well as Capybara write syntax (visit url, etc). The tests get much
 more readable for my taste. But I'll do it using Rails integration tests if
 you prefer.


Ok. I was a bit worried that Capybara implied Cucumber, and I'm not all that
into that :) So, if Capybara tests will still run fast, and stay readable (I
think the default runner is RackTest, so that should be in-memory and fast,
right?) you're welcome to give it a go with one test case, and we can decide
from that, ok?



 This worries me a bit, because I suspect we will take some heat for
 security regressions, even if only temporary. Is there a convenient way to
 monkey patch Device to add the secure option? Just while we wait for Rails
 3.


 Yes, that is what I've said. Since you are open to change to Devise before
 we finish the migration to Rails 3, then we *should* use secure cookies. In
 that case we can either write another strategy, or monkey patch the current
 strategy or send a pull request to Devise 1.0 branch (prefered alternative
 for me) to make it compatible with newest Devise.


Sure, we can send them a pull request, seems like the better option.


  Of course it's possible! If it works, we'll use it :) What we usually do
 with changes of this magnitude is to deploy changes to an internal staging
 area for a week or so before launching it on gitorious.org.


 This remembers me another thing I would like to talk with you. Is it
 possible for you to set some staging server that could be tested by the
 public? I mean, backup data and repositories from the official Gitorious and
 make them available in a staging server. That way, before we migrate to
 Rails 3, people would be able to try it and report any problems... Of course
 that changes involving security like cookie or password stealing, etc,
 couldn't be available with real data in this staging server, but I think
 that for the other changes this could be a great idea...


I agree that having a public staging area would be cool. I'm not quite sure
how we should actually do this, but I'll think about it.


 Thanks. Unfortunately, I wasn't able to work on Gitorious yesterday night.
 I've spent all my little free time watching the awesome Aaron Patterson
 (tenderlove) talk on RailsConf :)


Yeah, he is awesome :)

Christian

-- 
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] Rails 3.1 branch rebasing