2014-08-19 LXDE flasher image: broken web site

GoogleGroups
#1

Just FYI, I flashed the 2014-08-19 LXDE image to my BBB Rev C and the Getting Started web site on the BBB appears to be broken. Browsing to http://192.168.7.2 redirects me to http://192.168.7.2/{{site.baseurl}}/Support/bone101/, so obviously there’s a token that’s not getting replaced for some reason. I don’t know enough about the system to diagnose it any further than that yet.

Is there a better place to report issues with these images?

Eric

#2

Just FYI, I flashed the 2014-08-19 LXDE image to my BBB Rev C and the
Getting Started web site on the BBB appears to be broken. Browsing to
http://192.168.7.2 redirects me to
http://192.168.7.2/{{site.baseurl}}/Support/bone101/, so obviously
there's a token that's not getting replaced for some reason. I don't know
enough about the system to diagnose it any further than that yet.

Yeap, bone101 is broken, according to Jason, there's a new step
involved, i haven't implemented that other step yet..

Is there a better place to report issues with these images?

This is perfectly fine..

Regards,

#3

Hi Robert,

I have built a customized debian image based on your latest imagebuilder script, and I am also facing this issue. Is it still broken? If yes, could you please tell the steps to get it working?

Regards
viraniac

#4

bone101 "master" is still broken.. (master is built with jekyll) i
just pushed a commit to use a pre "master" checkout (non-jekyll
dependent) version that'll work: (it's a version of bone101 from mid
summerish)

https://github.com/RobertCNelson/omap-image-builder/commit/a61106b255bc7ae379981d13988c977671fa14b2

Regards,

#5

Hi Robert,

I have built a customized debian image based on your latest imagebuilder
script, and I am also facing this issue. Is it still broken? If yes, could
you please tell the steps to get it working?

bone101 "master" is still broken.. (master is built with jekyll) i
just pushed a commit to use a pre "master" checkout (non-jekyll
dependent) version that'll work: (it's a version of bone101 from mid
summerish)

https://github.com/RobertCNelson/omap-image-builder/commit/a61106b255bc7ae379981d13988c977671fa14b2

Here's a simple patch to avoid the bad reference to base.siteurl in
the home directory:
https://github.com/beagleboard/bone101/commit/4e9238747e864263cc0d5ebe45ee6f736206b38b

Making this work requires that you:
# apt-get install jekyll
# cd /var/lib/cloud9
# jekyll bone101

I believe the jekyll line is different on Debian 7 (wheezy) than
Debian 8 (jessie). For the newer jekyll, it should be something like:
# jekyll build --destination bone101

You should also be able to launch jekyll as a process to continuously
monitor the files and apply the templates.

#6

Here's a simple patch to avoid the bad reference to base.siteurl in
the home directory:
https://github.com/beagleboard/bone101/commit/4e9238747e864263cc0d5ebe45ee6f736206b38b

Nice Jason!!

Making this work requires that you:
# apt-get install jekyll
# cd /var/lib/cloud9
# jekyll bone101

I believe the jekyll line is different on Debian 7 (wheezy) than
Debian 8 (jessie). For the newer jekyll, it should be something like:
# jekyll build --destination bone101

I've been pulling jekyll from ruby:

[Successfully installed jekyll-2.5.2]

So we get the same version in wheezy/jessie

You should also be able to launch jekyll as a process to continuously
monitor the files and apply the templates.

I have systemd "jekyll-autorun.service"

[Service]
WorkingDirectory=/var/lib/cloud9
ExecStart=/usr/local/bin/jekyll build --watch
SyslogIdentifier=jekyll-autorun

Regards,

#7

Here's a simple patch to avoid the bad reference to base.siteurl in
the home directory:
https://github.com/beagleboard/bone101/commit/4e9238747e864263cc0d5ebe45ee6f736206b38b

Nice Jason!!

Making this work requires that you:
# apt-get install jekyll
# cd /var/lib/cloud9
# jekyll bone101

I believe the jekyll line is different on Debian 7 (wheezy) than
Debian 8 (jessie). For the newer jekyll, it should be something like:
# jekyll build --destination bone101

I've been pulling jekyll from ruby:

[Successfully installed jekyll-2.5.2]

Not sure where this got cut in the email, but I assume you mean:
# gem install jekyll

So we get the same version in wheezy/jessie

You should also be able to launch jekyll as a process to continuously
monitor the files and apply the templates.

I have systemd "jekyll-autorun.service"

[Service]
WorkingDirectory=/var/lib/cloud9
ExecStart=/usr/local/bin/jekyll build --watch
SyslogIdentifier=jekyll-autorun

You'll need to add the --destination:
See https://gist.github.com/jadonk/bc9a814b0f14d21a0dc3

#8

Thanks Jason & Robert,

That worked beautifully.

With Best Regards
viraniac