Procurexbundle
- Author: QuantbitERP
- Repository: https://github.com/QuantbitERP/ProcurexBundle
- GitHub stars: 0
- Forks: 1
- License: MIT
- Category: Other
- Maintenance: Actively Maintained
Install Procurexbundle
bench get-app https://github.com/QuantbitERP/ProcurexBundle
Add the Frappe Gems badge to your README
Maintain Procurexbundle? Paste this into your README:
[](https://frappegems.com/gems/apps/QuantbitERP/ProcurexBundle)
About Procurexbundle
ProcureX Bundle
One Frappe app that pulls in both halves of ProcureX and wires them together:
- Backend — ProcureX-Backend (
procurex), fetched withbench get-appand installed on the site. - Frontend — ProcureX, cloned, built as a static SPA and served by Frappe itself at
/procurex.
Installation
cd $PATH_TO_YOUR_BENCH
bench get-app https://github.com/jp-1709/ProcurexBundle.git
bench --site install-app procurex_bundle
That is the whole setup. install-app will:
bench get-appthe backend repo intoapps/procurex(if it is not there already) and installprocurexon the site,- clone the frontend into
apps/procurex_bundle/frontend/ProcureX, npm installand build it intoapps/procurex_bundle/procurex_bundle/public/procurex,- serve it at
https:///procurex.
Requirements on the bench host: git, and Node.js 20.19+ / 22.12+ with npm (the frontend uses Vite 8). The frontend build takes a few minutes.
How the two halves connect
The SPA is built with vite base = /assets/procurex_bundle/procurex/ and the TanStack router basepath = /procurex, and Frappe serves the prerendered shell for /procurex/* through a page renderer. Because the SPA is served by the site itself, its relative /api/... calls land on the same Frappe site with the session cookie already attached — no Node server, no PM2, no extra port, no reverse-proxy rules. The renderer also injects window.csrf_token (and a csrf_token cookie) so writes pass Frappe's CSRF check.
The frontend repository is never patched: the build uses frontend/procurex-bundle.vite.config.ts from this app, passed to vite build --config.
Commands
# rebuild the frontend (e.g. after changing branches or a failed install)
bench --site procurex-bundle-build-frontend [--update] [--clean]
# fetch + install the backend app only
bench --site procurex-bundle-setup-backend
Configuration
Optional overrides in site_config.json / common_site_config.json:
| Key | Default |
|---|---|
procurex_bundle_backend_repo |
https://github.com/QuantbitERP/ProcureX-Backend.git |
procurex_bundle_backend_branch |
version-16 |
procurex_bundle_frontend_repo |
https://github.com/QuantbitERP/ProcureX.git |
procurex_bundle_frontend_branch |
main |
procurex_bundle_node_bin |
— (directory containing node/npm, when not on PATH) |
procurex_bundle_skip_frontend_build |
false (skip the build during install-app) |
License
MIT
Related Other apps for Frappe & ERPNext
- Erpnext — Free and Open Source Enterprise Resource Planning (ERP)
- Helpdesk — Modern, Streamlined, Free and Open Source Customer Service Software
- Print Designer — Visual print designer for Frappe / ERPNext
- Ctr — CTR模型代码和学习笔记总结
- Whitelabel — Whitelabel ERPNext
- Fossunited — fossunited.org
- Helm — Helm Chart Repository for Frappe/ERPNext
- Frappe Attachments S3 — A frappe app to upload file attachments in doctypes to s3.