ERPNext & Frappe
Deploying, extending and running ERPNext and the Frappe framework in production - for developers and the businesses that depend on it.
Sub-topics
Installation & Setup
28Getting a real, production-ready ERPNext or Frappe bench up and running.
Upgrades & Migration
7Moving between versions, migrating sites, and the things that break when you do.
Custom App Development
8DocTypes, hooks, scripts, permissions and the framework internals you build on.
Troubleshooting
12The errors, the failed migrations and the 2am fixes.
ERPNext for Business
61ERPNext framed for owners and operators - decisions, cost and getting value.
Inventory & Operations
16Stock, warehousing and the operational side of running ERPNext.
124 articles · showing 1-9 (page 1 of 14)
One tap at the till, five documents: the submit chain behind ERPNext retail
I recorded an hour and twenty minutes of UpeoRetail and refused to cut the boring parts, because the eight seconds at the counter is the easy bit. What one submit really writes: stock ledger, GL, a serial and batch bundle, a payment, and two integrations that live outside the transaction.
Deploying Frappe apps to a client server you're not allowed to touch
The client will not give you access to their dev server, so every code change means someone on their side pulls and migrates by hand. Here is the complete fix: a self-hosted runner they install, a deploy script they own, and no credential to their environment on your side at all.
Bolting a phone onto ERPNext: custom routes, guest endpoints and HMAC auth in Frappe
Frappe claims every /api/* path before website routing, so a fixed third-party path 404s. Here is the before_request rewrite that fixes it, including the cached property you also have to bust, and why allow_guest endpoints can still be strongly authenticated.
The pull model: systemd timers and release polling
When the client's security team refuses a runner outright, you can still ship. A systemd timer on their server asks GitHub what the latest release is, compares it against what is checked out, and deploys when they differ. Nothing external can execute anything.
SSH deployment for Frappe: how it works, and what it costs you
SSH deployment is the right answer when you own the server, and here is a complete working pipeline for it. It is also a private key held by a third party's CI system, which is a bill worth reading before you sign it.
What bench migrate actually does, and the rollback you'll wish you had
Every patch commits as it completes and records itself as applied. So a migration that fails halfway is not a failed migration, it is a half-finished one, and re-running will not undo it. Here is the recovery, with real commands.
Anatomy of a Frappe bench
Five directories, one of which is not a directory at all but a collection of independent git repositories. Understanding that is the difference between a deploy that works and a Saturday spent fixing file ownership.
Access is a liability, not a convenience
Every SSH key you hold on a client's server is a credential you now have to defend, insure and explain. The strongest position in an enterprise procurement conversation is not having it at all.
ERPNext Partner Kenya: Why Businesses Trust Upeosoft
Choosing an ERPNext implementation partner in Kenya decides whether your ERP runs the business or haunts it. Here is how Upeosoft delivers ERPNext as an operations project, not a software install - and why 200+ systems later, clients stay.