Date: Tue, 28 Aug 2012 11:25:39 -0700 (PDT)
From: si...@polkaspots.com
To: whenever-gem@googlegroups.com
Message-Id: <6a1a0b47-5223-4b23-af77-a242407fdfd9@googlegroups.com>
Subject: Creating Schedule Per Record
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_618_25663137.1346178339671"

------=_Part_618_25663137.1346178339671
Content-Type: multipart/alternative; 
	boundary="----=_Part_619_11679296.1346178339671"

------=_Part_619_11679296.1346178339671
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

We've been using whenever successfully for a while now but have run up 
against a slightly strange requirement.

Our Rails 3.2 app has several thousand 'customers' each with their own 
cron. The values for each cron are stored in the client's model and the 
crontab rendered as a text file. On boot, each client connects and 
downloads their own file. It's pretty cumbersome right now.

We were thinking to wheneverize this process as your logic and structure if 
far superior and easy to understand.

Have had a look at the various output options but we don't really want to 
render to a file. 

Do you think it would be possible for whenever to generate the file on the 
fly, each time the client calls in? The values would still be stored in the 
db.

Is there a better way to achieve this?

------=_Part_619_11679296.1346178339671
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

We've been using whenever successfully for a while now but have run up against a slightly strange requirement.<div><br></div><div>Our Rails 3.2 app has several thousand 'customers' each with their own cron. The values for each cron are stored in the client's model and the crontab rendered as a text file. On boot, each client connects and downloads their own file. It's pretty cumbersome right now.</div><div><br></div><div>We were thinking to wheneverize this process as your logic and structure if far superior and easy to understand.</div><div><br></div><div>Have had a look at the various output options but we don't really want to render to a file.&nbsp;</div><div><br></div><div>Do you think it would be possible for whenever to generate the file on the fly, each time the client calls in? The values would still be stored in the db.</div><div><br></div><div>Is there a better way to achieve this?</div>
------=_Part_619_11679296.1346178339671--

------=_Part_618_25663137.1346178339671--