mirrors/mycorrhiza
1
0
Fork 0
mirror of https://github.com/osmarks/mycorrhiza.git synced 2024-12-04 18:19:54 +00:00
Code Issues Releases Wiki Activity
Wiki engine fork.
831 Commits 1 Branch 0 Tags 13 MiB
Go 70.8%
HTML 13.9%
JavaScript 7.2%
CSS 7.1%
Roff 0.8%
Other 0.2%
59deabd0d1
Go to file
Timur Ismagilov 59deabd0d1 Reimplement Navititle with go templates 
That was rough
2022-04-23 23:35:36 +03:00
.github/workflows Return windows binaries, but not for arm64 2021-08-01 23:56:45 +05:00
backlinks Embed data-rrh-addr attribute on all pages 2022-04-23 21:53:15 +03:00
categories Embed data-rrh-addr attribute on all pages 2022-04-23 21:53:15 +03:00
cfg Mycomarkup: Migrate to v4 2022-04-07 20:17:59 +03:00
files Categories: Show pre-populated categories 2022-03-19 23:57:33 +03:00
help Embed data-rrh-addr attribute on all pages 2022-04-23 21:53:15 +03:00
history Please staticcheck 2022-04-02 11:09:37 +03:00
hyphae Backlinks: Isolate 2022-04-02 19:58:57 +03:00
hypview Reimplement Navititle with go templates 2022-04-23 23:35:36 +03:00
l18n Backlinks: Isolate 2022-04-02 19:58:57 +03:00
migration Mycomarkup: Migrate to v4 2022-04-07 20:17:59 +03:00
mimetype Make mimetype.FromExtension case-insensitive 2022-02-20 12:28:33 +03:00
misc Get rid of div.layout, center header on two-columnar layout 2022-04-21 19:05:17 +03:00
shroom Mycomarkup: Migrate to v4 2022-04-07 20:17:59 +03:00
static Align left sidebars properly on very wide screens 2022-04-21 19:19:20 +03:00
tree Move hyphae.Iteration to a separate package 2022-02-20 12:40:16 +03:00
user Categories: Do not let anons add to/remove from categories 2022-03-26 18:31:13 +03:00
util Mycomarkup: Migrate to v4 2022-04-07 20:17:59 +03:00
views Reimplement Navititle with go templates 2022-04-23 23:35:36 +03:00
viewutil Reimplement Navititle with go templates 2022-04-23 23:35:36 +03:00
web Reimplement Navititle with go templates 2022-04-23 23:35:36 +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 v4.0.1 2022-04-17 16:59:44 +03:00
go.sum Mycomarkup: Update to v4.0.1 2022-04-17 16:59:44 +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.10.0 2022-04-21 17:39:23 +03:00
Makefile Move mycorrhiza.1 to help directory 2022-03-26 18:54:01 +03:00
README.md Update README.md 2022-04-03 15:34:31 +03:00

README.md

🍄 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.