From: will trillich
Here's our current dev-to-deploy approach -- we use mercurial and a
three-step staging process:
I think that it could be helpful to add a page to the Cat site that describe
the workflow for deployment because it is not clear which are the
possible/recommended
On 3/3/2011 1:58 AM, Octavian Rasnita orasnita-at-gmail.com |Catalyst/Allow to
home| wrote:
From: will trillich
Here's our current dev-to-deploy approach -- we use mercurial and a
three-step staging process:
I think that it could be helpful to add a page to the Cat site that
On Wed, Mar 2, 2011 at 12:43 AM, John M. Dlugosz wxju46g...@snkmail.com wrote:
As for reaching for templates in CSS: Sure, you can break common lines into
different tags so you only specify a color once:
#this, #that, div p .theother { color: x }
but that doesn't help making (say) a
On 2 Mar 2011, at 05:43, John M. Dlugosz wrote:
On 3/1/2011 9:58 AM, Bill Moseley moseley-at-hank.org |Catalyst/
Allow to home| wrote:
At build time I minimize and compress css and js (and images) and
combine
into single files grouped by page(s). They could be pre-processed
by TT
very
Hi,
On Wed, Mar 2, 2011 at 5:24 PM, Tomas Doran bobtf...@bobtfish.net wrote:
Installing to production servers via rsync / unison is insane, as there is
exactly no way of knowing what version the production server is on, with
what bugs...
Of course you can. You can include a file .version at
Here's our current dev-to-deploy approach -- we use mercurial and a
three-step staging process:
A) sandbox/dev server:
dev-server$ vi lib/*/blah/yadda
dev-server$ CATALYST_DEBUG=1 script/*_server.pl
test dev-server:3000 plenty -- lots of iterating, and then prep for
deploy-testing:
dev-server$
On Wed, Mar 2, 2011 at 5:35 PM, will trillich
will.trill...@serensoft.comwrote:
Here's our current dev-to-deploy approach -- we use mercurial and a
three-step staging process:
A) sandbox/dev server:
dev-server$ vi lib/*/blah/yadda
dev-server$ CATALYST_DEBUG=1 script/*_server.pl
test
On 2 Mar 2011, at 17:27, Pedro Melo wrote:
On Wed, Mar 2, 2011 at 5:24 PM, Tomas Doran bobtf...@bobtfish.net
wrote:
Installing to production servers via rsync / unison is insane, as
there is
exactly no way of knowing what version the production server is on,
with
what bugs...
Of course
On Tue, Mar 1, 2011 at 9:43 PM, John M. Dlugosz wxju46g...@snkmail.comwrote:
On 3/1/2011 9:58 AM, Bill Moseley moseley-at-hank.org |Catalyst/Allow to
home| wrote:
At build time I minimize and compress css and js (and images) and combine
into single files grouped by page(s). They could be
On 3/2/2011 11:24 AM, Tomas Doran bobtfish-at-bobtfish.net |Catalyst/Allow to
home| wrote:
Installing to production servers via rsync / unison is insane, as there is exactly no
way of knowing what version the production server is on, with what bugs... Which means
that all bug reports become
On 3/2/2011 11:27 AM, Pedro Melo melo-at-simplicidade.org |Catalyst/Allow to
home| wrote:
Of course you can. You can include a file .version at the root created
with 'git describe --always' .version before you rsync, and then
include it on your test reports.
Nice tip. Thanks.
Say I want to use TT in the .css, so (for example) I can name my colors and other
repeated content easily.
I'm assuming that I can define a Path of some kind on a rule to serve those. Any recipes
to share?
More critically, I want the browser to know that it doesn't have to keep re-fetching
That's only part of it. It should also answer status 304, and set headers to tell the
client not to even bother asking again any time soon.
On 3/1/2011 4:45 AM, Jorge Gonzalez jorge.gonzalez-at-daikon.es |Catalyst/Allow to home|
wrote:
So what you need then is a templating system which
Also see
http://wiki.catalystframework.org/wiki/adventcalendararticles/2007/11-Making_your_Catalyst_App_Cache-friendly
for
a neat approach to setting browser-cache expiry info.
On Tue, Mar 1, 2011 at 5:49 AM, John M. Dlugosz wxju46g...@snkmail.comwrote:
That's only part of it. It should also
On Tue, Mar 1, 2011 at 1:23 AM, John M. Dlugosz wxju46g...@snkmail.comwrote:
Say I want to use TT in the .css, so (for example) I can name my colors
and other repeated content easily.
I'm assuming that I can define a Path of some kind on a rule to serve
those. Any recipes to share?
More
On 3/1/2011 9:58 AM, Bill Moseley moseley-at-hank.org |Catalyst/Allow to home|
wrote:
At build time I minimize and compress css and js (and images) and combine
into single files grouped by page(s). They could be pre-processed by TT
very easily. The final file names include an MD5 of their
16 matches
Mail list logo
