Skip to content

asplunden/hollyrosa

Repository files navigation

Synopsis

Hollyrosa is a special developed program booking system for a scout centre called Vässarö, located on an island in Sweden. It's tailore made for Vässarö, the culture and the ways we do things.

Many centers use or look for activity booking systems, however, scouting simply isn't a set of activities on a patch of grass. I have therfore decided to design and build a program booking system, a system that help us make a better scout program for both visiting groups and staff. We believe being a staff member is/could be part of the scout program and this has guided design decisions in this system.

Some design decisions are just mad becuase the way we do things at Vässarö, For example, all program are free for groups at the island, so the system has no support at this time for billing which otherwise is quite common.

The system is built on Turbogears2 and is a little bit odd in that it uses CouchDB 1.x as backend, it does however allow master-master replication which in our case is a critical requirement.

Motivation

This project exist to make it possible for more kids and youth to have a great summer and scout experience. It also exists to enable our goal to empower young people, it does so by the single fact that it makes progeram booking distributed and so our young staff can handle the system and we old program staff can just monitor and check that all looks ok.

License

Hollyrosa is Copyright 2010-2018 Martin Eliasson

Hollyrosa is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

Hollyrosa is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details.

You should have received a copy of the GNU Affero General Public License along with Hollyrosa. If not, see http://www.gnu.org/licenses/.

Installation

You will need a running Couchdb 1 instance. I would recommend that you run CouchDB 1 in a docker container mapping the data folder to the host machine somewhere.

You can install the system as a Turbogears2 app and in production you may run it using Apache+mod_wsgi. You will also need to use the hollyrosa_viewtool to upload views to your CouchDB database.

Installation of TG2.3.11 using python 2

For Python 3, the installation is quite similar but not yet documented.

Step 1: Create virtualenv and activate:

virtualenv hollyrosa_env
cd hollyrosa_env
source bin/activate

Step 2: install TG

cd hollyrosa_env
pip install tg.devtools

Step 3: get source from Github

git clone https://github..../hollyrosa

Step 4: install hollyrosa

pip install -e .

Step 5: download tinymce 4 prod

TinyMCE v4 is not included with this codebase, it must be downloaded separately.

Download from http://download.tiny.cloud/tinymce/community/tinymce_4.9.7.zip and unzip into the public folder.

Another option is to change the links in the TinyMCE4Widget to point to the CDNs for tinymce.

cd <path to public>
wget http://download.tiny.cloud/tinymce/community/tinymce_4.9.7.zip
unzip tinymce_4.9.7.zip
rm tinymce_4.9.7.zip

Preparations

You will need to setup the couchdb 2 and configuring before proceeding.

TBD.

Deployment

There are many ways to deploy Hollyrosa using WSGI, below are a few hints

Apache Deployment using mod_wsgi

TBD

Nginx Deployment using WSGI and uWSGI

Nginx has straightforward support for uwsgi. Connecting to the uwsgi server may look like the example below. In order to offload static file serving from uwsgi, the three folders in the public folder of hollyrosa may be served directly by nginx.

´´´ location /hollyrosa/ { uwsgi_pass unix:/run/uwsgi/hollyrosa.socket;
include uwsgi_params; }

´´´

Deploying Hollyrosa with uWSGI and Systemd

The files below is adapted from uwsgi docs and creates a wsgi app that is managed by systemd. The service is started if it is not running when a connection is made to the socket.

The socket file below must be activated (the service itself is not ment to be directly activated) ´´´ systemctl enable uwsgi.service ´´´

/etc/systemd/system/wsgi-app@.socket

´´´ [Unit] Description=Socket for uWSGI app %i

[Socket] ListenStream=/run/uwsgi/%i.socket SocketUser=www-%i SocketGroup=www-data SocketMode=0660

[Install] WantedBy=sockets.target ´´´

/etc/systemd/system/wsgi-app@.service

´´´ [Unit] Description=%i uWSGI app After=syslog.target

[Service] ExecStart=/usr/bin/uwsgi
--ini /etc/uwsgi/apps-available/%i.ini --socket /run/uwsgi/%i.socket User=www-%i Group=www-data Restart=on-failure KillSignal=SIGQUIT Type=notify StandardError=syslog NotifyAccess=all ´´´

/etc/uwsgi/apps-available/hollyrosa.ini

´´´ [uwsgi] master = True cheap = True idle = 600 die-on-idle = True manage-script-name = True

plugin = python3 chdir = /hollyrosa wsgi-file = /hollyrosa/app.wsgi processes = 4 threads = 2 stats = 127.0.0.1:9191 virtualenv =

uid = www-hollyrosa gid = www-data

´´´

/hollyrosa/app.wsgi: ´´´ APP_CONFIG = "/hollyrosa/production.ini"

#Setup logging import logging.config logging.config.fileConfig(APP_CONFIG)

#Load the application from paste.deploy import loadapp application = loadapp('config:%s' % APP_CONFIG) ´´´

Tools

A set of tools have been developed to help administrating Hollyrosa. They are located in the hollyrosa/hollyrosa folder.

  • hollyrosa_view_tool.py - used by developers to load and store CouchDB view code
  • hollyrosa_tool.py - main tool for configuring new databases each year. Needs to be changed and configured every year.
  • hollyrosa_room_tool.py - tool used for creating room schemas
  • hollyrosa_schema_tool.py - tool used for creating program schemas

Development

Run (in debug mode)

gearbox serve -c <path to ini file>

Handling CouchDB view code in git

To store edited view code in CouchDB to the local source tree so they can be version controlled:

python hollyrosa_view_tool.py --couch=http://HOSTNAME:PORT --database DATABASENAME --username=USERNAME --password=PASSWORD --save-views

Tips on preventing accidental push to master

git config branch.master.pushRemote no_push

About

Scheduling solution for program activities at Vässarö scout centre. Used successfully in real life. Built on top of Turbogears2.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published