| Commit message (Collapse) | Author | Lines |
|
|
|
It should be a string, not a list.
|
|
The blacklisted error no longer appears with the default config since
the uid and gid are set.
|
|
|
|
Force the image to be built if it doesn't exist.
|
|
|
|
|
|
Relying more on gunicorn and its config parsing will avoid discrepancies
between the test and production environments.
|
|
|
|
|
|
|
|
|
|
|
|
The env var is no longer used anywhere.
|
|
The last part of the version is the commit count, which relies on the
repo's commit history.
|
|
|
|
Co-authored-by: Matteo Bertucci <[email protected]>
|
|
|
|
|
|
|
|
|
|
Subpackages weren't being included.
|
|
Use the HEAD commit's date as the package's version. Append the number
of commits made on the same date as HEAD to ensure multiple releases on
the same date still have unique versions.
|
|
|
|
|
|
|
|
Falcon provides a WSGI app which can be used by any server, not just
gunicorn. Thus, make gunicorn optional in case the user wants to use
a different server. There shouldn't be any import errors since the class
is now in an isolated module. The only time that module is imported is
when gunicorn loads its config.
Sentry is there for Python Discord mainly, so this dependency shouldn't
be imposed on others.
|
|
|
|
|
|
|
|
|
|
Ensure the dependencies are up-to-date in the dev container.
|
|
The update to Falcon v3 changed its capitalisation.
|
|
|
|
The update to v3 deprecated falcon.API in favour of falcon.App.
|
|
It's already installed by the container since Docker Compose is
configured with the DEV arg.
|
|
Pipenv was limited to only "normal" and "dev" dependencies. pip-tools
is more flexible, since each requirements file can be constrained by
more than one other requirements file. This means CI can choose to only
install coverage deps in the test job and linting deps in the lint job,
but these dependencies will still be constrained by each other and by
other requirements, so a developer will be able to install both sets
simultaneously without conflicts.
Use a Makefile to make up for the loss of Pipenv's scripts
functionality.
|
|
|
|
|
|
|
|
Merge DEVELOPING.md into CONTRIBUTING.md
|
|
|
|
Reusable workflows don't have access to secrets, even in this case where
the workflow is local.
|
|
There are no pipes the in script, so the presence of -o pipefail may
confuse readers.
|
|
The latter is consistent with GitHub Action's documentation.
|
|
There isn't enough "meat" to warrant their use.
|
|
Co-authored-by: wookie184 <[email protected]>
|
|
Also remove the reliance on the container needing to mount the host's
files to the same directory during local testing.
Fix #135
|
|
|
|
Use docker-compose run instead of docker-compose up. This is more
appropriate since the container is only needed for one command. The
latter was actually starting the whole snekbox server. Furthermore,
the former has the --rm option to remove the container when the command
finishes.
As an extra precaution, use docker-compose down in the self-hosted
runner to also remove images, volumes, networks, and any other
containers that were somehow missed. Removing images will also prevent
the disk usage from building up. This is not necessary for the GH-hosted
runner since a new VM is used for each run.
|