The website. The app. The everything.
A Django app that serves our website, payment portal for donations, engineering blog, and API. It can be found at https://grafeas.org.
For a quick and dirty method of testing blossom locally, run
docker-compose up -dand point your browser to http://localhost:8080/
Create a file at the top level called local_settings.py. Populate it with the following:
from blossom.settings.local import *
import better_exceptions
import os
# trust me, this will make your life better.
better_exceptions.MAX_LENGTH = None
# Use this file when developing locally -- it has some helpful additions which
# change how the server runs.
DEBUG = True
# Turns on any behavior that interacts with Slack (modchat)
ENABLE_SLACK = False
# Enables reddit instances for Blossom and the logged-in user + social auth
ENABLE_REDDIT = False
# Ping ocr.space with content for OCR goodness?
ENABLE_OCR = False
# Enable or disable access to the transcription app side entirely.
ENABLE_APP = False
# make it so that using the API does not require username / password / api key
OVERRIDE_API_AUTH = True
# By default, the app will only pull things from the latest 18 hours, but test
# data doesn't always play along.
OVERRIDE_ARCHIVIST_DELAY_TIME = 500 # hours
# Flip between these depending on what you're working on -- if you don't need
# domain-specific functionality, just leave them both commented out.
# OVERRIDE_HOST = "thetranscription.app"
# OVERRIDE_HOST = "grafeas.org"
ALLOWED_HOSTS = ['*']
CACHES = {
'default': {
'BACKEND': 'django.core.cache.backends.dummy.DummyCache',
}
}
# We deploy to postgres, but developing against sqlite3 will work in almost all
# cases. Just be aware of potential issues where sqlite3 and postgres do not
# play well together -- namely, django migrations for sqlite3 will allow a
# field creation and field alter call in the same transaction. Postgres... will
# not.
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.sqlite3',
'NAME': os.path.join(BASE_DIR, 'db.sqlite3'),
}
}
LOGGING = {
'version': 1,
'disable_existing_loggers': True,
'handlers': {
'console': {
'class': 'logging.StreamHandler',
},
},
'loggers': {
'django': {
'handlers': ['console'],
'level': os.getenv('DJANGO_LOG_LEVEL', 'INFO'),
},
'blossom': {
'handlers': ['console'],
'level': os.getenv('DJANGO_LOG_LEVEL', 'DEBUG')
}
},
}
MIDDLEWARE = ["blossom.middleware.BetterExceptionsMiddleware"] + MIDDLEWARE
IMAGE_DOMAINS += ['images.dog.ceo'] # the image API we use for dev dataThis file will be ignored by git, so make any changes you need to while developing.
Blossom uses pre-commit to help us keep everything clean. After you check out the repo and run poetry install, run pre-commit install to configure the system. The first time that you run git commit, it will create a small venv specifically for checking commits based on our toolset. All of these are installed as part of the regular project so that you can run them as you go -- don't get taken by surprise when you go to commit! The toolchain as written invokes the following tools:
- seed-isort-config
- This sets .isort.cfg with all of the third-party modules that are in use.
- isort
- Searches Python files for imports that are in the wrong order, then offers you the option of fixing them.
- black
- Opinionated code formatter; automatically fixes issues.
- flake8
- formatting checker and linter; does not automatically fix issues.
If an issue is detected when you run git commit, the action will be aborted and you'll receive a message about what needs to be fixed before committing.
-
Minimum Python version: 3.8
-
Install dependencies with
poetry install. Don't have Poetry? Info here: https://python-poetry.org/ -
Create your database with
python manage.py migrate. -
Run
python manage.py bootstrap_siteto prepopulate the site with the base posts. This will also create a base user account that you can use to make another user for yourself. -
Run
python manage.py generate_dev_dataif you're doing local development - this will create a bunch of dummy material for you to work with.
Start the server with python manage.py runserver, navigate to http://localhost:8000/login/, and log in with
username: [email protected] and password: asdf
You can use the above credentials to create yourself a new account.
- Navigate to http://localhost:8000/superadmin/newuser and log in with the above credentials.
- Create a personal user account with the requested fields. Make sure that you select "is superuser".
Next, we'll disable the default admin account.
- Navigate to
http://localhost:8000/superadmin/blossom/blossomuser/and click on the "admin" user. - Scroll to the bottom of the page and deselect "Active".
- Click Save.
You are now the only admin for the site. Other users must be added through the original form that can be accessed through the link above.
Run the server with python manage.py runserver. Note: you should see in your logs "Found local_settings.py -- loading and using!" twice. This is due to how Django's hot reloading feature works; it uses two threads, and each thread will trigger the message. This is expected.
Run python manage.py makemigrations blossom && python manage.py migrate
Run python manage.py collectstatic and answer 'yes' -- this will populate the /static/ endpoint with everything it needs. This is not needed in development, but without it nothing from the static folders will be served properly. It will create a new folder called 'static' in the application root, which is why the staticfiles development side is called 'static_dev'.
Run python manage.py bootstrap and see above for expected user credentials and user configuration.
Site root.
API root.
The processing url for Stripe.
Used by Bubbles for site isup checks.
General site administration, open to all user accounts.
User / post traditional admin. Requires staff acount.
Create a new user for the site.
Create a new post for the site.
The swagger API endpoint list.
The same thing as swagger, just with a different layout.