similar to: MemCacheStore; memcached-problem on freeze_edge (export version 3811)

When pass :cache param to ActionDispatch::Session::MemCacheStore, it should be removed from options, otherwise it remains "published". This violates the OOP encapsulation principle. I created a LH ticket with a patch http://bit.ly/cGDaWs Luca -- lucaguidi.com twitter.com/jodosha -- You received this message because you are subscribed to the Google Groups "Ruby on Rails:

I installed TortoiseSVN, created a local repository at c:/instantrails/SVNRepository. I have an app that I want to put into SVN and also do a freeze_edge for, but I''m not sure how. I ran command ''rake freeze_edge'' and got the error: ERROR: Must have subversion (svn) available in the PATH to lock this application to Edge Rails rake aborted! Any advice or links to a

How do i use "rake freeze_edge" over a proxy? "rake freeze_edge -p http://...." doesnt work THanks Chris -- Posted via http://www.ruby-forum.com/.

I got these messages running ''rake freeze_edge'' in the application directory rake aborted! Don''t know how to build task ''freeze_edge'' What gives ? TIA -- Posted via http://www.ruby-forum.com/.

Anyone know what''s going on here? Every time I rune rake freeze_gems it complains that I don''t have rails installed. freeze_edge won''t work either. catalog1# rake freeze_gems (in /usr/local/cart/ast/rails) rm -rf vendor/rails mkdir -p vendor/rails Unpacked gem: ''actionpack-1.9.1'' Unpacked gem: ''activerecord-1.12.2'' Unpacked gem:

(from http://pastebin.ca/44831) from a rails 1.0 app i did rake freeze_edge and rake rails:update. that went fine. when i go to the front page of my rails app I get wrong number of arguments (2 for 3) /var/www/somehost.net/site/public/../config/../vendor/rails/railties/lib/dispatcher.rb:63:in `failsafe_response''

Hi - Just downloaded and installed the memcache-client and cached_model gems and am trying to test it out on a development setup. I added this to my environment/development.rb CACHE = MemCache.new :c_threshold => 10_000, :compression => true, :debug => true, :namespace => ''eztrip'',

Courtesy of The Robot Co-op. $ yes | sudo gem install cached_model Or, you can download cached_model and memcache-client (our zippy-fast memcache library, required) from: http://rubyforge.org/frs/?group_id=1266 I don''t have the README posted for making cached_model work online yet, so here it is: = CachedModel Rubyforge Project: http://rubyforge.org/projects/rctools/ == About

The new version of cached_model features bug fixes and tests! Bugs fixed: Updating a model no longer stores associations into the cache. This could cause strange, hard-to-debug bugs when an invalid set of assocations was retrieved along with a cached model. Reloading a model refreshes the cache. When CachedModel::find can''t understand query params and a single result is

Could someone please elaborate on the technical differences and practical impact of whether choosing memory-based tables in MySQL or using memcached. I got this far on my own: It seems that MySQL uses the NDB engine for transaction-safe memory access in a cluster. the memory storage engine seems to be faster but not synchronizable by any means in a cluster. memcached seems to be ultimately fast

Lighthouse ticket: https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/4452 I have recently been working on some gems that utilize ActiveSupport::Cache and ran into some issues with the different implementations handling the same functionality differently. One of the issues was that I couldn''t rely on expiring entries with the :expires_in option. MemCacheStore takes this

Hi all - I am trying to get rails to use memcache for sessions and fragment caching. I''d also like to use the same connection for general caching of this and that. I''m following the instructions here: http://wiki.rubyonrails.com/rails/pages/HowtoChangeSessionStore and hitting a brick wall. I''m using the new memcache-client since from what I''ve read

Dear R users, sorry for this general email and I am sure it has been asked way too many times. IT departements in big companies only want to support the big standards. Whatever big standards means apart from being expensive. We are in the process of trying to get a risk management project for a big conservative company in Germany. As part of the project we would use R to run simulations,

Hi, I''m trying to use mem_cache_store for sessions. I have installed the server and the gem and have added the following to my config/environment.rb: >>>>>>>>>>>>>>>>>>>>>>>>> memcache_options = { :c_threshold => 10_000, :compression => true, :debug => false, :namespace =>

I try to switch my application from Rails 2.2.2 to Rails 2.3.3. In namespace :admin I have a resource-based controller. See controller class Admin::OSystemsController < Admin::BaseController def index ....... end def edit ......... end def update .......... end end Resource is added to routes.rb like map.namespace :admin do |admin| ............ admin.resources :o_systems,

> > > Now, under CentOS 7, I see we have two files controlling memcached under > the new sysctl system. At least, using sysctl is new to me! > > I see we have this file: > > [root at web1:~] #cat /usr/lib/systemd/system/memcached.service > [Unit] > Description=Memcached > Before=httpd.service > After=network.target > > [Service] > Type=simple >

Hi all. I am thinking about installing memcached with replication, I've found http://sourceforge.net/projects/repcached/files/repcached/2.2.1-1.2.8/ but it is for 1.2.8, and for Centos 6.3 memcached is in version 1.4.4. I do not want to use client side "replication" (writing to two memcached nodes at the same time) and haven't found other solution. Are there any good, protocol

I have rails 1.0 and I cannot install rails-1.1 system-wide. However, I can freeze_edge (but just once because of svn 1.1.4 on Debian). Under this scenario, how can I create brand new rails-1.1 apps? I know how to freeze_edge *existing* rails-1.0 apps but that process seems to be imperfect because the script/about command and /rails/info/properties URL do not work after freezing to 1.1.0

Hi, Is there someone successfully running memcached-1.4.1 on Centos 4 with centosplus php? I'm trying to use memcached under Centos 4. I can set values fine but 'get' returns: [root at rakosnicek eshop]# php d.php PHP Warning: Memcached::get(): bad type specifier while parsing parameters in /var/www/d.php on line 6 NULL string(7) "SUCCESS" array(1) {

Hi. I am using Capistrano for my webapp and after deploy I need to restart memcached service. I am trying to do it with sudo "/etc/init.d/memcached restart" But it does not do it, even if memcached service existed - after deployment memcached service is off. I did some researching and added run "sleep 40" right after sudo command and found that service process existed