FAQ

Frequently Asked Questions#

How to update the Platfone NodeJS Backend?#

To update the Platfone NodeJS Backend, pull the latest changes from the repository and redeploy the server.

Where can I find logs for the Platfone NodeJS Backend?#

Logs are written to stdout/stderr. Depending on your deployment setup, you can view logs using:

• PM2: pm2 logs platfone-nodejs-backend
• Docker: docker logs <container_name>
• Systemd: journalctl -u platfone-nodejs-backend -f

Where can I find variables and secrets that the Platfone NodeJS Backend uses?#

Environment variables and secrets are managed via your .env file or your deployment environment configuration (e.g., Docker, systemd, or cloud key vault).

Which resources does the Platfone NodeJS Backend use?#

1. NodeJS Server: Runs the application logic for HTTP endpoints, authentication, and webhook handling.
2. MySQL (MariaDB) Database: Stores customer, payment, and activation data.
3. Payment Gateways: Processes external payment and refund webhooks.
4. Firebase: Used as authentication provider and for sending notifications.

Can I use another database instead of MySQL?#

Yes. The Platfone NodeJS Backend is designed to be customizable and can be extended to support other databases. However, the default implementation uses MySQL (MariaDB) for its simplicity and compatibility with the provided migrations. For more information please refer to https://lucid.adonisjs.com and https://lucid.adonisjs.com/docs/installation for database configuration. (sqlite, postgres, mssql are officially supported by AdonisJS Lucid ORM).

Can I use another payment gateway instead of Stripe or PayPal?#

Yes, you can implement custom payment gateways by creating a webhook handler that processes incoming payment events and updates the database accordingly. For more information, refer to the Configure payment gateways section.

Can I use another authentication provider instead of Firebase?#

Yes, you can implement custom authentication providers by creating a new authentication strategy that integrates with your desired provider. The backend is open-source and designed to be extensible, allowing you to add support for other authentication methods as needed.