Discussion:
tracks on rails3
Reinier Balt
2012-05-18 18:38:07 UTC
Permalink
Hi all

I've just merged the rails3 branch. This means that
* Tracks is migrated to rails 3
* Tracks runs on ruby 1.9 (tested on 1.9.3)

This migration has some consequences:
* support for ruby 1.8.7 is going away. You need to have ruby 1.9.x for the
test environment because some gems depend on it. (ruby 1.8.7 will be
unsupported from this summer IIRC; Rails 4 will also work only on ruby 1.9)
* I hope to maintain tracks 2.2 on 1.8.7, but only if it isn't too hard (I'd
like to focus my energy on other stuff). N.B. My own Tracks server is
running ruby 1.8.7, probably until I migrate it to Fedora 18 in the end of
the year (FC17 will include ruby 1.9)
* I had to remove support for openid, cas and ldap. I have no means to test
it (cas, ldap) and the gems we used for openid is not supported anymore. I'd
like to move to device/omniauth to get support back in, preferably in the
2.2 timeframe.
* I had to remove SOAP support, because the gem is not really available for
rails 3.2 and SOAP is not really believed in anymore by the rails community.
This means you may need to migrate your scripts (email-to-tracks?) to REST.
* I you try rails in production environment, do not forget to run
rake assets:precompile
to get all js, css and images working. This is not needed for development
and test environment.
* If you have ruby 1.8.7, run
bundle install --without test
to avoid installing factory-girl which depends on ruby 1.9

I did get almost all tests running. Those tests not passing have issues with
the tests, not Tracks functionality :-)

Please help test Tracks on Rails 3.2 out!

Reinier
Sebastian Fischmeister
2012-05-21 23:31:19 UTC
Permalink
Great job. How do I start the local server in rails 3? The following
doesn't work:

./script/server -e development

Thanks,
Sebastian
Post by Reinier Balt
Hi all
I've just merged the rails3 branch. This means that
* Tracks is migrated to rails 3
* Tracks runs on ruby 1.9 (tested on 1.9.3)
* support for ruby 1.8.7 is going away. You need to have ruby 1.9.x for the
test environment because some gems depend on it. (ruby 1.8.7 will be
unsupported from this summer IIRC; Rails 4 will also work only on ruby 1.9)
* I hope to maintain tracks 2.2 on 1.8.7, but only if it isn't too hard (I'd
like to focus my energy on other stuff). N.B. My own Tracks server is
running ruby 1.8.7, probably until I migrate it to Fedora 18 in the end of
the year (FC17 will include ruby 1.9)
* I had to remove support for openid, cas and ldap. I have no means to test
it (cas, ldap) and the gems we used for openid is not supported anymore. I'd
like to move to device/omniauth to get support back in, preferably in the
2.2 timeframe.
* I had to remove SOAP support, because the gem is not really available for
rails 3.2 and SOAP is not really believed in anymore by the rails community.
This means you may need to migrate your scripts (email-to-tracks?) to REST.
* I you try rails in production environment, do not forget to run
rake assets:precompile
to get all js, css and images working. This is not needed for development
and test environment.
* If you have ruby 1.8.7, run
bundle install --without test
to avoid installing factory-girl which depends on ruby 1.9
I did get almost all tests running. Those tests not passing have issues with
the tests, not Tracks functionality :-)
Please help test Tracks on Rails 3.2 out!
Reinier
_______________________________________________
Tracks-discuss mailing list
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
Sebastian Fischmeister
2012-05-24 21:21:40 UTC
Permalink
How do I then start the development mode and which configuration file
does it use? It seems to use some different configuration file now on
my setup.

Thanks,
Sebastian
rails server
instead of ./script/server
Thanks
--
Matt
Post by Sebastian Fischmeister
Great job. How do I start the local server in rails 3? The following
./script/server -e development
Thanks,
Sebastian
Post by Reinier Balt
Hi all
I've just merged the rails3 branch. This means that
* Tracks is migrated to rails 3
* Tracks runs on ruby 1.9 (tested on 1.9.3)
* support for ruby 1.8.7 is going away. You need to have ruby 1.9.x for the
test environment because some gems depend on it. (ruby 1.8.7 will be
unsupported from this summer IIRC; Rails 4 will also work only on ruby 1.9)
* I hope to maintain tracks 2.2 on 1.8.7, but only if it isn't too hard (I'd
like to focus my energy on other stuff). N.B. My own Tracks server is
running ruby 1.8.7, probably until I migrate it to Fedora 18 in the end of
the year (FC17 will include ruby 1.9)
* I had to remove support for openid, cas and ldap. I have no means to test
it (cas, ldap) and the gems we used for openid is not supported anymore. I'd
like to move to device/omniauth to get support back in, preferably in the
2.2 timeframe.
* I had to remove SOAP support, because the gem is not really available for
rails 3.2 and SOAP is not really believed in anymore by the rails community.
This means you may need to migrate your scripts (email-to-tracks?) to REST.
* I you try rails in production environment, do not forget to run
rake assets:precompile
to get all js, css and images working. This is not needed for development
and test environment.
* If you have ruby 1.8.7, run
bundle install --without test
to avoid installing factory-girl which depends on ruby 1.9
I did get almost all tests running. Those tests not passing have issues with
the tests, not Tracks functionality :-)
Please help test Tracks on Rails 3.2 out!
Reinier
_______________________________________________
Tracks-discuss mailing list
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
_______________________________________________
Tracks-discuss mailing list
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
Reinier Balt
2012-05-25 09:28:40 UTC
Permalink
rails s -e production
it uses /path/to/tracks/config/environments/production.rb

environment.rb is moved to application.rb in /config, this is a rails3
change. So probably you may need to migrate your custom settings to there

Reinier
-----Oorspronkelijk bericht-----
Namens Sebastian Fischmeister
Verzonden: donderdag 24 mei 2012 23:22
Aan: Matt Rogers
Onderwerp: Re: [Tracks-discuss] Re: tracks on rails3
How do I then start the development mode and which configuration file does
it use? It seems to use some different configuration file now on my setup.
Thanks,
Sebastian
rails server
instead of ./script/server
Thanks
--
Matt
Post by Sebastian Fischmeister
Great job. How do I start the local server in rails 3? The following
./script/server -e development
Thanks,
Sebastian
Post by Reinier Balt
Hi all
I've just merged the rails3 branch. This means that
* Tracks is migrated to rails 3
* Tracks runs on ruby 1.9 (tested on 1.9.3)
* support for ruby 1.8.7 is going away. You need to have ruby
1.9.x for the test environment because some gems depend on it.
(ruby 1.8.7 will be unsupported from this summer IIRC; Rails 4
will also work only on ruby 1.9)
* I hope to maintain tracks 2.2 on 1.8.7, but only if it isn't too
hard (I'd like to focus my energy on other stuff). N.B. My own
Tracks server is running ruby 1.8.7, probably until I migrate it
to Fedora 18 in the end of the year (FC17 will include ruby 1.9)
* I had to remove support for openid, cas and ldap. I have no
means to test it (cas, ldap) and the gems we used for openid is
not supported anymore. I'd like to move to device/omniauth to get
support back in, preferably in the
2.2 timeframe.
* I had to remove SOAP support, because the gem is not really
available for rails 3.2 and SOAP is not really believed in anymore
by the
rails community.
Post by Sebastian Fischmeister
Post by Reinier Balt
This means you may need to migrate your scripts (email-to-tracks?)
to
REST.
Post by Sebastian Fischmeister
Post by Reinier Balt
* I you try rails in production environment, do not forget to run
rake assets:precompile to get all js, css and images working. This
is not needed for development and test environment.
* If you have ruby 1.8.7, run
bundle install --without test
to avoid installing factory-girl which depends on ruby 1.9
I did get almost all tests running. Those tests not passing have
issues with the tests, not Tracks functionality :-)
Please help test Tracks on Rails 3.2 out!
Reinier
_______________________________________________
Tracks-discuss mailing list
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
_______________________________________________
Tracks-discuss mailing list
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
tiki
2012-05-23 17:20:28 UTC
Permalink
I all,
Got a question, how could i transfert a complete action from one user to
a new one for another user?

Example:
UserA need to buy something.
When finshed
UserB sould install it.
Reinier Balt
2012-05-24 07:25:07 UTC
Permalink
Not. Tracks cannot share / exchange actions between users.

Reinier
-----Oorspronkelijk bericht-----
Verzonden: woensdag 23 mei 2012 19:20
Onderwerp: [Tracks-discuss] transfert tasks
I all,
Got a question, how could i transfert a complete action from one user to a
new one for another user?
UserA need to buy something.
When finshed
UserB sould install it.
_______________________________________________
Tracks-discuss mailing list
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
Hans de Graaff
2012-05-28 08:19:46 UTC
Permalink
Post by Reinier Balt
Hi all
I've just merged the rails3 branch. This means that
* Tracks is migrated to rails 3
rake db:migrate fails for me:

== AddRenderedNotes: migrating
===============================================
-- add_column(:todos, "rendered_notes", :text)
-> 5.4755s
-- Clearing show_from dates from completed todos
-- Generating new column values from notes. This may take a while.
rake aborted!
An error has occurred, all later migrations canceled:

undefined method `[]' for false:FalseClass
/usr/lib64/ruby/gems/1.8/gems/activerecord-3.2.3/lib/active_record/validations.rb:76:in `perform_validations'


The culprit seems to be the "save(false)" statement in that migration. I
seem to recall that this is a recent change in one of the Rails 3.x
versions. Not sure how you want to handle that, so no pull request.


Also, the stats page crashes, first because the swf assets are not
precompiled (pull request coming), and secondly on a routing error that
I have not yet looked at:

ActionController::RoutingError (No route matches
{:id=>"500", :action=>"tag", :controller=>"todos"}):


Kind regards,

Hans

Loading...