OneGov Cloud Modules¶
There are three kinds of OneGov Cloud Modules:
- Base modules
Provide the framework inside which OneGov Cloud is run.
- Supporting modules
Provide models/methods/utilities, but no HTTP interface (neither HTML nor REST).
- Base applications
Provide shared bases for multiple applications. Namely it allows for shared UI elements.
Utilize the base and the supporting modules to actually provide a web application. Those may or may not be limited to HTML/REST.
This is how this hierarchy looks like:
┌───────────────┐ │ │ │ onegov.server │ ◇─┐ │ │ │ └───────────────┘ │ ▲ │ base modules │ │ ┌───────────────┐ │ │ │ │ │ onegov.core │ ◇─┘ │ │ └───────────────┘ ▲ │ ┌───────────────┐ │ │ ◇─┐ │ onegov.org │ │ a base application │ │ ◇─┘ └───────────────┘ ▲ │ ┌───────────────┐ │ │ ◇─┐ │ onegov.town │ │ an application │ │ ◇─┘ └───────────────┘ ┌──────────────────┼──────────────────┐ ▼ ▼ ▼ ┌───────────────┐ ┌───────────────┐ ┌───────────────┐ │ │ │ │ │ │ │ onegov.page │ │ onegov.user │ │ onegov.form │ │ │ │ │ │ │ └───────────────┘ └───────────────┘ └───────────────┘ ◇ ◇ └─────────────────────────────────────┘ supporting modules (may depend on onegov.core or each other)
Serves the OneGov web-applications. Meant to be the runner and configurator of all applications. Not meant to run publicly. Like all python web-applications this one should be proxied behind Nginx or Apache2.
OneGov server does not depend on any other OneGov module.
Contains functionality shared between all the other OneGov modules, with the exception of OneGov Server, which may not depend on the core. In many ways this is the OneGov Cloud framework.
- Onegov Core API
- Static Files
- Browser Session
- Internationalization (i18n)
- Templating (Chameleon)
- Cli Commands
- Webasset Filters
Provides a base for applications written for organizations close to the government. For example, municipalities, youth organizations, elderly care, and so on.
The most visible part of the OneGov municipality websites. Combines functionality of other OneGov modules and renders them.
OneGov Town tries to implement features itself when necessary. It’s main concern is rendering JSON/HTML. Therefore it should be considered the UI layer.
Providers user management without any UI.
Integrates the form library WTForms with OneGov and provides useful functionality related to that. May generate HTML, but won’t offer any UI as such.
Provides a way to store and serve files tied to the database and bound to the transaction.
Provides functionality to manage custom pages used by OneGov Town. Does not provide a UI.
Provides functionality to manage people. Does not provide a UI.
Provides the Zurb Foundation theme for OneGov in an extendable fashion.
A simple ticketing system for OneGov.
Libres integration for OneGov Cloud. Libres is a python library to reserve stuff.
A simple event (concert, meetup, party) system for OneGov Cloud.
Elasticsearch integration for OneGov Cloud.
A generic implementation of e-mail/sms/url recipients backed by the database.
OneGov Election Day¶
Shows Swiss election/voting results in an archive and as they come in during voting day.
Contains a model representing elections/votes in Switzerland.
Developed for Pro Juventute, this specialised organisation website helps to organise summer activites for Switzerland’s youth.
Contains the model representing youth activites for Pro Juventute.