Your friendly manager of attendees at an event.
EventMan(ager) will help you handle your list of attendees at an event, managing the list of tickets and marking persons as present.
See the screenshots directory for some images.
See the docs/DEVELOPMENT.md file for more information about how to contribute.
The web part is incuded; you need to install Tornado, MongoDB and the pymongo module on your system (no configuration needed). If you want to print labels using the print_label trigger, you may also need the pycups module.
Be sure to have a running MongoDB server, locally. If you want to install the dependencies only locally to the current user, you can append the --user argument to the pip calls. Please also install the python3-dev package, before running the following commands.
wget https://bootstrap.pypa.io/get-pip.py sudo python3 get-pip.py sudo pip3 install tornado # version 4.2 or later sudo pip3 install pymongo # version 3.2.2 or later sudo pip3 install python-dateutil sudo pip3 install pycups # only needed if you want to print labels sudo pip3 install eventbrite # only needed if you want to import from Eventbrite using their API sudo pip3 install serial # only for the qrcode_reader script sudo pip3 install requests # only for the qrcode_reader script git clone https://github.com/raspibo/eventman cd eventman ./eventman_server.py --debug
Open browser and navigate to: http://localhost:5242/
If you store SSL key and certificate in the ssl directory (default names: eventman_key.pem and eventman_cert.pem), HTTPS will be used: https://localhost:5242/
So, you've just installed it and you have the server running. Let's create an event:
Now persons can start joining your event:
As an administrator, you can now go to the list of tickets of the event:
Some notes about the event registration form:
About the "Group ID" of events and "Unregistered persons" list:
By default, authentication is not required; unregistered and unprivileged users can see and join events, but are unable to edit or handle them. Administrator users can create ed edit events; more information about how permissions are handled can be found in the docs/DEVELOPMENT.md file.
The default administrator username and password are admin and eventman. If you want to force authentication (you usually don't), run the daemon with --authentication=on
Users can register, but are not forced to do so: tickets can also be issued to unregistered persons. However, if you register, you'll be able to access the list of all of your tickets (otherwise, you have to save the tickets' link, if you want to edit them later).
In the 'tools' directory there are some useful tools, to handle check-in and extract data.
Needs something simpler, that just allows you to register attendees at an event? Try ibt2
Copyright 2015-2017 Davide Alberani email@example.com, RaspiBO firstname.lastname@example.org
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.