aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/protoc.py (unfollow)
Commit message (Collapse)AuthorLines
2022-05-30Specify wsgi_app in Gunicorn configGravatar MarkKoz-2/+3
2022-05-30Remove redundant module for creating the WSGI appGravatar MarkKoz-6/+3
2022-05-30Make Sentry SDK and gunicorn optional dependenciesGravatar MarkKoz-8/+14
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.
2022-05-30Move logging code to separate utility modulesGravatar MarkKoz-49/+72
2022-05-30Move coverage config into pyproject.tomlGravatar MarkKoz-13/+16
2022-05-30Tweak Makefile formatGravatar MarkKoz-2/+1
2022-05-30Add a pyproject.tomlGravatar MarkKoz-14/+52
2022-05-29Rebuild the container before running the test commandGravatar MarkKoz-0/+1
Ensure the dependencies are up-to-date in the dev container.
2022-05-29Fix 415 error response titleGravatar MarkKoz-2/+2
The update to Falcon v3 changed its capitalisation.
2022-05-29Fix paths to files in CONTRIBUTING.mdGravatar MarkKoz-2/+2
2022-05-29Fix deprecation warning from FalconGravatar MarkKoz-1/+1
The update to v3 deprecated falcon.API in favour of falcon.App.
2022-05-29Remove redundant numpy install in test commandGravatar MarkKoz-1/+1
It's already installed by the container since Docker Compose is configured with the DEV arg.
2022-05-29Deps: use pip-tools instead of PipenvGravatar MarkKoz-453/+217
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.
2022-05-28CI: only show pre-commit log if it existsGravatar MarkKoz-1/+5
2022-05-28Deps: specify flake8 deps via pre-commitGravatar MarkKoz-335/+164
2022-03-12Replace ASCII diagram with mermaid sequence diagramGravatar Mark-14/+15
2022-03-05Move community health files to .github dirGravatar MarkKoz-4/+5
Merge DEVELOPING.md into CONTRIBUTING.md
2022-02-13CI: define KUBECONFIG secret as required in build workflowGravatar MarkKoz-0/+3
2022-02-13CI: pass KUBECONFIG secret to build workflowGravatar MarkKoz-0/+2
Reusable workflows don't have access to secrets, even in this case where the workflow is local.
2022-02-13CI: remove unnecessary shell option from scriptGravatar MarkKoz-1/+1
There are no pipes the in script, so the presence of -o pipefail may confuse readers.
2022-02-13CI: replace "artefact" with "artifact"Gravatar MarkKoz-19/+19
The latter is consistent with GitHub Action's documentation.
2022-02-13CI: remove region commentsGravatar MarkKoz-4/+0
There isn't enough "meat" to warrant their use.
2022-01-15Fix typo in commentGravatar Mark-1/+1
Co-authored-by: wookie184 <[email protected]>
2021-12-28Store relative paths in coverage dataGravatar MarkKoz-7/+6
Also remove the reliance on the container needing to mount the host's files to the same directory during local testing. Fix #135
2021-12-27CI: rename jobsGravatar MarkKoz-10/+6
2021-12-27CI: clean up Docker stuff in self-hosted runnerGravatar MarkKoz-8/+14
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.
2021-12-27Change entrypoint tests to integration testsGravatar MarkKoz-35/+25
No more mocks!
2021-12-27CI: fix pre-commit logs step conditionGravatar MarkKoz-1/+1
The step was running even if the pre-commit hooks step never ran.
2021-12-27CI: fix flake8 being skippedGravatar MarkKoz-0/+7
2021-12-27CI: run linters outside the containerGravatar MarkKoz-36/+44
Remove the dependency on the container so the lint job can run in parallel with the build job. More time has to be spent installing Python dependencies, but this is made up for by not having to download and load the image artefact in addition to not having to wait for the build job.
2021-12-27CI: specify service name to coverallsGravatar MarkKoz-1/+1
See https://github.com/TheKevJames/coveralls-python/issues/240
2021-12-26CI: remove SHA from image build GHA cache scopeGravatar MarkKoz-1/+1
Unlike the cache action, the build-push action's GHA cache feature seems to only do an exact comparison for the scope. Thus, new commits lead to cache misses.
2021-12-26CI: combine coverage data from all matrix jobsGravatar MarkKoz-21/+39
2021-12-26CI: pass artefact name as an input to workflowsGravatar MarkKoz-10/+28
Make the artefact and file names identical to simplify things. The artefact name doesn't have to be unique anyway since it can only be downloaded by the same workflow run.
2021-12-26CI: use buildx's integrated GH Actions cache featureGravatar MarkKoz-12/+18
2021-12-26CI: use build-push-action to output an image tarballGravatar MarkKoz-4/+1
load: true was already creating a tarball, but it was getting immediately loaded. Since no other Docker builds run in this job, it's useless to load it. The action can still be leveraged to create the tarball instead of manually invoking `docker save`.
2021-12-26CI: use reusable workflows as jobs in main workflowGravatar MarkKoz-242/+27