Knowledge Base

How to create, manage, and delete application services

This article explains the normal lifecycle for Node.js, Laravel, CodeIgniter, WordPress, and similar application services on Idea Comindo hosting.

Important: Some accounts can manage files, databases, FTP, SSL, and backups, but cannot create, modify, or delete websites directly. If the button or menu you need is not visible in the hosting panel, open a support ticket and we will do that step for you.

Create a service

  1. Decide the domain or subdomain that will run the application, such as app.yourdomain.com or yourdomain.com.
  2. Create the website/subdomain in the hosting panel if your account has permission. If not, request it from support.
  3. Create a database and database user if the application needs one.
  4. Upload the application files with File Manager, FTP, or Git if available.
  5. For WordPress, use the WordPress installer/manager if it is available, or upload WordPress manually.
  6. For Laravel and CodeIgniter, make sure the domain points to the correct public folder, such as public for Laravel and CodeIgniter 4.
  7. For Node.js, send support the project folder, startup command, environment variables, and preferred public URL so we can run it with PM2 and connect it through the web server.
  8. Issue SSL and test the site before announcing it as live.

Manage a service

  • Use File Manager or FTP for file uploads and small changes.
  • Use Databases and phpMyAdmin for database checks, exports, and imports.
  • Use SSL tools to issue or renew HTTPS certificates.
  • Use Backups before plugin, theme, framework, package, or database changes.
  • Use the WordPress dashboard or WordPress Manager for WordPress updates when available.
  • For Node.js restarts, PM2 changes, environment variables, queue workers, or reverse proxy changes, open a support ticket.

Delete a service

  1. Confirm the service is no longer needed and take a final backup of files and database.
  2. Export any database or uploaded content you may need later.
  3. Remove DNS records only after you are sure the service should stop receiving traffic.
  4. Delete application files only after backup confirmation.
  5. Delete unused databases, database users, FTP accounts, and email accounts connected to the service.
  6. For WordPress, remove the site from WordPress Manager if available, then remove files and database that are no longer needed.
  7. For Node.js, ask support to stop and delete the PM2 process and remove the reverse proxy rule.
  8. If your account cannot delete the website/subdomain from CyberPanel, open a support ticket with the domain and deletion request.

Deletion can be permanent. If you are unsure, ask support to suspend or disable the service first instead of deleting it immediately.

Please rate this article to help us improve our Knowledge Base.

0 0