https://github.com/blaggacao/frappix

Frappe on Nix
https://github.com/blaggacao/frappix

erpnext erpnext-customization frappe frappe-framework

Last synced: 6 months ago
JSON representation

Frappe on Nix

• Host: GitHub
• URL: https://github.com/blaggacao/frappix
• Owner: blaggacao
• Created: 2023-07-22T00:56:35.000Z (about 2 years ago)
• Default Branch: main
• Last Pushed: 2025-03-25T13:46:08.000Z (7 months ago)
• Last Synced: 2025-04-12T18:07:37.707Z (6 months ago)
• Topics: erpnext, erpnext-customization, frappe, frappe-framework
• Language: Nix
• Homepage: https://blaggacao.github.io/frappix/
• Size: 640 KB
• Stars: 34
• Watchers: 5
• Forks: 9
• Open Issues: 7
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

          


  

  
Frappix

  
A Frappe Development & Deployment Environment





---

> [!NOTE]

>

> **Guided install**

>

> ```shell

> bash <(curl https://blaggacao.github.io/frappix/install) frappe myproject

> ```

[![Chat on Matrix](https://img.shields.io/matrix/frappix:matrix.org?server_fqdn=matrix.org&style=for-the-badge)](https://matrix.to/#/#frappix:matrix.org)

It is best for now, to join the community in the chat until the docs are more elaborate!

Frappix is a development and deployment environment designed to cover the full software delivery lifecycle from development to deployment and operation for Frappe-based projects.

It is intended for developers and operator alike in their respective role in customer-facing or educational projects.

It can be used in simple scenarios to prototype apps that could later be run on Frappé Cloud but also for very complex production deployments which required extensive customization and fork-like patching of the upstream framework.

### Motivation

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 leverages Nix to achieve (close to) reproducible builds of your deployment artifacts, while Nixpkgs is leveraged for its vast amount of up to date and readily available packages across various language ecosystems.

For example, it is near trivial to set up and run a LLM efficiently via llama.cpp alongside your production setup, while it _is_ trivial to provide a swalwart email service in-scope on the same project, set up a nightly backup with StorJ, tweak your database performance with hugepages, host you plausible analytics instance alongside, or even spin up an entire private chat solution based on the Matrix protocol, etc.

### Battle tested

Frappix, and it's predecessor, has served the author very well during the last year in a complex and highly sofisticated production environment.

Please contact me via the above Matrix Chat or the [Frappé Forum](https://discuss.frappe.io/) if you have any further inquiry.