TL;DR — We deployed the entire MyZubster ecosystem on an Aruba VPS: Gateway (Monero payments) + Marketplace + Security Bot, fixed port conflicts, configured PM2, connected all services, and created a GitHub Project for tracking. The system is now live in production and ready to scale.
🧱 Architecture Overview
MyZubster is a decentralized ecosystem made of:
Gateway (Node.js + Express) — handles Monero payments, JWT authentication, webhooks, and transaction monitoring
Marketplace (Node.js + SQLite) — manages users, products, orders, and reputation
MoneroService — connected to the Monero daemon on mainnet
PaymentMonitor — automatically scans pending payments every 30 seconds
Telegram Bot — sends notifications and interacts with users
Databases:
MongoDB for the Gateway
SQLite for the Marketplace
🧭 Initial State
Before we started, the situation was:
Service Status Port
Gateway ❌ crashed 3000
Marketplace ❌ down –
PaymentMonitor ❌ inactive –
PM2 ❌ missing –
GitHub Project ❌ missing –
The Gateway failed to start because port 3000 was already occupied by another service (tokenization-singapore).
The Marketplace was stopped and pointed to the Gateway at http://localhost:3001 — but the Gateway actually needed to run on a different port.
🛠️ What We Did
1️⃣ Changed the Gateway Port
We updated the .env file:
bash
PORT=3000 → PORT=3002
2️⃣ Started the Gateway with PM2
bash
pm2 start server.js --name myzubster-gateway
Health check active:
bash
curl http://localhost:3002/health
3️⃣ Found and Started the Marketplace
The Marketplace was located in /root/MyZubster-Marketplace.
bash
pm2 start server.js --name myzubster-marketplace
4️⃣ Fixed the Gateway URL in the Marketplace
We updated line 11 in server.js:
js
const GATEWAY_API_URL = 'http://localhost:3001';
to:
js
const GATEWAY_API_URL = 'http://localhost:3002';
5️⃣ Restarted the Marketplace with Updated Environment
bash
pm2 restart myzubster-marketplace --update-env
6️⃣ Verified Communication Between Services
bash
curl http://localhost:4000/api/health
curl http://localhost:3002/health
Both returned successful JSON responses.
7️⃣ Saved PM2 State for Auto-Restart on Boot
bash
pm2 save
pm2 startup
8️⃣ Created a GitHub Project for Tracking
We manually created a new GitHub Project to manage issues, milestones, and roadmap:
🔗 https://github.com/users/DanielIoni-creator/projects/1
✅ Final System Status
Service Status Port Health Check
Gateway ✅ online 3002 http://localhost:3002/health
Marketplace ✅ online 4000 http://localhost:4000/api/health
PaymentMonitor ✅ active – scans every 30 seconds
MongoDB ✅ connected 27017 –
SQLite ✅ active – –
PM2 ✅ saved – auto-start on reboot
GitHub Project ✅ created – active tracking
🧪 Quick Test Commands
bash
Gateway
curl http://localhost:3002/health
Marketplace
curl http://localhost:4000/api/health
Expected output:
json
{
"status": "OK",
"message": "MyZubster Gateway is running!",
"timestamp": "2026-07-29T15:37:32.747Z",
"version": "1.0.0"
}
and
json
{
"status": "ok",
"timestamp": "2026-07-29T15:37:32.732Z",
"service": "MyZubster-Marketplace",
"version": "1.0.0",
"database": "sqlite"
}
🎯 Next Steps
Configure Nginx with SSL to expose services on a custom domain
Set up automated database backups (MongoDB + SQLite)
Implement GitHub Actions for continuous deployment
Add new services (Ethereum, NFT, DAO)
🙌 Contribute
The project is open source and contributions are welcome!
Gateway Repo: https://github.com/DanielIoni-creator/MyZubsterGateway
Marketplace Repo: https://github.com/DanielIoni-creator/MyZubster-Marketplace
GitHub Project: https://github.com/users/DanielIoni-creator/projects/1
🏁 Conclusion
In just a few hours, we went from a broken system to a fully functional, production-ready ecosystem.
All services are communicating, the PaymentMonitor is active, and everything is persistent thanks to PM2.
MyZubster is now ready to grow! 🚀
✍️ Written by Daniel Ioni — developer and enthusiast of decentralized technologies.
Top comments (0)