This is a wiki engine with markdown template. It aims for performances on low and medium scale. It aims to implement ACL, user management, internal linking, internal search, versioning, tagging&listing, and be easy to mod. https://wiki.sceptique.eu
Go to file
Arthur POULET b75f70528d
wip: add acl
2021-10-17 11:37:10 +02:00
config wip: add database with users 2021-10-17 00:26:47 +02:00
db wip: add acl 2021-10-17 11:37:10 +02:00
spec wip: init 2021-10-16 19:19:27 +02:00
src wip: add acl 2021-10-17 11:37:10 +02:00
.drone.yml wip: init 2021-10-16 19:19:27 +02:00
.editorconfig wip: init 2021-10-16 19:19:27 +02:00
.gitignore wip: add database with users 2021-10-17 00:26:47 +02:00
LICENSE wip: init 2021-10-16 19:19:27 +02:00
Makefile wip: add database with users 2021-10-17 00:26:47 +02:00
README.md wip: add some documentation 2021-10-17 00:35:14 +02:00
polywiki wip: add acl 2021-10-17 11:37:10 +02:00
sam.cr wip: add acl 2021-10-17 11:37:10 +02:00
shard.lock wip: init 2021-10-16 19:19:27 +02:00
shard.yml wip: add some documentation 2021-10-17 00:35:14 +02:00

README.md

polywiki

TODO: Write a description here

Installation

# install dependencies
make deps

# make the binary
make release

# setup the database configuration
cp config/database.yml.sample config/database.yml
editor config/database.yml

# initialize the database
make sam db:setup

# setup the wiki base configuration
editor config/application.yml

Update

# roll the new migrations
make sam db:migrate

# make the binary
make release

Usage

TODO: Write usage instructions here

Development

Dependencies

Documentation about software dependencies we use is written in shards.yml

Database

  • We usually generate migration with make sam generate:model ModelName field:type ...
  • Sometimes to alterate existing table also make sam generate:migration MigrationName
  • Entries in the database are modelized following the principes:
    • Index what is often required
    • Don't make too many relations, but don't copy too much data
    • Always try to refuse null values, unless it make sense
    • Validate data on both application and database schema

Contributing

  1. Fork it (https://github.com/Nephos/polywiki/fork)
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request

Contributors