Jekyll, bone101, cloud9 and beaglebone black
- Dominant language
- JavaScript
- Stars
- 48
- Forks
- 75
- PR merge metrics
- No merged PRs in 30d
Description
I have pulled your bone101 repos to my beaglebone black in /var/lib/cloud9. But when I look at the html files and also the makefile, it looks like the webinterface is made to be run by jekyll. INdeed when I visit the webinterface of my beaglebone I get the bare jekyll preamble "--- layout: index title: bone101 scripts:" etc as plain text in the html. And I also get a bunch of 404 errors because the {{site.baseurl}} variable is output as plaintext as %7B%7Bsite.baseurl%7D%7D in the urls. So it looks like I am looking at unprocessed jekyll files. I don't see jekyll running on my beaglebone black running debian wheezy. Is this an error on my beaglebone, or do I need to build the bone101 repos first? I don't see any docs on this anywhere.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by examining the HTML files and Makefile in the bone101 repository, then compare them with the files served from /var/lib/cloud9 on the BeagleBone Black. Check how Jekyll is expected to process the templates and what build step the repository documents or implies. Done means the interface serves rendered HTML rather than Jekyll markup and the reported URL 404s are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, javascript, jekyll
- Domain
- build-system, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100