FestivalsApp Server
A lightweight service providing a RESTful API, called FestivalsAPI. The FestivalsAPI provides all the necessary data for the FestivalsApp, including festivals and events, as well as functionality to create and manage this data.

Development •
Deployment •
Engage
Development
The developement of the FestivalsAPI (see documentation) and the festivals-server is heavily dependend on the festivals-api-ios and the festivals-database which provides the persistent storage to the FestivalsAPI. In my regular development workflow i first mock the needed behaviour in the API client library and then start implementing the changes in the festivals-server and after that in the festivals-database. To test whether the festivals-server is working correctly i'm currently relying on downstream tests of the festivals-api-ios framework.
The general documentation for the Festivals App is in the festivals-documentation repository. The documentation repository contains architecture information, general deployment documentation, templates and other helpful documents.
Requirements
Deployment
The Go binaries are able to run without system dependencies so there are not many requirements for the system to run the festivals-server binary,
just follow the deployment guide for deploying it inside a virtual machine or the local deployment guide
for running it on your macOS developer machine.
Engage
I welcome every contribution, whether it is a pull request or a fixed typo. The best place to discuss questions and suggestions regarding the festivals-server is the issues section.
More general information and a good starting point if you want to get involved is the festival-documentation repository.
The following channels are available for discussions, feedback, and support requests:
| Type |
Channel |
| General Discussion |
|
| Other Requests |
 |
Licensing
Copyright (c) 2017-2025 Simon Gaus. Licensed under the GNU Lesser General Public License v3.0