1
0
mirror of https://github.com/osmarks/mycorrhiza.git synced 2024-10-30 03:36:16 +00:00
Wiki engine fork.
Go to file
Timur Ismagilov afba9b597a Update release.yaml
* Remove freebsd. Seems like it was failing the builds of the previous two releases, that's why other platforms thought they should not build as well
* Add help/mycorrhiza.1 into the extra files section
2022-06-05 20:45:00 +03:00
.github/workflows Update release.yaml 2022-06-05 20:45:00 +03:00
admin Admin: Isolate the panel view 2022-05-18 21:03:36 +03:00
backlinks Mycomarkup: Update to v5.0.1 2022-06-05 15:35:40 +03:00
categories Viewutil: Introduce CopyEnRuWith 2022-05-18 19:58:24 +03:00
cfg Mycomarkup: Update to v5.0.0 2022-06-05 15:35:40 +03:00
files Interwiki: Start implementing 2022-05-22 12:25:22 +03:00
help Change version to 1.11.0 2022-06-05 15:36:58 +03:00
history Fix /history/ <title> 2022-05-31 13:38:06 +03:00
hyphae Backlinks: Isolate 2022-04-02 19:58:57 +03:00
hypview Viewutil: Introduce CopyEnRuWith 2022-05-18 19:58:24 +03:00
interwiki Mycomarkup: Update to v5.0.0 2022-06-05 15:35:40 +03:00
l18n History: Translate /history/ 2022-05-18 20:32:53 +03:00
migration Mycomarkup: Update to v5.0.0 2022-06-05 15:35:40 +03:00
mimetype Make mimetype.FromExtension case-insensitive 2022-02-20 12:28:33 +03:00
misc Viewutil: Introduce CopyEnRuWith 2022-05-18 19:58:24 +03:00
shroom Mycomarkup: Update to v5.0.0 2022-06-05 15:35:40 +03:00
static Mycomarkup: Update to v4.3.2 2022-06-05 15:35:40 +03:00
tree Move hyphae.Iteration to a separate package 2022-02-20 12:40:16 +03:00
user Auth: Do not load users with weird characters in names 2022-05-17 16:35:43 +03:00
util Mycomarkup: Update to v5.0.0 2022-06-05 15:35:40 +03:00
views Change version to 1.11.0 2022-06-05 15:36:58 +03:00
viewutil Copyedit 2022-05-18 20:18:30 +03:00
web Mycomarkup: Update to v5.0.0 2022-06-05 15:35:40 +03:00
.gitignore Allow changing the wiki path for make 2021-10-26 12:45:28 +07:00
.mailmap Add a .mailmap 2022-02-01 20:47:32 +07:00
Dockerfile Docker: Delete the line 2022-02-19 12:25:23 +03:00
flag.go Remove some unused stuff 2022-02-20 13:11:29 +03:00
go.mod Mycomarkup: Update to v5.0.1 2022-06-05 15:35:40 +03:00
go.sum Mycomarkup: Update to v5.0.1 2022-06-05 15:35:40 +03:00
httpd.go Migrate to gorilla/mux for web needs 2021-07-16 00:47:00 +07:00
LICENSE Change the license to AGPL 2021-03-29 16:13:52 +05:00
main.go Change version to 1.11.0 2022-06-05 15:36:58 +03:00
Makefile Move mycorrhiza.1 to help directory 2022-03-26 18:54:01 +03:00
README.md Update README.md 2022-06-03 21:06:00 +03:00

🍄 Mycorrhiza Wiki

Mycorrhiza Wiki is a lightweight file-system wiki engine that uses Git for keeping history. Main wiki

A screenshot of mycorrhiza.wiki's home page in the Safari browser

Features

  • No database required. Everything is stored in plain files. It makes installation super easy, and you can modify the content directly by yourself.
  • Everything is hyphae. A hypha is a unit of content such as a picture, video or a text article. Hyphae can transclude and link each other, forming a tight network of hypertext pages.
  • Hyphae are authored in Mycomarkup, a markup language that's designed to be unambigious yet easy to use.
  • Categories let you organize hyphae without any hierarchy restrictions, with all the benefits of a category system.
  • Nesting of hyphae is also supported if you like hierarchies.
  • History of changes for textual parts of hyphae. Every change is safely stored in Git. Web feeds for recent changes included.
  • Keyboard-driven navigation. Press ? to see the list of shortcuts.
  • Support for authorization. Both plain username-password pairs and Telegram's login widget are supported.
  • Open Graph support. The most relevant info about a hypha is made available through OG meta tags for consumption by other software.

Compare Mycorrhiza Wiki with other engines on WikiMatrix.

Installing

See the deployment guide on the wiki.

Contributing

If you want to contribute with code, open a pull request on GitHub or send a patch to the mailing list. If you want to report an issue, open an issue on GitHub or contact us directly.

Consider supporting the development on Boosty.