aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
...
* Properly escape newlines in docker run commandGravatar Sebastiaan Zeeff2020-11-16-1/+2
|
* Use GHCR containers in DockerfilesGravatar Sebastiaan Zeeff2020-11-16-2/+2
|
* Check out repository to access filesGravatar Sebastiaan Zeeff2020-11-16-0/+5
|
* Trigger workflow on feature branchGravatar Sebastiaan Zeeff2020-11-16-1/+1
|
* Move workflow file to correct locationGravatar Sebastiaan Zeeff2020-11-16-0/+0
|
* Test workflow build strategyGravatar Sebastiaan Zeeff2020-11-16-0/+83
|
* Merge pull request #78 - Update to Python 3.9Gravatar Mark2020-11-15-280/+290
|\
| * Update Python binary mount path in nsjail configGravatar MarkKoz2020-11-14-2/+2
| |
| * Update pipenv in base Docker imageGravatar MarkKoz2020-11-14-1/+1
| |
| * Use flake8 from pipenv when running pre-commit hooksGravatar MarkKoz2020-11-14-12/+7
| |
| * Update to Python 3.9Gravatar MarkKoz2020-11-14-265/+280
|/
* Merge pull request #77 - Add `lark` to available importsGravatar Mark2020-10-30-139/+171
|\
| * re-lock with 'lark'Gravatar decorator-factory2020-10-30-139/+170
| |
| * Update PipfileGravatar decorator-factory2020-10-30-0/+1
|/
* Merge pull request #72 from python-discord/python-LevenshteinGravatar Mark2020-07-31-218/+251
|\ | | | | Add python-levenshtein and sort Pipfile (dev)packages
| * Sort Pipfile packages & dev-packagesGravatar TizzySaurus2020-07-31-19/+19
| |
| * Add python-LevenshteinGravatar TizzySaurus2020-07-31-200/+233
|/
* Merge pull request #70 from neonsea/clarify-readmeGravatar Mark2020-03-29-1/+1
|\ | | | | add --dev flag to readme
| * add --dev flag to readmeGravatar Rasmus Moorats2020-03-29-1/+1
|/
* Merge pull request #69 from python-discord/bug/ci/66/pipenv-run-creates-venvGravatar Mark2020-03-24-17/+17
|\ | | | | Fix venv being created in Dockerfile
| * Fix #66: venv being created in containerGravatar MarkKoz2020-03-23-2/+2
| | | | | | | | | | `pipenv run` creates a venv because it cannot detect that a --system install was done. The solution is to invoke gunicorn directly.
| * Use a config file for gunicornGravatar MarkKoz2020-03-23-9/+6
| | | | | | | | | | This will make it easy to maintain a consistent config without relying on invocation via pipenv.
| * Move snekbox.cfg to a config directoryGravatar MarkKoz2020-03-23-6/+9
|/ | | | | There will be more config files to come so it's cleaner to have them together than littering the root directory with more files.
* Merge pull request #68 from python-discord/feat/doc/57/docker-run-cmdGravatar Mark2020-03-23-32/+29
|\ | | | | Document a simpler way to run snekbox
| * Fix a grammatical error in README.mdGravatar MarkKoz2020-03-23-1/+1
| |
| * Replace NsJail config details with a reference to snekbox.cfgGravatar MarkKoz2020-03-23-29/+3
| | | | | | | | | | | | As convenient as it may be, it is redundant to list out the config in the docs. It also may fall out of sync with the actual config should someone forget to update the docs.
| * Use reference links in README.mdGravatar MarkKoz2020-03-23-7/+18
| | | | | | | | Makes the Markdown less cluttered when editing it.
| * Document a simple way to run the container from Docker HubGravatar MarkKoz2020-03-23-0/+12
|/ | | | | | | | The current run instructions are geared towards developers. A simpler way to run snekbox is to start a container with `docker run` via the image published on Docker Hub. Resolves #57
* Merge pull request #67 from python-discord/update-contribGravatar Mark2020-03-21-23/+36
|\ | | | | Update contributor doc
| * Update contributor docGravatar S. Co12020-03-20-23/+36
|/
* Merge pull request #65 from python-discord/sentry-integrationGravatar Mark2020-03-08-24/+71
|\ | | | | Add sentry integration
| * Relock pipfile.lock with new dependancy.Gravatar scragly2020-03-09-24/+62
| |
| * Update PipfileGravatar Joseph2020-03-08-1/+1
| | | | | | Co-Authored-By: Mark <[email protected]>
| * Add sentryGravatar Joseph Banks2020-03-08-0/+9
|/
* Merge pull request #59 from python-discord/composeGravatar Mark2020-02-28-5/+4
|\ | | | | Use port mapping, change container name to snekbox.
| * Change CI and dev.sh to not use host network mode.Gravatar scragly2020-02-29-2/+0
| |
| * Merge branch 'master' of github.com:python-discord/snekbox into composeGravatar scragly2020-02-29-354/+406
| |\ | |/ |/|
* | Change snekbox timeout to 6 seconds.Gravatar scragly2020-02-29-1/+1
| | | | | | This is to attempt to avoid matching the bot's typing event being resent at the 5 second mark, which seems to be causing it to hang around after the timeout message.
* | Merge pull request #54 from python-discord/ci-improvementsGravatar Mark2020-02-27-212/+219
|\ \ | | | | | | CI Improvements
| * | CI: fix can_pull causing script to exit with code 1Gravatar MarkKoz2020-02-23-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | Error handling is performed inside can_pull so the callers of the function don't always check its exit code. Because set -e present, if can_pull returns 1, bash would consider that function a failed call and thus exit the entire script with code 1. That, in turn, would cause the CI job to fail.
| * | CI: output flake8 to stdout (resolve #37)Gravatar MarkKoz2020-02-22-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Azure website has proven to not be reliable for displaying the JUnit output. Furthermore, some may simply prefer the format of the output in the terminal over the JUnit representation on the Azure site. Nevertheless, the JUnit output isn't that bad (when there's actually a lint error) so it will remain for now. It also provides historical statistics on occurrences of errors, which is kind of cool, I guess...
| * | CI: don't run commands through pipenvGravatar MarkKoz2020-02-22-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since #62, the dependencies have been installed to the system interpreter. Therefore, it's not necessary to run through pipenv to ensure the commands run through an activated virtual environment. This should also fix pipenv run creating a virtual environment. It seems it cannot tell when it should be using the system interpreter. It probably wasn't designed for that anyway i.e. the intent was to run commands directly in such case, which is what this PR will do.
| * | CI: log when the build cache is usedGravatar MarkKoz2020-02-22-0/+1
| | |
| * | CI: fix unbound variable error when checking cacheGravatar MarkKoz2020-02-22-1/+1
| | | | | | | | | | | | The array shouldn't be expanded when testing with -v.
| * | CI: cache the response from Azure APIGravatar MarkKoz2020-02-22-0/+11
| | | | | | | | | | | | | | | | | | The script may need to use the master commit several times. The easiest way to implement the cache was to just cache the response rather than the commit hash.
| * | CI: fix job nameGravatar MarkKoz2020-02-21-1/+1
| | | | | | | | | | | | Hyphens are disallowed so they are replaced with underscores.
| * | CI: merge build job with test jobGravatar MarkKoz2020-02-21-108/+42
| | | | | | | | | | | | | | | * Remove duplicate build steps * Move push steps to a separate YAML file
| * | CI: don't build venv image if it can be pulledGravatar MarkKoz2020-02-21-2/+10
| | |
| * | CI: check if venv image can be pulledGravatar MarkKoz2020-02-21-0/+6
| | |
| * | CI: create a function to check if an image can be pulledGravatar MarkKoz2020-02-21-13/+26
| | |
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-19 12:14:03 +0000