Backend
Why cPanel keeps Nepal backends small
Shared hosting is a classroom leftover.
IT colleges in Nepal still demo phpMyAdmin. Agencies still sell cPanel as backend. Then the first real traffic spike locks the table and nobody has a restore. I run PostgreSQL because I can explain the backup, the migration, and the fail path. That is the backend practice.
PostgreSQL docs are the same in Kathmandu as in Berlin. The lag is confidence, not fiber. cPanel hides the engine until it explodes.
OpenListener uses Node and Python against one database. Not because of a tweet. Because one product had two jobs: request path and a slower worker. Node and Python in one product is that diary.
Backend
What uptime actually means from Kathmandu
99.9% is a restore drill, not a badge.
Uptime is not a green icon in a client Slack. It is whether the API answers when a booking hits at 11pm. I watch process health, disk, and migration lock. Docker means I can rebuild the box. Railway documentation is how that box often lives.
Shared MySQL on a cheap plan will share noisy neighbors with you. Fine for a college project. Not fine for a product that takes money. Say the constraint out loud before you work with someone.
If a studio cannot name the last restore, they do not have a backend. They have a panel login.
Backend
How I move a Nepal site off cPanel
Dump, transform, cut over, watch.
Export. Map types. Load into PostgreSQL. Run the app against staging. Cut DNS when the numbers match. Keep the old panel cold for a week. Boring on purpose.
Email and DNS often live next to that panel. Do not move the database and forget MX. What a mail server is is the sibling lesson. Search dies when mail dies too, because founders panic and change the wrong record.
I will not migrate a mystery plugin zoo onto PostgreSQL and call it a product. We delete what the product does not use. That is the actual work.
Backend
Who this is for
Coded clients. Named operator.
If you need a night NOC bench, work with a company. If you need one person who can keep Node, Python, and Postgres honest from Kathmandu, that is this practice. Kathmandu backend uptime is the longer case.
Students: stop putting cPanel on the CV as backend. Put a repo, a schema, and a URL. Learn in Nepal is the map.
Email [email protected] with the current host and the number you care about. p95 or restore time. Not 'make it modern'.