wec
About
WeatherEye Controller (wec) is a single codebase, implemented using the Python Textualize package, that provides a Command Line Interface (CLI), Text User Interface (TUI) and Web UI for provisioning (Terraform), orchestrating (Ansible) and configuring WeatherEye software on Linux servers.
wec is aware of environments that it can install to including:
- Provisioning
- Infrastructure Providers (e.g. Locally Proxmox or VMWare. Remote: Amazon Web Services, Google Cloud Platform etc. see supported providers
- Orchestrating
- Linux servers (VMs, cloud instances)
- Configuration Management
- WeatherEye Admin Django project (configuring which Django apps are running in a single Django instance)
- Other WeatherEye application configurations
The wec command line tool includes the following modules which can also be accessed through WeatherEye Admin:
- WeatherEye Upgrade
- WeatherEye Rollback
- WeatherEye Backup
Powered by:
- Terraform for server provisioning
- Ansible for server orchestration
- Textualize (MIT) - An application framework for CLI, TUI and WebUI in a single codebase
- pipx - A way to install Python CLI's as a tool in a contained environment
Tests
Run pytest. For more detailed output, including test coverage:
pytest -vv --cov=. --cov-report term-missing
Contributing
If you would like to contribute to the project:
- if you're making code contributions, please try and write some tests to accompany your code, and ensure that the tests pass.
- commit your changes via
cz commit. Follow the prompts. When you're done,pre-commitwill be invoked to ensure that your contributions and commits follow defined conventions. Seepre-commit-config.yamlfor more details. - your commit messages should follow the conventions described here. Write your commit message in the imperative: "Fix bug" and not "Fixed bug" or "Fixes bug." This convention matches up with commit messages generated by commands like
git mergeandgit revert. Once you are done, please send a merge request.
Metadata
Release files for wec 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| wec-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for wec-0.1.0-py3-none-any.whl |
Release files / wec-0.1.0-py3-none-any.whl
| Download URL | wec-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
838bafa2ce266ab6e0d526308d537efac84b5b86f5802a174fc5d8912fe41a4f
|
|
BLAKE2b-256 checksum How to use checksums |
5bb14edc8b8e5addd706a63e71c1e2b317fca59b94a9d3124edfa535fb6a63a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.6
|
Security for wec 0.1.0
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.