Re: Sass_on_heroku compiled css shows line number

[Karl]

On Jan 12, 12:53 pm, John McCaffrey  wrote:
> I don't know if you are referring to a different plugin, but I'm using the
> one mentioned on the heroku 
> bloghttp://blog.heroku.com/archives/2009/8/18/heroku_sass/

Yup, that's the one I'm using.

> I put together a
> quick demo to show how awesome sass, haml, and formtastic are, so some
> people on my team could start 'drinking the koolaid' with me!
>
> http://mccaffrey-formtastic.heroku.com/
>
> my application.sass includes these
>
> @import scaffold.sass
> @import formtastic_base.sass
> @import skintastic.sass
>
> but the final compiled css doesn't have any line numbers or unexpected
> artifacts

I have to agree with you, it doesn't have any line numbers.

I am using compass... wonder if that is having an effect on the
generated css.

John, are you seeing the line numbers when running under development
environment? You should.
-- 
You received this message because you are subscribed to the Google Groups 
"Heroku" group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to 
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en.

Re: Sass_on_heroku compiled css shows line number

[John McCaffrey]

I don't know if you are referring to a different plugin, but I'm using the
one mentioned on the heroku blog
http://blog.heroku.com/archives/2009/8/18/heroku_sass/

I put together a
quick demo to show how awesome sass, haml, and formtastic are, so some
people on my team could start 'drinking the koolaid' with me!

http://mccaffrey-formtastic.heroku.com/

my application.sass includes these

@import scaffold.sass
@import formtastic_base.sass
@import skintastic.sass

but the final compiled css doesn't have any line numbers or unexpected
artifacts



On Mon, Jan 11, 2010 at 11:10 AM, Karl  wrote:

> Just noticed this today, using sass_on_heroku when I look at the
> generated css, it still contains line numbers.
>
>  /* line 16, ../../app/stylesheets/partials/_base.sass */
>  .spacer-40 { height: 40px; }
>
> I tried the following with no effect:
>Sass::Plugin.options[:style] = :compact
>Sass::Plugin.options[:line_numbers] = false
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Heroku" group.
> To post to this group, send email to her...@googlegroups.com.
> To unsubscribe from this group, send email to
> heroku+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/heroku?hl=en.
>
>
>
>


-- 
-John
-- 

You received this message because you are subscribed to the Google Groups "Heroku" group.

To post to this group, send email to her...@googlegroups.com.

To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/heroku?hl=en.

Re: error installing heroku gem (ruby 1.9 / mac os x)

[dan]

gem is installing correctly on my system now

sudo gem install heroku
Successfully installed mime-types-1.16
Successfully installed rest-client-1.2.0
Successfully installed heroku-1.6.4
Successfully installed configuration-1.1.0
4 gems installed
Installing ri documentation for mime-types-1.16...
Installing ri documentation for rest-client-1.2.0...
Installing ri documentation for heroku-1.6.4...
Installing ri documentation for configuration-1.1.0...
Updating class cache with 2950 classes...
Installing RDoc documentation for mime-types-1.16...
Installing RDoc documentation for rest-client-1.2.0...
Installing RDoc documentation for heroku-1.6.4...
Installing RDoc documentation for configuration-1.1.0...


thanks!
-- 
You received this message because you are subscribed to the Google Groups 
"Heroku" group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to 
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en.

Re: Continuous deployment using heroku

[Bradley]

Right now I'm using Hudson to manage this.  I have a devel, staging
and production environment (all separate apps on heroku)  Google
"heroku multiple environments" for more information.

I then have hudson monitor different branches, so when I push to my
master branch (devel) it runs its tests and, assuming all is good push
to heroku.  When we're ready for a release I merge to staging and
push.  Hudson pulls, tests, then deploys to Heroku staging.  Run some
manual checks to make sure all is good.

Assuming it is, merge to production and push, Hudson pulls, tests and
pushes to Production if all's good.  I have my testing/staging envs
using the same DB at the moment, might split them all into their own
DB at some point.

All of this is supported with Heroku's current features.

On Jan 11, 9:22 am, Alex  wrote:
> Hi everyone, This is just a thought but it would be great to get some
> feedback, see how useful this could be.
>
> Is it feasible to allow individual dynos to be given different code to
> run?
> Read below for more information: It would awesome if we could supply a
> couple of our dynos with new code and monitor them for problems (while
> they run in production, with our normal database).
>
> From what I've seen, we have a lot of different ways to set up
> different working environments, staging apps, testing apps etc. but
> these all end up with separate apps using separate databases. We can't
> get our users to actually use the staging app for instance.
>
> Continuous deployment 
> -http://www.startuplessonslearned.com/2009/06/why-continuous-deploymen...
> - is a simple idea.
>
> Code is checked in to the master branch, or whatever the release
> branch is. That code gets tested and pushed to a small chunk of your
> server instances (this assumes multiple servers, or in heroku's case,
> multiple dynos).
> Those instances are monitored, using whatever monitoring system you
> want and if no problems occur, the new code is pushed out even more.
> More monitoring. Code is then pushed to the whole system.
> If at any point something goes wrong, the new code is rolled back and
> a developer has to take a look before you can deploy again.
>
> This isn't something I'd expect Heroku to produce, but with some
> support tools, maybe we can manage it for ourselves?
-- 
You received this message because you are subscribed to the Google Groups 
"Heroku" group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to 
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en.