Projects / snek / src / snek / templates / about.md

git clone https://molodetz.nl/retoor/snek.git

Raw source file available here . 

# Snek

What is a snek?

A snek is a danger noodle.

Design choices

I made several design choices:

  • Implemented the worst 3rd party markdown to html renderer ever . See this nice bullet list .
  • Only password requirement is thats it requires six characters. Users are responsibly for their own security. Snek is not so arrogant to determine if a password is strong enough. It's up to what user prefers. Snek does not have a forgot-my-password service tho.
  • Email is not required for registration. Email is (maybe) used in future for resetting password.
  • Database is SQLite by default. Postgres is also possible. In that case you have to change db_path prefix to postgres:/// and add a postgres docker container to the docker setup.
  • Homebrew made ORM framework based on dataset.
  • Homebrew made Form framework based on the homebrew made ORM. Most forms are ModelForms but always require an service to be saved for sake of consistency and structure.
  • !DRY for HMTL/jinja2 templates. For templates Snek does prefer to repeat itself to implement exceptions for a page easier. For Snek it's preffered do a few updates instead of maintaining a complex generic system that requires maintenance regarding templates.
  • No existing chat backend like inspircd (Popular decent IRC server written in the language of angels) because I prefer to know what is exactly going on above performance and concurrency limit. Also, this approach reduces as networking layer / gateway layer.