On Sun, Mar 24, 2013 at 12:04 AM, tamouse mailing lists
wrote:
> If you do decide to go that route, DJ can handle the requeuing itself,
> not needing anything else. It's just a bit more configuration and
> such.
As much as I've seen you ask people not to top post, I'm going to
remind you to trim
> On Sat, Mar 23, 2013 at 5:37 PM, tamouse mailing lists
> wrote:
>>
>> On Sat, Mar 23, 2013 at 1:20 PM, Jodi Showers wrote:
>> > I'm just about to scale to a second app server - so good timing
>> >
>> > in which ways did you find cron to be a poor choice ? on a single server
>> > they meet our n
On Sat, Mar 23, 2013 at 4:46 PM, Colin Law wrote:
> On 23 March 2013 21:37, tamouse mailing lists wrote:
>> ...
>> The primary issue when you bring in multiple servers is
>> synchronization of the workers. Cron can't do that, as it only knows
>> about one server. Having something that workers can
yes - I know - I use DJ presently
my question was about what advantages you see with clockwork over cron -
other than syntax I don't see any advantages
now if the schedule was stored in the db, and I could run multiple
clockworks on each server there would some inherent scheduling failover (DJ
al
On 23 March 2013 21:37, tamouse mailing lists wrote:
> ...
> The primary issue when you bring in multiple servers is
> synchronization of the workers. Cron can't do that, as it only knows
> about one server. Having something that workers can distribute over
> requires something more sophisticated.
On Sat, Mar 23, 2013 at 1:20 PM, Jodi Showers wrote:
> I'm just about to scale to a second app server - so good timing
>
> in which ways did you find cron to be a poor choice ? on a single server
> they meet our needs nicely
>
> you'd only run one clock instance per cluster - so much like cron (ie
I'm just about to scale to a second app server - so good timing
in which ways did you find cron to be a poor choice ? on a single server
they meet our needs nicely
you'd only run one clock instance per cluster - so much like cron (ie. no
interserver clock scheduling). Have you tried using clock d
Please bottom post (appending). It makes responses easier to find.
On Sat, Mar 23, 2013 at 10:32 AM, Jodi Showers wrote:
> that is a good thinking, just like normalization - then comes a time to
> denormalize
>
> we have millions of visitors per month - and about 50 asynch processes -
> having on
On 23 March 2013 17:19, Tommy Pollák wrote:
> Thanks! Worked perfectly. Really astonishing fast help!
Glad to be of help
Colin
>
>
> On Saturday, 23 March 2013 16:59:36 UTC+1, Tommy Pollák wrote:
>>
>> When trying to generate a new Rails application (to test email posting) I
>> receive the mess
Thanks! Worked perfectly. Really astonishing fast help!
On Saturday, 23 March 2013 16:59:36 UTC+1, Tommy Pollák wrote:
>
> When trying to generate a new Rails application (to test email posting) I
> receive the message:
>
> Installing sqlite3 (1.3.7) with native extensions
> Gem::Installer::Exte
On 23 March 2013 16:10, Tommy Pollák wrote:
> Sorry, forget to mention this, Ubuntu 12.04.
sudo apt-get install libsqlite3-dev sqlite3
Colin
>
> On Saturday, 23 March 2013 17:04:29 UTC+1, Colin Law wrote:
>>
>> On 23 March 2013 15:59, Tommy Pollák wrote:
>> > When trying to generate a new Rail
Sorry, forget to mention this, Ubuntu 12.04.
On Saturday, 23 March 2013 17:04:29 UTC+1, Colin Law wrote:
>
> On 23 March 2013 15:59, Tommy Pollák
> >
> wrote:
> > When trying to generate a new Rails application (to test email posting)
> I
> > receive the message:
> >
> > Installing sqlite3
On 23 March 2013 15:59, Tommy Pollák wrote:
> When trying to generate a new Rails application (to test email posting) I
> receive the message:
>
> Installing sqlite3 (1.3.7) with native extensions
> Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native
> extension.
>
> /ho
When trying to generate a new Rails application (to test email posting) I
receive the message:
Installing sqlite3 (1.3.7) with native extensions
Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native
extension.
/home/*/.rbenv/versions/1.9.3-p286/bin/ruby extconf.rb
che
that is a good thinking, just like normalization - then comes a time to
denormalize
we have millions of visitors per month - and about 50 asynch processes -
having one rails process deal with all those asynchs rather than one per is
not helpful in any way
using a best practice such as my approach
On 23 March 2013 15:15, Jodi Showers wrote:
> for regularly scheduled jobs, I use a mixture of cron (to create a delayed
> job), and the delayed_job itself
>
> the crontab instance is very light, just a small (non-rails) rb script to
> insert the delayed_job in the delayed_jobs table
>
> then the
On Friday, 22 March 2013 09:56:23 UTC-4, Paulo Ribeiro wrote:
>
> Hey guys. Im looking to make a model with fewer included modules from
> ActiveRecord. Basically, i want to include only the modules so it can work
> fine inside rails and with the methods to access the database.
>
> I tried to do
for regularly scheduled jobs, I use a mixture of cron (to create a delayed
job), and the delayed_job itself
the crontab instance is very light, just a small (non-rails) rb script to
insert the delayed_job in the delayed_jobs table
then the delayed_job instance will pickup the job and run it
in y
On 23 March 2013 14:10, Barry wrote:
> Hi, I faced such issue - my app should run some delayed method.
> For example, I have Test model, which User can create. But to other users it
> should be visible only if it has :saved value in status attribute, which is
> assigned with special button.
> I wa
Hi, I faced such issue - my app should run some delayed method.
For example, I have Test model, which User can create. But to other users
it should be visible only if it has :saved value in status attribute, which
is assigned with special button.
I want to delete all tests, which remained unpubli
On Friday, March 22, 2013 2:20:09 AM UTC+2, jle...@socit.co.uk wrote:
>
> So I have a rails 3.2.11 Example app that exhibits some simple core use
> cases and I am starting again under rails 4.0.0.beta1
>
> **
> <%= f.label r %>
> <%= f.fields_for :interactions, s.initialized_in
Enviado desde mi Blackberry® 3G de Iusacell.
-Original Message-
From: tamouse mailing lists
Sender: rubyonrails-talk@googlegroups.com
Date: Fri, 22 Mar 2013 23:49:56
To:
Reply-To: rubyonrails-talk@googlegroups.com
Subject: Re: [Rails] Re: Trouble after cloning my app from Github
On Fr
22 matches
Mail list logo
