Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Using Ruby on Rails 5.0.1 on Ubuntu 16.04 One Click Install. Builder cannot be found but is being used? Question Question
Using Rails 16.04 One-Click-App (no usage/config documentation) *Errors Question Question

Question

Ubuntu 16.04 Rails one click images 404 not found.

Posted May 25, 2017 3.7k views
Ruby on RailsDigitalOcean 1-Click Apps MarketplaceUbuntu 16.04

Images that exist in my repo and display fine in development are 404 not found in production.

I have confirmed the images are present on the production server in root/assets/images/<subdir>/. The images are not accessible in any subpath I have tried typing into the broswer, unlike locally, where I can get a lone image to display in the browser by adding /<subdir>/<imagename> to the url.

I have added the following lines to my /etc/nginx/nginx.conf:
server {
root /home/rails/<myproj>;

        location /images/ {
        root /home/rails/<myproj>/app/assets;
    }
    }

No change. I manually precompiled assets on the server with no errors.

My /config/environments/production.rb has the line:
config.servestaticfiles = ENV[‘RAILSSERVESTATIC_FILES’].present?

and the rails environment RAILSSERVESTATIC_FILES is set to true.

How can I make my images locatable in my production site?

Add a comment
jcspampinato
By:
jcspampinato

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Using Ruby on Rails 5.0.1 on Ubuntu 16.04 One Click Install. Builder cannot be found but is being used? Question Question
Using Rails 16.04 One-Click-App (no usage/config documentation) *Errors Question Question

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
2 answers
UncleJumper May 26, 2017

Hi!

If you are referring to these images from your app, then you need to use image_path in your code, instead of direct link to the image

Docs http://api.rubyonrails.org/classes/ActionView/Helpers/AssetUrlHelper.html

Regards,
Sergey

Reply Report
  • jcspampinato May 30, 2017

    Thanks Sergey. However, as I said in my post, these images and references to them load fine in my development environment. I don’t think the problem is an incorrect path or helper.

    Reply Report
    • UncleJumper June 1, 2017

      All the images will be available by their real name only in case they are located in app/public folder. It’s related to development and production environments.
      But in case of production and assets pipeline, you need to use image_path. Your images has a different names if they are in assets pipeline.

      Reply Report
jtittle1 May 25, 2017

@jcspampinato

If you’re server block only consists of:

server {
    root /home/rails/<myproj>;

    location /images/ {
        root /home/rails/<myproj>/app/assets;
    }
}

The server block really isn’t complete. You can take a look at the error logs for NGINX to see what is or may be causing the issue by running:

tail -20 /var/log/nginx/error.log

If you’ll paste the output of that command to a code block using the </> icon, we can see if there’s a bit of information there that we can use.

Generally though, when it comes to server blocks, you’d have something that looks more like this:

server {
    listen 80;
    server_name domain.com www.domain.com;

    root /home/rails/<myproj>;

    location /images {
        root /home/rails/<myproj>/app/assets;
    }
}

That’s very basic and NGINX would only handle /images for you in this case.

Reply Report

Related

Looking for something else?

Ask a new question Search for more help