As I understand sass_on_heroku or better hassle can be used to compile sass stylesheets to the /tmp folder on Heroku. I'm wondering what the findings are about using this approach.
I'm asking because of this mention in the Heroku docs. Especially the last sentence.
There are two directories that are writeable: ./tmp and ./log (under your application root). If you wish to drop a file temporarily for the duration of the request, you can write to a filename like #{RAILS_ROOT}/tmp/myfile_#{Process.pid}. There is no guarantee that this file will be there on subsequent requests (although it might be), so this should not be used for any kind of permanent storage.
> As I understand sass_on_heroku or better hassle can be used to compile > sass stylesheets to the /tmp folder on Heroku. I'm wondering what the > findings are about using this approach.
> I'm asking because of this mention in the Heroku docs. Especially the > last sentence.
> There are two directories that are writeable: ./tmp and ./log (under > your application root). If you wish to drop a file temporarily for the > duration of the request, you can write to a filename like > #{RAILS_ROOT}/tmp/myfile_#{Process.pid}. There is no guarantee that > this file will be there on subsequent requests (although it might be), > so this should not be used for any kind of permanent storage.
> Cheers, > Marcel
> -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to heroku@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscribe@googlegroups.com<heroku%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en.
I threw a quick app together to show how haml and sass can work on heroku, along with formtastic and a nice jquery dynamic styles changer here: http://mccaffrey-formtastic.heroku.com/
> As I understand sass_on_heroku or better hassle can be used to compile > sass stylesheets to the /tmp folder on Heroku. I'm wondering what the > findings are about using this approach.
> I'm asking because of this mention in the Heroku docs. Especially the > last sentence.
> There are two directories that are writeable: ./tmp and ./log (under > your application root). If you wish to drop a file temporarily for the > duration of the request, you can write to a filename like > #{RAILS_ROOT}/tmp/myfile_#{Process.pid}. There is no guarantee that > this file will be there on subsequent requests (although it might be), > so this should not be used for any kind of permanent storage.
> Cheers, > Marcel
> -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to heroku@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscribe@googlegroups.com<heroku%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en.
I couldn't find this information on the hassle github page. Do you know if Hassle is advised to used by Heroku?
The page and the information on Heroku website seem to be 'outdated'. Heroku.com still mentions sass_on_heroku but it's github page says it's deprecated for pedro's Hassle.
Cheers, Marcel
On Mar 26, 6:40 pm, Oren Teich <o...@heroku.com> wrote:
> hassle stores the stylesheets in varnish, cached for all dynos.
> Oren
> On Fri, Mar 26, 2010 at 6:30 AM, Marcel Overdijk > <marceloverd...@gmail.com>wrote:
> > As I understand sass_on_heroku or better hassle can be used to compile > > sass stylesheets to the /tmp folder on Heroku. I'm wondering what the > > findings are about using this approach.
> > I'm asking because of this mention in the Heroku docs. Especially the > > last sentence.
> > There are two directories that are writeable: ./tmp and ./log (under > > your application root). If you wish to drop a file temporarily for the > > duration of the request, you can write to a filename like > > #{RAILS_ROOT}/tmp/myfile_#{Process.pid}. There is no guarantee that > > this file will be there on subsequent requests (although it might be), > > so this should not be used for any kind of permanent storage.
> > Cheers, > > Marcel
> > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to heroku@googlegroups.com. > > To unsubscribe from this group, send email to > > heroku+unsubscribe@googlegroups.com<heroku%2Bunsubscribe@googlegroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/heroku?hl=en.
Locally it works but on Heroku server the stylesheet cannot be found.
I've used both = stylesheet_link_tag "application.css" <link href="/stylesheets/application.css" media="screen" rel="stylesheet" type="text/css" /> in my layout, but it just can't find /stylesheets/application.css
Note that when I'm running my app locally it writes the compiled css to ./public/stylesheets and not in ./tmp. Don't know if this should be the case either?
On Mar 26, 6:40 pm, Oren Teich <o...@heroku.com> wrote:
> hassle stores the stylesheets in varnish, cached for all dynos.
> Oren
> On Fri, Mar 26, 2010 at 6:30 AM, Marcel Overdijk > <marceloverd...@gmail.com>wrote:
> > As I understand sass_on_heroku or better hassle can be used to compile > > sass stylesheets to the /tmp folder on Heroku. I'm wondering what the > > findings are about using this approach.
> > I'm asking because of this mention in the Heroku docs. Especially the > > last sentence.
> > There are two directories that are writeable: ./tmp and ./log (under > > your application root). If you wish to drop a file temporarily for the > > duration of the request, you can write to a filename like > > #{RAILS_ROOT}/tmp/myfile_#{Process.pid}. There is no guarantee that > > this file will be there on subsequent requests (although it might be), > > so this should not be used for any kind of permanent storage.
> > Cheers, > > Marcel
> > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to heroku@googlegroups.com. > > To unsubscribe from this group, send email to > > heroku+unsubscribe@googlegroups.com<heroku%2Bunsubscribe@googlegroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/heroku?hl=en.
As long as ik keep sass templates in ./public/stylesheets/sass and include stylesheets from /stylesheets in html page everything works fine.
However I like to change the template location of the sass templates to ./app/stylesheets using Sass::Plugin.options[:template_location] = "./app/stylesheets". But when I do this it won't work anymore.
Next to that I would also change Sass::Plugin.options[:css_location] = "./public/stylesheets/compiled" So I can easily add this folder to .gitignore.
I'm wondering if this possible with the hassle plugin. Any help appreciated.
Cheers, Marcel
On Mar 26, 6:40 pm, Oren Teich <o...@heroku.com> wrote:
> hassle stores the stylesheets in varnish, cached for all dynos.
> Oren
> On Fri, Mar 26, 2010 at 6:30 AM, Marcel Overdijk > <marceloverd...@gmail.com>wrote:
> > As I understand sass_on_heroku or better hassle can be used to compile > > sass stylesheets to the /tmp folder on Heroku. I'm wondering what the > > findings are about using this approach.
> > I'm asking because of this mention in the Heroku docs. Especially the > > last sentence.
> > There are two directories that are writeable: ./tmp and ./log (under > > your application root). If you wish to drop a file temporarily for the > > duration of the request, you can write to a filename like > > #{RAILS_ROOT}/tmp/myfile_#{Process.pid}. There is no guarantee that > > this file will be there on subsequent requests (although it might be), > > so this should not be used for any kind of permanent storage.
> > Cheers, > > Marcel
> > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to heroku@googlegroups.com. > > To unsubscribe from this group, send email to > > heroku+unsubscribe@googlegroups.com<heroku%2Bunsubscribe@googlegroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/heroku?hl=en.
> I couldn't find this information on the hassle github page. > Do you know if Hassle is advised to used by Heroku?
> The page and the information on Heroku website seem to be 'outdated'. > Heroku.com still mentions sass_on_heroku but it's github page says > it's deprecated for pedro's Hassle.
> Cheers, > Marcel
> On Mar 26, 6:40 pm, Oren Teich <o...@heroku.com> wrote: > > hassle stores the stylesheets in varnish, cached for all dynos.
> > Oren
> > On Fri, Mar 26, 2010 at 6:30 AM, Marcel Overdijk > > <marceloverd...@gmail.com>wrote:
> > > As I understand sass_on_heroku or better hassle can be used to compile > > > sass stylesheets to the /tmp folder on Heroku. I'm wondering what the > > > findings are about using this approach.
> > > I'm asking because of this mention in the Heroku docs. Especially the > > > last sentence.
> > > There are two directories that are writeable: ./tmp and ./log (under > > > your application root). If you wish to drop a file temporarily for the > > > duration of the request, you can write to a filename like > > > #{RAILS_ROOT}/tmp/myfile_#{Process.pid}. There is no guarantee that > > > this file will be there on subsequent requests (although it might be), > > > so this should not be used for any kind of permanent storage.
> > > Cheers, > > > Marcel
> > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "Heroku" group. > > > To post to this group, send email to heroku@googlegroups.com. > > > To unsubscribe from this group, send email to > > > heroku+unsubscribe@googlegroups.com<heroku%2Bunsubscribe@googlegroups.com> > <heroku%2Bunsubscribe@googlegroups.com<heroku%252Bunsubscribe@googlegroups. com>
> -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to heroku@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscribe@googlegroups.com<heroku%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en.
> What's the confusion? As the github page says, sass_on_heroku is now > hassle. You should use that one. Which info on the heroku site is > outdated?
> Oren
> On Sat, Mar 27, 2010 at 5:50 AM, Marcel Overdijk > <marceloverd...@gmail.com>wrote:
> > Hi Oren,
> > I couldn't find this information on the hassle github page. > > Do you know if Hassle is advised to used by Heroku?
> > The page and the information on Heroku website seem to be 'outdated'. > > Heroku.com still mentions sass_on_heroku but it's github page says > > it's deprecated for pedro's Hassle.
> > Cheers, > > Marcel
> > On Mar 26, 6:40 pm, Oren Teich <o...@heroku.com> wrote: > > > hassle stores the stylesheets in varnish, cached for all dynos.
> > > Oren
> > > On Fri, Mar 26, 2010 at 6:30 AM, Marcel Overdijk > > > <marceloverd...@gmail.com>wrote:
> > > > As I understand sass_on_heroku or better hassle can be used to compile > > > > sass stylesheets to the /tmp folder on Heroku. I'm wondering what the > > > > findings are about using this approach.
> > > > I'm asking because of this mention in the Heroku docs. Especially the > > > > last sentence.
> > > > There are two directories that are writeable: ./tmp and ./log (under > > > > your application root). If you wish to drop a file temporarily for the > > > > duration of the request, you can write to a filename like > > > > #{RAILS_ROOT}/tmp/myfile_#{Process.pid}. There is no guarantee that > > > > this file will be there on subsequent requests (although it might be), > > > > so this should not be used for any kind of permanent storage.
> > > > Cheers, > > > > Marcel
> > > > -- > > > > You received this message because you are subscribed to the Google > > Groups > > > > "Heroku" group. > > > > To post to this group, send email to heroku@googlegroups.com. > > > > To unsubscribe from this group, send email to > > > > heroku+unsubscribe@googlegroups.com<heroku%2Bunsubscribe@googlegroups.com> > > <heroku%2Bunsubscribe@googlegroups.com<heroku%252Bunsubscribe@googlegroups. com>
> > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to heroku@googlegroups.com. > > To unsubscribe from this group, send email to > > heroku+unsubscribe@googlegroups.com<heroku%2Bunsubscribe@googlegroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/heroku?hl=en.
