similar to: --dry-run reliability ?

Dear developers, In the rsync's manpage, there is a line describing the "archive mode" option: -a, --archive archive mode; equals -rlptgoD (no -H,-A,-X) Archive mode means that all data is backed up sensibly while the same doesn't apply for all metadata (hence the mentioned -H, -A and -X options). There is another similar "special file system option" as

Hi all! I've got a machine setup to be an "RSYNC Server", i.e. running rsync in daemon mode waiting for connections from various other machines on my network. This machine is running Debian Sarge and rsync 2.6.3. For the past several days, I've been getting notices like this in my backup logs: ============================================================================ =====

https://bugzilla.samba.org/show_bug.cgi?id=8273 Summary: -a doesn't do -HAX Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: Dave at Yost.com QAContact: rsync-qa at

Hello everyone! Ive been on rails for the last month or so and really enjoyed this framework. However its very hard to find documentation on how to do things right! For example every beginner after a while realizes that having similar CRUD actions in every controller and views for them is not DRY at all! Few days ago I found http://dereksivers.com/rails-shared-controller.html I quite like his

I tend to write a fresh description block for every change in the parameters for that specific action, because I hate conditionals in the example describtion, e.g.: describe SomeController, "handling GET /path/with/param/3" do it "should do this" it "should not do this if" it "should still do that in both cases" end Seperate description blocks keep

I''ve got 8 scaffolds, each one can be considered an ''item'', such as a blog, photo, etc. Using login_engine and user_engine, I list all blogs belonging to a user by saying: @user=session[:user] @blogs=@user.blogs.find(:all) but then let''s say I want to create an option where I want to slice it differently: @user=session[:user] if @someOption ==1

Why select_date and select_date? I dont understand why having both (backward compat?). I also look that their source are different, one use the InstanceTag and others calls 3 select_(year, month, day) functions.

Given the case of validating the presence of an attribute and then performing other tests on said attribute, how do you go about not having to check for nil in the other tests? Example: validates_presence_of :start_date, :end_date validate :validate_start_date_before_end_date def validate_start_date_before_end_date # without this check an exception will be thrown on access to the

Sorry, search is down on the forum, so I don''t know if this has been posted elsewhere. I have some config variables that I want to have set in all environments, and overridden in production. What I want to do is put this in my config/environment.rb SOME_CONFIG = 555 And then override it in config/environments/production.rb as: SOME_CONFIG = 333 Problem is, using constants I

I have a heap of fill-out-form/send-website-operator-mail/send-user-confirmation types of forms. It''s daunting when you think about how many files it takes to do this. I''m not coming up with an obvious "Rails" way to pull it off, so I thought it''d be good to know if anyone else has worked through this (7 per form!). models/ my_form_data.rb

In an attempt to provide a gracefully degradable link_to_remote, I repeat myself every time: <%= link_to_remote(''Signup'', {:url => {:controller => ''user'', :action => ''signup''}}, {:href => url_for(:controller => ''user'', :action => ''signup'')}) %> Looked around the RDoc &

Here''s what I''ve got: <% @fields.each do |field_name| %> <tr> <td> <%= field_name.humanize %> </td> <td> <% unless field_name =~ /_id$/ %> <%= form.text_field field_name, :size => 40 %> <% else %> <%= select(:vendor, field_name, State.find(:all, :order

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, A few months ago someone posted a message about specifying validates_* constraints on a per-attribute basis. I just created a small plugin that allows you to do this. Here''s an example from one of my models: class Country < ActiveRecord::Base attribute :name, :string do |a| a.validates_length :within =>

I need to pull user preferences on every page load of every controller and action in my app. I do this like so: @user = User.find(@session[''user''].id) @prefs = @user.prefs And it works fine in the action of one of my controllers, but I certainly don''t want to plunk it in every instance. Where do you normally put something like this? I tried putting it in the

Hello everyone, I''ve got several different user roles (i.e. admin, user, guest, ...) and have set up a bunch of controllers for each user role. I''m trying to set up some sort of validation that the user accessing e.g. the admin/subjects controller has the ''admin'' role. The brute force way to do this would be something like: - for each controller, put in

I have a test/fixtures/users.yml like so: apa: id: 1 username: apa [...] created_at: <%=Time.now.strftime("%Y-%m-%d %H:%M:%S")%> updated_at: <%=Time.now.strftime("%Y-%m-%d %H:%M:%S")%> I don''t like how I''m repeating myself with the strftime bit. Is there some shorter Time method to format time for a (MySQL) datetime field that

What are some good ways of doing validation with AJAX in Rails (with Prototype/Scriptaculous)? I have some Ajax.InPlaceEditors, and I would like the page with the editors on it to display errors if the data given is e.g. too short, too long, wrong format... Ideally, this should be DRY in regard to the validators. A related question: is there any way of DRY between the database table field

Hi all, I have defined the following method in both application.rb and application_helper.rb: def still_logged_in? !session[:user_id].nil? end This method is called in a before_filter in my application.rb, as well as in my layout/application.rhtml and view/user/login.rhtml (for showing a login / logout button, etc.) I had to put it both places, otherwise I would get an

I need a constant, X, to be known in a jQuery script In an .rb file in Rails ins some css/SASS How can I get this constant known in all three places? -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to

Hey all, Anybody use the --dry-run command line option? I''m planning to deprecate it if nobody has a compelling reason to keep it. Please post your comments in the ticket: https://rspec.lighthouseapp.com/projects/5645-rspec/tickets/781-deprecate-dry-run Thanks, David