n, f, m, c, p, e, and r. What are the meanings and uses of the Frappe Cloud virtual machine series?
Refering to this: Frappe Cloud Infra Architecture, we know:
n => nginx (external facing proxy)
f => frappe / App Server (workers)
m => mariadb / DB Server
4 to go, maybe like this wild guesses
(e.g. more cloud/datacenter oriented, less host oriented):
c => certs / configuration / clowns ?
p => proxy / postgres ?
e => egress / erpnext / exports ?
r => registry / redis / runners ?
Maybe the sources ( GitHub - frappe/press: Full service cloud hosting for the Frappe stack - powers Frappe Cloud) know more.