Re: Static asset packaging on Heroku

2010-06-07 Thread Bradley
ya I think the S3 option would be the best.  Heroku docs explicitly
say

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.

I'd rather not risk the possibility of a file being cleared out.

On Jun 6, 6:57 pm, Matthew Soldo m...@heroku.com wrote:
 Hi Bradley,

 In the SASS world this problem was solved by writing the compiled assets to
 the tmp directory and then modifying rack to serve the assets from there.
 You can check it out here:

 http://github.com/Papipo/hassle

 http://github.com/Papipo/hassleAnother really cool solution would be to
 modify your asset packager to write the files to S3, and then redirect the
 requests to JS and CSS files appropriately.

 Matt





 On Sun, Jun 6, 2010 at 3:11 PM, Bradley bradleyrobert...@gmail.com wrote:
  Safari crashed on my while posting this the first time so I hope it's
  not a dup.

  I'm just wondering what people are using for packaging/minifying
  static assets on heroku.  I just finished a project using Jammit which
  worked amazingly well, but Heroku's read-only filesystem would make
  the standard Jammit setup not work.  Also with a git deploy, from what
  I understand, if I pre-packaged these assets, I'd then need to add
  them into the repo, which is not really desirable.

  Has anyone used Jammit successfully on Heroku or do you have any other
  packing solutions for static assets?

  --
  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.comheroku%2bunsubscr...@googlegroups.com
  .
  For more options, visit this group at
 http://groups.google.com/group/heroku?hl=en.

 --
 Matthew Soldo
 Heroku, Inc

 (415) 323-0003http://www.linkedin.com/in/mattsoldo
 @mattsoldo

-- 
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: Static asset packaging on Heroku

2010-06-06 Thread Matthew Soldo
Hi Bradley,

In the SASS world this problem was solved by writing the compiled assets to
the tmp directory and then modifying rack to serve the assets from there.
You can check it out here:

http://github.com/Papipo/hassle

http://github.com/Papipo/hassleAnother really cool solution would be to
modify your asset packager to write the files to S3, and then redirect the
requests to JS and CSS files appropriately.

Matt


On Sun, Jun 6, 2010 at 3:11 PM, Bradley bradleyrobert...@gmail.com wrote:

 Safari crashed on my while posting this the first time so I hope it's
 not a dup.

 I'm just wondering what people are using for packaging/minifying
 static assets on heroku.  I just finished a project using Jammit which
 worked amazingly well, but Heroku's read-only filesystem would make
 the standard Jammit setup not work.  Also with a git deploy, from what
 I understand, if I pre-packaged these assets, I'd then need to add
 them into the repo, which is not really desirable.

 Has anyone used Jammit successfully on Heroku or do you have any other
 packing solutions for static assets?

 --
 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.comheroku%2bunsubscr...@googlegroups.com
 .
 For more options, visit this group at
 http://groups.google.com/group/heroku?hl=en.




-- 
Matthew Soldo
Heroku, Inc

(415) 323-0003
http://www.linkedin.com/in/mattsoldo
@mattsoldo

-- 
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.