# cectf-proxy
You need Python 3 and pip installed to set up this project.
Navigate to the project repository and run ./setup_workspace.sh. This will set up the virtual environment, install the required python dependencies, and set up a default instance/config.py that points to the default cectf-frontend and cectf-server instances running on localhost.
Run sudo run.sh to launch the Flask server. It is configured to run the server on http://127.0.0.1:80 (AKA http://127.0.0.1) by default, and so requires sudo access.
Configuration can be done by adding variables to instance/config.py.
TODO add some tests
For testing, first do pip install pytest coverage. Run pip install -e . to install the project in the local virtual environment (the -e ensures that it is updated as the project is modified). Run pytest to run all tests. Run coverage run -m pytest to generate a code coverage report. Run coverage report to get the report in the command line, or run coverage html to generate an interactive HTML page in htmlcov/index.html.
1 maintainer
Metadata
1 maintainer
Release files for cectf-proxy 1.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cectf-proxy-1.0.5.tar.gz | 3.2 kB | Without provenance | Details for cectf-proxy-1.0.5.tar.gz |
Release files / cectf-proxy-1.0.5.tar.gz
| Download URL | cectf-proxy-1.0.5.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
76fcf18b9ea13d637e4a8b4114a91a78600b7d58cbaf5ec748d154084338f948
|
|
BLAKE2b-256 checksum How to use checksums |
301ce95717c7271d4431b228b87f57b18e86f73c4cea847783b55ca4d16e67ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.35.0 CPython/3.6.7
|
Security for cectf-proxy 1.0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
