Closed jgvictores closed 5 years ago
https://github.com/GitbookIO/documentation is deprecated and now points to:
Which apparently are all also about legacy
.
One of the first steps is running Gitbook on localhost: both versions if possible (and also find out if legacy is really legacy or just legacy from the perspective of https://www.gitbook.com).
Turns out that https://github.com/GitbookIO/gitbook is the open source command line tool and Node.js library that generated the beautiful legacy
books.
From "How will this project move forward - is it left for dead? GitbookIO/gitbook#2148" we read that https://www.gitbook.com has decided to move away from open source. At time of writing:
legacy
: https://asrob-uc3m.gitbooks.io/robotdevastation-user-manual/content/en/new
: https://asrob-uc3m.gitbook.io/robotdevastation-user-manualsource | arrow keys | languages | interface | plantuml plugin | |
---|---|---|---|---|---|
legacy |
open | yes | yes | clean | yes |
new |
closed | no | no | crowded | no |
EDIT: added info regarding plantuml
, seems not rendered in new:
We've began a a list of alternatives starting here. However, I'll continue to use this issue to track progress on legacy
, which was nice.
More alternatives to be found in https://alternativeto.net/software/gitbook.
legacy
, at least for generating .html
, works great:
npm install gitbook-cli -g
_book/
via gitbook build
gitbook serve
(generates _book
anyway)Small note: On a PC without apache
, had to use the gitbook serve
option: simply opening the index.html
rendered, but arrow keys and links did not work. I've been running into similar errors lately, where very plain client-side code had to be served via python -m SimpleHTTPServer 8000
(edit: this option also works). Turns out I may have been running into "For security purposes, Mozilla applications block links to local files (and directories) from remote files. This includes linking to files on your hard drive, on mapped network drives, and accessible via Uniform Naming Convention (UNC) paths. " as described at S.O. (also for Chromium). Tried serving the generated _book
folder via apache
on server, everything cool. Simple and fast.
https://help.github.com/articles/using-a-static-site-generator-other-than-jekyll/ says GitHub pages will host, but not generate, alternatives to Jekyll. We'd have to rely on a server (think about heroku).
Turns out that legacy
gitbook.com URLs for robotics-lab
are dead due to the update (we had been warned there was no way back). Example of broken link as analogous to here (we've tried several of these): https://roboticslab-uc3m.gitbooks.io
No longer blocking asrob-uc3m org (see https://github.com/asrob-uc3m/actas/issues/148) provided these results, but blocking roboticslab-uc3m org until we:
*Note: I'm saying "temporal" because I'd like external hosting in the future (e.g. process as herokuapp and push back to github)
- [x] set up temporal cron jobs enabling temporal URLs at robots.uc3m.es
- [x] update links to these temporal URLs at robots.uc3m.es
Done for most relevant org gitbook repos (developer-manual
and teo-developer-manual
). Recommended to reopen or open new issues for other repos. Follow steps cited here as well as recommendations of https://github.com/asrob-uc3m/actas/issues/148#issuecomment-450514258.
Pending: installation-guides
See https://github.com/roboticslab-uc3m/installation-guides/issues/58
For future reference, this is installed on robots.uc3m.es at time of writing:
$ gitbook --version
CLI version: 2.3.2
GitBook version: 3.2.3
$ gitbook --version CLI version: 2.3.2 GitBook version: 3.2.3
Which, as commented at http://robots.uc3m.es/gitbook-installation-guides/install-gitbook.html (perma) works with nodejs 10.x
.
"Your organization is being upgraded to the new GitBook" (https://www.gitbook.com/@roboticslab-uc3m/migration/status).
Note: Some info at https://github.com/asrob-uc3m/actas/issues/148
legacy
vs new are different.