CodeIgniter projects are usually simpler to deploy than full framework stacks, but the correct public folder and configuration still matter.

Create

1. Create the website/domain in the hosting panel.
2. Upload the project files with File Manager, FTP, or Git if available.
3. For CodeIgniter 4, point the document root to the project's public folder.
4. For older CodeIgniter projects, confirm whether index.php, application, and system are expected under the current web root.
5. Create a database if the application needs one.
6. Update .env or the database config with the correct database credentials.
7. Check that the PHP version matches the application requirements.
8. Issue SSL and test the main pages, forms, and login flow.

If the application uses writable cache, session, or upload folders, confirm those folders can be written by the web server.

Manage

• Use File Manager or FTP for code and asset updates.
• Use phpMyAdmin for database exports/imports and careful checks.
• Keep the base URL, database settings, and writable folders aligned with the live domain.
• Open a support ticket for document-root, PHP version, SSL, or rewrite-rule changes you cannot access.

Delete

1. Back up files and database first.
2. Remove the website/subdomain if your account has permission, or request deletion from support.
3. Delete unused application files, databases, database users, FTP accounts, and DNS records.
4. Ask support to remove custom rewrite or vhost rules if any were added for the app.

Troubleshooting

• If routes return 404, check rewrite rules and the document root.
• If the app shows database errors, verify the database credentials and hostname.
• If sessions or uploads fail, check writable folder permissions.
• If only some pages fail, check whether the base URL is set correctly for the domain.
• When opening a ticket, include the CodeIgniter version and the exact failing URL.