Realtime collaborative hackathon tracks on all platforms.
More awesome hackathons!
A platform for time-limited, team-based, data-driven, open collaboration
For background and references, see User's Guide and About Page. If you need help or advice in setting up your event, or would like to contribute to the project: please get in touch via GitHub Issues or e-mail. The rest of this page has details for deploying the dribdat application.
Screenshot of a dribdat event page.
This project can be deployed to any server capable of serving Python applications, and is set up for fast deployment to the Heroku cloud:
The first user that registers becomes an admin, so don't delay! If you would like to run dribdat on any other cloud or local machine, follow the Developer guide below. The following section details environment variables you can add to tweak your installation.
Optimize your dribdat instance with the following environment variables in production:
TIME_ZONE- set if your event is not in UTC time (e.g. "Europe/Zurich" - see pytz docs)
SERVER_URL- fully qualified domain name where the site is hosted
SERVER_SSL- redirect all visitors to HTTPS, applying CSP
CSP_DIRECTIVES- configure content security policy - see Talisman docs
DATABASE_URL- connects to PostgreSQL or another database via
postgresql://username:[email protected](in Heroku this is set automatically)
CACHE_TYPE- speed up the site with Redis or Memcache - see Flask-Caching
The following options can be used to toggle application features:
DRIBDAT_ENV- 'dev' to enable debugging, 'prod' to optimise assets etc.
DRIBDAT_SECRET- a long scary string for hashing your passwords - in Heroku this is set automatically
DRIBDAT_APIKEY- for connecting clients to the remote API
DRIBDAT_USER_APPROVE- set to True so that any new non-SSO accounts are inactive until approved by an admin
DRIBDAT_NOT_REGISTER- set to True to hide the registration, so new users can only join this server via SSO
DRIBDAT_TOOL_APPROVE- set to True for suggested components to not immediately appear
DRIBDAT_THEME- can be set to one of the Bootswatch themes
DRIBDAT_STYLE- provide the address to a CSS stylesheet for custom global styles
DRIBDAT_CLOCK- use 'up' or 'down' to change the position, or 'off' to hide the countdown clock
Support for Web analytics can be configured using one of the following variables:
ANALYTICS_FATHOM(Fathom - with optional
ANALYTICS_FATHOM_SITEif you use a custom site)
ANALYTICS_GOOGLE(starts with "UA-...")
ANALYTICS_HREF- an optional link in the footer to a public dashboard for your analytics
OAuth 2.0 support for Single Sign-On (SSO) is currently available using Flask Dance, and requires SSL to be enabled (using
SERVER_SSL=1 in production or
OAUTHLIB_INSECURE_TRANSPORT in development). Register your app with the provider (see SSO tips below), and set the following variables:
OAUTH_TYPE- e.g. 'Slack', 'GitHub', 'Azure'
OAUTH_ID- the Client ID of your app
OAUTH_SECRET- the Client Secret of your app
OAUTH_DOMAIN- (optional) subdomain of your Slack instance, or AD tenant for Azure
OAUTH_SKIP_LOGIN- (optional) when enabled, the dribdat login screen is not shown at all
For uploading images and other files directly within dribdat, you can configure S3 through Amazon and compatible providers:
S3_KEY- the access key (20 characters, all caps)
S3_SECRET- the generated secret (long, mixed case)
S3_BUCKET- the name of your S3 bucket
S3_REGION- defaults to 'eu-west-1'
S3_FOLDER- skip unless you want to store to a subfolder
S3_HTTPS- URL for web access to your bucket's public files
S3_ENDPOINT- alternative endpoint for self-hosted Object Storage
MAX_CONTENT_LENGTH- defaults to 1048576 bytes (1 MB) file size
To customize some of the default content, you can edit the template include files, for example the default quickstart or stages - as long as you're not limited by ephemeral storage of your deployment.
There are a number of API calls that admins can use to easily get to the data in Dribdat in CSV or JSON format. These are linked in the About page in a running app. Additionally, the site has a See GitHub issues for development status.
Basic data on an event:
Retrieve data on all projects from an event:
Recent activity in projects (all or specific):
Search project contents:
limit query parameter to get more or less than 10 results.
If you would like to use external clients, like the chatbot, to remote control Dribdat you need to set
DRIBDAT_APIKEY. The (experimental) call used to push data into projects is:
For more details see api.py
Install Python, Virtualenv and Pip, or Poetry to start working with the code.
Run the following commands from the repository root folder to bootstrap your environment:
poetry shell poetry install
Or using plain pip:
pip install -r requirements/dev.txt
By default in a dev environment, a SQLite database will be created in the root folder (
dev.db). You can also install and configure your choice of DBMS supported by SQLAlchemy. In production, the
DATABASE_URL configures connectivity to an SQLAlchemy-compatible database engine. This requires a
.envto store environment variables for local development. See the Configuration section for more details.
Run the following to create your local SQLite database tables and perform the initial migration. Note that we avoid using the production
migrations folder locally due to Flask-Migrate#61:
mv migrations migrations_prod python manage.py db init python manage.py db migrate python manage.py db upgrade
Install a local copy of frontend resources for offline development using yarn install. These will be used when
FLASK_ENV=dev, otherwise a CDN will be used in production.
Finally, run this command (or just
debug.sh) to start the server:
FLASK_DEBUG=1 python manage.py run
You will see a welcome screen at http://127.0.0.1:5000 - register your first user account, which will have admin access and let you set up events.
This section has some advice for developers and operators.
To open the interactive shell, run:
python manage.py shell (or, using the Heroku toolchain,
heroku run python manage.py shell). By default, you will have access to the
User model, as well as Event, Project, Category, Activity.
To run all tests, whose source is in the tests folder, run:
python manage.py test
Whenever a database migration needs to be made. Run the following commands:
python manage.py db migrate
This will generate a new migration script. Then run:
python manage.py db upgrade
To apply the migration. Watch out for any errors in the process.
For a full migration command reference, run
python manage.py db --help.
Guidance to common errors:
Add results to my own web page
There is an Embed button in the event page and in the admin which provides you with code for an IFRAME that just contains the hexagrid. If you would like to embed the entire application, and find it more intuitive to hide the navigation, add
?clean=1 to the URL. To also hide the top header, use
?minimal=1. You might also invoke the dribdat API to pull data from the platform.
Navigation is not visible
Dark Bootswatch themes do not play well with the navbar-light component used in our layout (
nav.html). Override the styles by hand using the
DRIBDAT_CSS_URL environment variable.
Need help setting up SSO
Cannot determine SSO callback for app registration? Try
<my server url>/oauth/slack/authorized (replace
slack with your OAuth provider).
Restore admin access
Create a user account if you do not already have one. From the console, run
./manage.py shell then to promote to admin and/or reset the password of a user called "admin":
u = User.query.filter(User.username=='admin').first() u.is_admin = True u.set_password('[email protected]*/c0mpl3x') u.save()
Cannot upgrade database
In local deployment, you will need to upgrade the database using
./manage.py db upgrade. On Heroku, a deployment process called Release runs automatically.
If you get errors like ERROR [alembic.env] Can't locate revision identified by 'aa969b4f9f51', your migration history is out of sync. You can set
FORCE_MIGRATE to 1 when you run releases, however changes to the column sizes and other schema details will not be deployed. Instead, it is better to verify the latest schema specifications in the
migrations folder, fix anything that is out of sync, and then update the alembic version, e.g.:
alter table projects alter column webpage_url type character varying(2048); insert into alembic_version values ('7c3929047190')
See also further instructions in the
Test locally using SSL
Some development scenarios and OAuth testing requires SSL. To use this in development with self-signed certificates (you will get a browser warning), start the server with
./manage.py run --cert=adhoc
You can also try to test SSO providers with
OAUTHLIB_INSECURE_TRANSPORT=true (do not use in production!)
Special thanks to the Open Data, Open Networking and Open Source communities in Switzerland for the many trials and feedbacks. We are also grateful to F. Wieser and M.-C. Gasser at Swisscom for conceptual inputs and financial support at an early stage of this project. This code is originally based on Steven Loria's flask-cookiecutter, which we of course encourage you to use in YOUR next project!
Additional and :heart:-felt thanks for testing and feedback to: