Skip to content

How do I always use Cloudinary URLs when developing locally? #117

@theetrain

Description

@theetrain

Hello, thanks for building this plugin.

From reading the documentation, I understand that setting only_prod: false should always generate image tags with their cloudinary URL. However, when running Jekyll locally, my images appear like this:

<img src="http://0.0.0.0:4000/nature-mountains.jpg" 
  srcset="https://res.cloudinary.com/etrain/image/fetch/c_limit,f_auto,q_auto,w_320/http://0.0.0.0:4000/nature-mountains.jpg 320w, 
  https://res.cloudinary.com/etrain/image/fetch/c_limit,f_auto,q_auto,w_365/http://0.0.0.0:4000/nature-mountains.jpg 365w,
  https://res.cloudinary.com/etrain/image/fetch/c_limit,f_auto,q_auto,w_410/http://0.0.0.0:4000/nature-mountains.jpg 410w, 
  https://res.cloudinary.com/etrain/image/fetch/c_limit,f_auto,q_auto,w_455/http://0.0.0.0:4000/nature-mountains.jpg 455w, 
  https://res.cloudinary.com/etrain/image/fetch/c_limit,f_auto,q_auto,w_500/http://0.0.0.0:4000/nature-mountains.jpg 500w" 
  sizes="100vw" alt="test" crossorigin="anonymous" />

How do I not use localhost|http://0.0.0.0 and only use production URLs when developing locally? Once I understand this better, I would be happy to make a PR to the documentation.

I'm using:

  • jekyll-cloudinary v1.14.1
  • jekyll v4.2.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions