Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: "Antonin Décimo" <>
To: "Juliusz Chroboczek" <>
Cc: Jeroen van Veen <>,
	"" <>
Subject: [Galene] Re: Docker config?
Date: Wed, 23 Dec 2020 16:14:49 +0100	[thread overview]
Message-ID: <C809HOKA7HXX.36OZK7O0XULL6@kobain> (raw)
In-Reply-To: <>

> How do I migrate from a Github wiki to a different provider?

Various markups languages are supported, the markup of a file is
discovered using its extension (so you’d have to add .md). The web
interface doesn't take into account the structure of the repo
(directories don't map to subpages). You can customize the sidebar as
a workaround.

Essentially, it's just a flat directory with a bunch of files. No
annotations, structure, use your favorite markup language. If you want
to migrate, clone the wiki, maybe pandoc your way into another markup
language (or not).

I’m not found of them, they tend to get out-of-sync, IMO carrying the
doc within the repository and periodically generating and uploading
html from the repo somewhere is better, but it may be more noisy in
the main repo, and more cumbersome to set up.

One advantage of gh wikis is that you can loosen up editing rights to
a bigger community than developpers of the main repo. But that may
also imply proof-reading from a maintainer… some projects set up a
wiki but distanciate themselves from it; editing and maintaining the
wiki is left to the community.

  reply	other threads:[~2020-12-23 15:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-23  3:18 [Galene] " Jeroen van Veen
2020-12-23 13:33 ` [Galene] " Juliusz Chroboczek
2020-12-23 13:49   ` Antonin Décimo
2020-12-23 14:47     ` Juliusz Chroboczek
2020-12-23 15:14       ` Antonin Décimo [this message]
2020-12-24 14:25   ` Jeroen van Veen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C809HOKA7HXX.36OZK7O0XULL6@kobain \ \ \ \ \
    --subject='[Galene] Re: Docker config?' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox