{% extends "base.html" %} {% block title %}Kahala — Jamgraf{% endblock %} {% block content %}
Kahala is the shared, server-side half of the same wiki. A local wiki can be linked to one there, then pushed up or pulled down. Only content travels — pages, their hierarchy, elements, templates and images. Search indexes are rebuilt on arrival rather than sent.
{# --- signing in ---------------------------------------------------- #}Jamgraf will not keep a sign-in token in a plain file, so signing in is switched off here rather than done less safely.
{% elif not status.can_sign_in %} {% elif status.signed_in %}Signed in to {{ status.issuer }}. The token is kept in your
Keychain, never in a wiki file, so it is not included when you save or
share a wiki.
One sign-in per install, not per wiki: every linked
wiki uses this identity. If you need a Kahala on a different sign-in
server, sign out and set kahala_issuer in
app_config.json — a proper per-link setting is
tracked.
You aren’t signed in to {{ status.issuer }} yet.
This opens Kahala’s own sign-in page in your web browser — not inside Jamgraf — so you get your usual session, your password manager and whatever second factor your organisation uses. Jamgraf never sees your password.
{% endif %}Linked to {{ status.remote }} on
{{ status.base_url }}.
Push and pull normally send only what changed, which is a few kilobytes rather than the whole wiki. These send everything — slower, and worth reaching for if something looks out of step.
Push and pull need you to be signed in.
{% endif %} {# The one thing people misread about a snapshot round-trip. Say it on the page, next to the buttons, not only in the docs. #}Both directions merge; neither deletes. A push adds and updates pages on Kahala and removes nothing there; a pull does the same here. So a page you deleted locally is still on Kahala, and a pull will bring it back.
Custom elements, templates and images travel with the pages, so a page never arrives referring to a definition that didn’t.
A push can’t create the wiki on Kahala. It has to exist there first — Open Kahala… goes to the page where you make one. Jamgraf can’t do it for you: creating a wiki there is a browser form tied to your Kahala session, and the token Jamgraf holds is only accepted on Kahala’s API.
{% else %}This wiki isn’t linked yet.
Linking only records the address here on this machine. It is never written into the wiki itself, so it can’t travel to someone you share the wiki with.
The wiki has to already exist on Kahala. Create it there first (its Wikis page), then put the name it ends up with above — Kahala turns the name you type into the slug, so they can differ. Linking to something that isn’t there yet looks identical to linking to another tenant’s wiki, and the push will say so.
{% endif %}A clone always creates a new local wiki, so it can never write over one you already have.
| {{ slug }}
{{ lk.remote }} on {{ lk.base_url }} |
Open |