RunestoneInteractive / RunestoneInteractive/rs
eBookConfig migration
Open
@ascholerChemeketa is already working on this.
Since Aug 18, 2026.
enhancement
- Dominant language
- TypeScript
- Stars
- 69
- Forks
- 117
- Avg merge
- 6d 4h
- Merged PRs (30d)
- 24
Description
This is for discussion related to moving as much responsibility for eBookConfig to Runestone as possible.
Here is what the _base.html emitted by RS has:
eBookConfig property |
Runestone-hosted context variable / source | Non-Runestone-hosted value |
|---|---|---|
π’ π΅ π‘ useRunestoneServices |
Fixed: true |
false |
π΄ host |
Fixed: '' |
http://127.0.0.1:8000 |
π΄ app |
Derived from host |
Not set |
π’ course |
course_name |
PTX_Course_Title_Here |
π’ termStartDate |
term_start_date |
Not set |
π’ basecourse |
base_course |
PTX_Base_Course |
π’ isLoggedIn |
is_logged_in (default false) |
false |
π’ email |
user_email |
'' |
π’ isInstructor |
is_instructor (default false) |
false |
π’ π΅ logLevel |
Fixed: 10 |
0 |
π΄ ajaxURL |
Derived from app |
Not set |
π’ username |
user_id |
'' |
π’ readings |
readings (default []) |
null |
π’ activities |
activity_info (default {}) |
null |
π’ π‘ downloadsEnabled |
downloads_enabled (default false) |
false |
π’ π‘ allow_pairs |
allow_pairs (default false) |
false |
π’ course_attrs |
course_attrs (default {}, JSON-encoded) |
Not set |
π’ π΅ π‘ enableScratchAC |
Publisher option: $b-has-scratch-activecode |
Same |
π’ π΅ π‘ acDefaultLanguage |
$html-scratch-activecode-language, when Scratch enabled |
Same |
new_server_prefix |
Fixed: "/ns" |
Not set |
π‘ runestone_version |
$runestone-version |
Same |
π΄ build_info |
Not set | '' |
π΄ python3 |
Not set | null |
π΄ jobehost |
Not set | '' |
π΄ proxyuri_runs |
Not set | '' |
π΄ proxyuri_files |
Not set | '' |
π΄ enable_chatcodes |
Not set | false |
π’ Definitely needed for RA
π΄ Should be removed, potentially with a bit of work
π΅ Needed for static html
π‘ Gets a value set by PreTeXt
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up β it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.