Re: [Radiant] Unicorn and/or Thin and assets - not displaying in production

390 views
Skip to first unread message

Jim Gay

unread,
Jan 9, 2013, 5:15:50 AM1/9/13
to radia...@googlegroups.com
config.assets.compile is a Rails 3 feature and Radiant is currently on Rails 2
Can you give any more details about this?
What URLs do you have and what should they be?

On Sun, Jan 6, 2013 at 12:26 AM, Lou Brothers <l...@loubrothers.com> wrote:
> I've recently migrated my site to a host that doesn't like Mongrel. So I'm
> trying out Unicorn and Thin. I've also moved all of my assets within the app
> (from my Public folder).
>
> Using Webrick I can see all assets displayed on the site appropriately. But
> using Unicorn and Thin I cannot:
> bundle exec unicorn_rails -p 3000 -o 0.0.0.0 -E production
>
> The links are working appropriately (in that they're resolving to what they
> did with Webrick) but they're invalid when I follow them through to Radiant.
>
> The tips I've seen online about altering production.rb with
> config.assets.compile=true don't seem to be working (I get: undefined method
> `assets').
>
> Help, please.
>
>



--
Write intention revealing code #=> http://www.clean-ruby.com

Jim Gay
Saturn Flyer LLC
571-403-0338

Lou Brothers

unread,
Jan 9, 2013, 11:11:59 AM1/9/13
to radia...@googlegroups.com
Thanks for offering assistance. I won't be able to reply again until the weekend when I'm in front of my development machine. 

Lou

Lou Brothers

unread,
Jan 11, 2013, 8:23:54 PM1/11/13
to radia...@googlegroups.com
A View Source on my site shows that assets are resolving as: /system/assets/8/original/20100314-logo.png.

Going to 0.0.0.0:3000/system/assets/8/original/20100314-logo.png shows a Radiant CMS Page Not Found.  Viewing the Assets tab shows broken links for every previously uploaded image (uploaded when I was running Webrick locally).  I regenerated, reuploaded the item, and deleted/reuploaded the item. None worked.  On regeneration Terminal stated: 
   **** Warning: considering '0000000000 XXXXX n' as a free entry.

   **** This file had errors that were repaired or ignored.
   **** The file was produced by: 
   **** >>>> Mac OS X 10.4.9 Quartz PDFContext <<<<
   **** Please notify the author of the software that produced this
   **** file that it does not conform to Adobe's published PDF
   **** specification.

Again, the files worked fine when run from script/server -e production.  Launching as this again and visiting assets shows them just fine and the site works as expected. 

Running rake paperclip:refresh CLASS=Attachment RAILS_ENV=production from the command line gives the same warning.  DB is Sqlite3.

Adam Waterson

unread,
Apr 30, 2013, 10:39:02 AM4/30/13
to radia...@googlegroups.com
Upgrading to 1.1.3 but language redirect from .9 now throws an error. What are people using for Geoip to get visitors to the proper language?

Thanks!

Sent from my iPhone.


On 29 apr. 2013, at 15:25, "Cheng Guang-Nan" <che...@gmail.com> wrote:

I found that it's thin failed the use the right adaptor. Use `thin -A rails` to fix that.


On Sunday, January 6, 2013 1:26:03 PM UTC+8, Lou Brothers wrote:
I've recently migrated my site to a host that doesn't like Mongrel. So I'm trying out Unicorn and Thin. I've also moved all of my assets within the app (from my Public folder).  

Using Webrick I can see all assets displayed on the site appropriately. But using Unicorn and Thin I cannot:
     bundle exec unicorn_rails -p 3000 -o 0.0.0.0 -E production

The links are working appropriately (in that they're resolving to what they did with Webrick) but they're invalid when I follow them through to Radiant. 

The tips I've seen online about altering production.rb with config.assets.compile=true don't seem to be working (I get: undefined method `assets').

Help, please.


--
 
---
You received this message because you are subscribed to the Google Groups "Radiant CMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to radiantcms+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply all
Reply to author
Forward
0 new messages