quokka 0.3.2

Quokka CMS!

quokka

The Happiest CMS in the world

NOTE: QuokkaCMS is being rewritten from scratch to be more simpler and use a flat file DB system the old QuokkaCMS based in MongoDB will be still available in <1.0.0 branch but will no longer be maintained or updated and fixes and improvements will be only community driven. I recommend you to use the migration script if you are using the old QuokkaCMS.

Quokka CMS is a small and simple Content Management System based in Python, Flask, Flask-Admin and TinyDB.

The default database system is TinyDB because it does not require a database system and stores data in a flat JSON file.

Altough you can also use MongoDB if you need to run the CMS in a concurrent admin user environment.

Why use QuokkaCMS

• You want a simple but powerful CMS for your website or blog

• You want a lightweight platform simple to deploy

• You want to be able to run without a database system

• You want the possibility to optionally use a powerful NoSQL database

• You want to have a web admin interface to manage your content and posts

• You want to optionally generate your CMS as a static HTML website to host on github.io

• You want to use the already existing and powerful Pelican Themes

• You want to install and develop plugins easily

• You like Quokkas (the animal)

• You like Python

• You like Flask

Quick Start

Install quokka

pip install quokka

NOTE: QuokkaCMS runs only in Python 3.6+

Start a project

quokka init mywebsite
Generating new quokka project in ./mywebsite folder

The above command will generate your project in myproject folder as:

.
├── databases        # TinyDB database files (gitignored)
├── static_build     # output static site
├── themes           # Pelican Themes
├── uploads          # Media uploaded via admin
├── .gitignore       # gitignore to exclude sensitive files
├── manage.yml       # Controls the `quokka` cli commands and shell
├── .secrets.yml     # To store keys, tokens and passwords (gitignored)
├── settings.yml     # CMS settings
└── wsgi.py          # To deploy `gunicorn wsgi:app`

You can optionally pass arguments:

Choose existing theme (the default is Flex)

quokka init mywebsite --theme http://github.com/user/theme

Install modules

quokka init mywebsite --theme http://github.com/user/theme --modules="commerce,foo"

the above looks for ``quokka_commerce`` and ``quokka_foo`` in PyPI
and installs it

Set important configurations

quokka init mywebsite --theme http://github.com/user/theme --config="auth_enabled=false"

That is optional, you have to edit ``settings.yml`` to tune your
settings.

Run your website

quokka runserver --port 5000

Access admin interface

http://localhost:5000/admin

Access your site

http://localhost:5000

Deploy

You can deploy your Quokka Website in a WSGI server

Check the wsgi.py and refer to it when deploying in wsgi servers.

cd myproject
gunicorn wsgi:app -w 4 -b "0.0.0.0:8000"

An example of supervisord config

[program:quokka]
command=/myproject/venv/bin/gunicorn wsgi:app -w 4 -b "0.0.0.0:8000"
directory=/myproject

For more information read Gunicorn documentation

Publish Static HTML website

NOTE: To generate a static website all user management, keys and passwords will be removed from settings.

You can generate a static HTML website to host anywhere

Once you have your website running locally you can easily generate a static HTML website from it.

$ quokka publish --static [--output path]
Generating static HTML website on ./static_build folder

Once you have a ./static_build folder populated with static website you can deploy it using SCP, FTP or git, it is a full static website.

Deploying to github pages from command line

NOTE: You need either ssh key access to github or it will ask login/password

quokka publish --static --git=rochacbruno/mysite --branch=gh_pages

The above is also available in admin under 'publish' menu.

Deploying via SCP

quokka publish --static --scp --dest='me@hostname:/var/www/mysite' [--sshkey ~/.ssh/key] [--password xyz]
password : ...

Deploying to Heroku

This requires heroku client installed, if Procfile is not found it will be generated

quokka publish --static --heroku --options

Deploying via FTP

quokka publish --static --ftp --host='ftp://server.com' --dest='/var/www/mysite'

Load database from remote deployment (only for TinyDB)

When you publish a static website along with the static files the database also goes to the server under the databases/ folder only as a backup and snapshot.

You can load that remote database locally e.g: to add new posts and then re-publish

quokka restoredb --remote --git=rochacbruno/mysite
Creating a backup of local database...
Downloading remote database
Restoring database..
Done...

Now you can run quokka runserver open your localhost:5000/admin write new content and then Publish website again using command line or admin interface.

NOTE: If you want to restore a local database use --local and --path path/to/db

Using MongoDB

You can choose to use MongoDB instead of TinyDB, That is useful specially if you deploy or local instance has more than one admin user concurrently and also useful if you want to install plugins which support MongoDB only (because it relies on aggregations and gridfs)

You only need a running instance of Mongo server and change settings.yml:DB on your project from:

quokka:
  DB:
    system: tinydb
    folder: databases

to:

quokka:
  DB:
    system: mongodb
    name: my_database
    host: 127.0.0.1
    port: 2600
    username: xxxx
    password: xxxx

Then when running quokka again it will try to connect to that Mongo Server.

With that you can deploy your site on wsgi server or can also generate static website.

Contributing to Quokka CMS Development

Do you want to be part of this open-source project?

Take a look at Contributing Guidelines