Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-standard folder structure — error when navigating to /admin #451

Closed
Organikk opened this issue Feb 28, 2018 · 2 comments
Closed

Non-standard folder structure — error when navigating to /admin #451

Organikk opened this issue Feb 28, 2018 · 2 comments

Comments

@Organikk
Copy link

Description:

I'm getting an error when navigating to the jekyll-admin interface /admin

I have a non-standard Jekyll folder structure:

.
├── Gemfile
├── Gemfile.lock
├── Makefile
├── _config.yml
├── _config_prod.yml
├── docker-compose.yml
├── app
│   ├── jekyll source files
└── web
    └── compiled site...

Tell us a bit about yourself:

  • Version of JekyllAdmin I'm using: 0.7.0
  • Version of Jekyll I'm using: 3.7.3
  • Version of NodeJS I'm using: v9.4.0
  • Operating System: OS X
  • Browser: Chrome

Steps to reproduce:

Set up the directory structure like I mentioned above, serve it, and navigate to /admin

I expected the following:

I expected to see the jekyll-admin interface

But got the following, instead:

Configuration file: /srv/jekyll/_config.yml
            Source: app
       Destination: web
 Incremental build: disabled. Enable with --incremental
      Generating... 
                    done in 2.661 seconds.
 Auto-regeneration: enabled for 'app'
  JekyllAdmin mode: production
    Server address: http://0.0.0.0:4000/
  Server running... press ctrl-c to stop.
Configuration file: none
Configuration file: none
2018-02-28 11:22:53 - Errno::ENOENT - No such file or directory @ rb_sysopen - /srv/jekyll/app/_config.yml:
/usr/local/bundle/gems/jekyll-admin-0.7.0/lib/jekyll-admin/server/configuration.rb:36:in `read'
/usr/local/bundle/gems/jekyll-admin-0.7.0/lib/jekyll-admin/server/configuration.rb:36:in `raw_configuration'
/usr/local/bundle/gems/jekyll-admin-0.7.0/lib/jekyll-admin/server/configuration.rb:7:in `block (2 levels) in <class:Server>'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:1611:in `call'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:1611:in `block in compile!'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:975:in `block (3 levels) in route!'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:994:in `route_eval'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:975:in `block (2 levels) in route!'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:1015:in `block in process_route'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:1013:in `catch'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:1013:in `process_route'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:973:in `block in route!'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:972:in `each'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:972:in `route!'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:1085:in `block in dispatch!'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:1067:in `block in invoke'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:1067:in `catch'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:1067:in `invoke'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:1082:in `dispatch!'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:907:in `block in call!'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:1067:in `block in invoke'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:1067:in `catch'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:1067:in `invoke'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:907:in `call!'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:895:in `call'
/usr/local/bundle/gems/rack-protection-1.5.4/lib/rack/protection/xss_header.rb:18:in `call'
/usr/local/bundle/gems/rack-protection-1.5.4/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/local/bundle/gems/rack-protection-1.5.4/lib/rack/protection/json_csrf.rb:18:in `call'
/usr/local/bundle/gems/rack-protection-1.5.4/lib/rack/protection/base.rb:49:in `call'
/usr/local/bundle/gems/rack-protection-1.5.4/lib/rack/protection/base.rb:49:in `call'
/usr/local/bundle/gems/rack-protection-1.5.4/lib/rack/protection/frame_options.rb:31:in `call'
/usr/local/bundle/gems/rack-1.6.9/lib/rack/nulllogger.rb:9:in `call'
/usr/local/bundle/gems/rack-1.6.9/lib/rack/head.rb:13:in `call'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:182:in `call'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:2013:in `call'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:1487:in `block in call'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:1787:in `synchronize'
/usr/local/bundle/gems/sinatra-1.4.8/lib/sinatra/base.rb:1487:in `call'
/usr/local/bundle/gems/rack-1.6.9/lib/rack/handler/webrick.rb:88:in `service'
/usr/local/lib/ruby/2.5.0/webrick/httpserver.rb:140:in `service'
/usr/local/lib/ruby/2.5.0/webrick/httpserver.rb:96:in `run'
/usr/local/lib/ruby/2.5.0/webrick/server.rb:307:in `block in start_thread'

Other details:

The site works fine locally. I only get the error in console when trying to navigate to the admin interface.

Using docker to serve my site:

version: "3"
services:
  site:
    container_name: mysite.dev
    command: jekyll serve
    image: jekyll/jekyll:latest
    restart: always
    volumes:
      - $PWD:/srv/jekyll
      - $PWD/app/vendor/bundle:/usr/local/bundle
    ports:
      - 4000:4000
@jekyllbot
Copy link

This issue has been automatically marked as stale because it has not been commented on for at least two months.

The resources of the Jekyll team are limited, and so we are asking for your help.

If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.

If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.

This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.

@leimao
Copy link

leimao commented Dec 31, 2020

I got similar problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants