Frappix bridges the gap between system dependencies and such that are already available in Python.
It brings the power of the entire software ecosystem to Frappé, not only the Python ecosystem.
It achieves this by plugging into the one of the biggest software repositories to date.
System dependencies are declared by their identifier in pyproject.toml and are then mapped to their available implementation from the backing software repository.
When a user wants to start working on a project wired with Frappix, it is guaranteed for him to be productive at exactly on command away. Furthermore, the exact same environment used for development is recycled to produce a variety of production grade runtime artifacts, such as:
- MicroVMs
- VMs
- Entire Host Operating System (fully configured)
- OCI Containers
Whatever deployment scenario can be supported by this infrastructure.
The purpose, hence, of this work is to expand the unified experience of the Frappé ecosystem beyond its current boundary which it inherits from its language ecosystems.
- Quality assured and continually maintained onboarding story into the Frappé framework
- A comprehensive development environment for Linux & macOS (Windows on WSL2, only)
- Fully supported deployment targets: VM, MicroVM, Host OS, OCI Container
- Appropriate documentation at its layer of the stack with clear interlinking to upstream documentation
- QA further the onboarding experience of the status quo
- Ensure cross-platform support of the development environment
- Implement OCI, MicroVM in addition to the status quo
- Evaluate performance improvements of the associated tooling
- Elaborate user and technical documentation
- Lead developer
- Community contributions welcome!
- Close collaboration with Frappé staff for up streaming necessary changes
- Sometimes a slow turnover of upstream PRs