a Django-based indieweb.org site https://00dani.me/
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Danielle McLean 9586f59592
Write a big ol' README.md
5 years ago
entries Satisfy autopep8 by adding a newline between two methods 5 years ago
home Nicely handle the unlikely case where the h-card contains absolutely no PGP keys and/or social profiles 5 years ago
lemonauth Throw away now-unused lemonauth templates, since they've all been ported across to Jinja2 5 years ago
lemoncurry Fix URL syntax for linking to the current lemoncurry version in the repo, so it works with Gitea 5 years ago
lemonshort Install mypy and make the minimum changes necessary for it to pass, albeit using --ignore-missing-imports 5 years ago
micropub Add a Link header to the Micropub create response indicating the entry's shortlink 5 years ago
users Add caching and smarter resizing to the Libravatar endpoint 5 years ago
webmention Add docstring to webmention:status endpoint 5 years ago
wellknowns Replace the previous WebFinger implementation with a fairly simple forwarder to Bridgy Fed, so that Bridgy Fed will work eventually 5 years ago
.gitignore Install mypy and make the minimum changes necessary for it to pass, albeit using --ignore-missing-imports 5 years ago
.gitlab-ci.yml Simplify the GitLab cache config, should be more reliable this way? 5 years ago
.gitmodules Load the Material colour scheme directly from the source YAML, rather than hardcoding it into Stylus format 6 years ago
.pre-commit-config.yaml Add pytest and mypy steps to the pre-commit hooks to avoid committing clearly broken code 5 years ago
.pyup.yml Configure pyup to look at my Pipfiles 5 years ago
.travis.yml Explicitly mark the environment variables as global 5 years ago
Forwardfile Add a Forwardfile for development 6 years ago
LICENSE Extend the copyright range in the license to cover 2018 as well 5 years ago
Pipfile Install mypy and make the minimum changes necessary for it to pass, albeit using --ignore-missing-imports 5 years ago
Pipfile.lock Bump library versions using pipenv lock 5 years ago
README.md Write a big ol' README.md 5 years ago
lemoncurry.paw Create a basic but functional micropub media endpoint :o 5 years ago
lemoncurry.svg Add the lemoncurry logo - yes, it's just FA's lemon layered over a dark circle 5 years ago
manage.py Make development-specific settings file 6 years ago
package.json Relocate official repository to git.00dani.me 5 years ago
pytest.ini Add support for tests that use django.test.Client and that require a database, and use this support to test some of the wellknowns.views modules 5 years ago
yarn.lock Bump npm library versions using yarn upgrade 5 years ago


lemoncurry (always all-lowercase) is a Django-based personal site designed to operate as part of the IndieWeb. It currently supports the following IndieWeb specifications natively.

  • All content is exposed using standard microformats2 markup, making it easy for other sites and applications across the IndieWeb to consume.
  • Additionally, the site owner's profiles are exposed using rel-me, enabling independent verification of their identity across various services. This permits IndieAuth.com to authenticate the site's owner using a social profile, such as a Twitter account. However, this functionality is not necessary because lemoncurry also fully implements…
  • IndieAuth, an protocol derived from OAuth 2.0 which enables the site's owner to authorise access to their domain directly from the lemoncurry site itself. Additionally, tokens for further access to the lemoncurry site may be requested and issued, including customisable token scope as in OAuth.
  • Micropub is partially supported - using a token obtained through IndieAuth, clients may post new content to the lemoncurry site using either the form-encoded or JSON request formats. There is currently no support for updating or deleting existing content through Micropub, although this is of course planned.
  • Webmention, used to enable rich commenting and social interaction between separate IndieWeb sites, is partially supported. lemoncurry will correctly send webmentions to all URLs mentioned in a published entry. However, it currently does not expose an endpoint for receiving webmentions.
  • WebSub is also partially supported. When content is posted through Micropub, WebSub is pinged as it should be - however, since only creating new content through Micropub is supported, updates do not currently cause a WebSub ping.


lemoncurry uses the following tools:

  • Pipenv - developed with Pipenv 2018.5.18, but should work with most versions.
  • Yarn - again, developed with Yarn 1.7.0, but should work with most versions.

As well as the following services:

  • PostgreSQL - create a database named lemoncurry. Socket auth is recommended, so ensure the UNIX user you'll be running lemoncurry with has access to that database. Alternatively, set the POSTGRES_PASSWORD environment variable to use password auth.
  • Redis - lemoncurry expects to find Redis on port 6380, rather than the standard port of 6379. Sorry about that.

If you're running in production, I'd recommend Gunicorn, which is already part of lemoncurry's Pipfile. Ensure you run Gunicorn behind a secure reverse proxy, such as Nginx.

If you're running in development, the usual Django run_server command should be fine.


Clone the repo, and then install both Python and Node dependencies:

$ git clone https://git.00dani.me/00dani/lemoncurry
$ cd lemoncurry
$ pipenv install
$ yarn install

Once those steps complete, you should be able to perform the usual Django steps to get a development server up and running. (If you'd prefer, you can use pipenv shell to activate lemoncurry's virtualenv, rather than prefacing each command with pipenv run. I like being explicit.)

$ pipenv run ./manage.py migrate
$ pipenv run ./manage.py collectstatic
$ pipenv run ./manage.py runserver 3000