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

Running documentation doesn't work as described in Readme #8174

Closed
mediafreakch opened this issue Jun 14, 2013 · 5 comments
Closed

Running documentation doesn't work as described in Readme #8174

mediafreakch opened this issue Jun 14, 2013 · 5 comments
Labels

Comments

@mediafreakch
Copy link
Contributor

Bootstrap 3.0.0:
The most recent Readme says:

  1. If necessary, install Jekyll.
  2. From the /bootstrap directory, run jekyll serve in the command line.
  3. Open http://getbootstrap.dev:9001 in your browser, and voilà.

This doesn't work. An error message saying that the server couldn't be found will be displayed in the browser when you try to access http://getbootstrap.dev:9001. What's the right command to see the docs on a local server?

@cvrebert
Copy link
Collaborator

Yeah, I remember running into this recently. IIRC, try http://localhost:9001 instead.

@mediafreakch
Copy link
Contributor Author

Didn't work neither. I got it working by runnning jekyll serve --server in the command line and accessing it via http://localhost:4000

But I don't think that's the intended behaviour...

@mdo
Copy link
Member

mdo commented Jun 15, 2013

Perhaps you're on an old version of Jekyll? --server is a deprecated command for Jekyll. See the docs at http://jekyllrb.com/docs/. You should only need to run jekyll serve or jekyll build.

@mediafreakch
Copy link
Contributor Author

After updating Jekyll to 1.0.3 it works using jekyll serve and accessing the docs locally on localhost:9001 .
There is already a pull request #8182 that fixes the link in the readme. But actually that means that there is an issue with the jekyll _config.yml configuration not taking into account the url variable. I couldn't figure out why...

@mdo
Copy link
Member

mdo commented Jun 20, 2013

Looks like this has been resolved in v3 now—no more custom URL, but there is still a custom port.

@mdo mdo closed this as completed Jun 20, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants