Welcome
Let's set up FaithCode Help Desk
AI-powered helpdesk & customer support ticketing. This wizard walks you through checking your server, verifying your purchase, and configuring your database and admin account — no command line required.
We detected your browser language automatically — change it if needed.
Step 1 of 6
Server requirements
FaithCode Help Desk needs PHP 8.3.0+ and these extensions enabled.
We check this automatically — nothing to configure here. A green ✓ means that item is ready; a red ✕ means your host needs to enable it (usually a one-line change in php.ini, or a toggle in cPanel → "Select PHP Version" → Extensions).
- PHP version
Hosting diagnostics
These checks help on shared hosting and VPS panels. Warnings do not block installation — they explain what to configure next. A failing document root check does block installation until it is fixed.
Step 2 of 6
File permissions
These paths must be writable by your web server user.
"Writable" means PHP is allowed to create and edit files in that folder — FaithCode Help Desk needs this to save your .env configuration, cache pages, and store uploads. If a row shows ✕, copy its chmod command into your host's File Manager "Change Permissions" dialog (or run it over SSH/terminal if you have one), then re-check.
-
Run:
Step 4 of 6
Database connection
Enter the database FaithCode Help Desk should use. Ask your host for these details if you're unsure.
The server your database runs on. Usually 127.0.0.1 or localhost on shared hosting — check your host's control panel if unsure.
Leave the default unless your host told you to use a different port.
The database user your host created — this is not your hosting/cPanel login.
The password for the database user above. This is stored only in your .env file, never shown again.
"Test Connection" just checks these details work — nothing is saved or changed until you click Next.
Step 5 of 6
Application & admin account
This is the last thing we need before installing.
Application settings
Shown in the browser tab, emails, and login page — you can change this later in Admin → Settings.
https://support.yourcompany.com. We've pre-filled this from the domain you're installing on — only change it if that's wrong.
Used to display dates and times correctly for your team.
The default language for new users — everyone can pick their own later.
You can configure this later in Admin → Settings → Mail.
smtp.gmail.com or mail.yourdomain.com.
587 (TLS) or 465 (SSL) — check with your mail provider.
Usually the full email address you're sending from.
Your mailbox password, or an app-specific password if your provider requires one (e.g. Gmail).
support@yourdomain.com.
Super admin account
This creates your first login — you'll have full access to every setting, ticket, and user once installed.You'll use this to log in — make sure it's an address you can access.
Demo content
Step 6 of 6
If installation failed after database tables were created, retrying is safe when you use a table prefix. Your database may already contain partial tables; the installer cleans only FaithCode Help Desk tables for this prefix before trying again. The install lock has not been written yet.
Technical details
You're all set!
FaithCode Help Desk has been installed successfully.
Finish setup on your server
1. Add a cron job (required)
Schedule Laravel once per minute so emails, live chat timeouts, and update checks keep running. After login, you can also review these commands under Admin → Settings → Cron Jobs:
* * * * * cd /home/faithcod/helpdesk.faithcode.tech && /usr/local/bin/lsphp artisan schedule:run >> /dev/null 2>&1
2. Process the queue (required for notifications & updates)
On shared hosting, add a second cron with flock. On VPS, use Supervisor:
* * * * * flock -n /tmp/unexgendesk-queue.lock /usr/local/bin/lsphp /home/faithcod/helpdesk.faithcode.tech/artisan queue:work database --stop-when-empty --queue=update-center,notifications,default --tries=3 --timeout=1800
3. Enable HTTPS
Turn on SSL in your hosting panel, then confirm APP_URL uses https:// in Admin → Settings.
The installer route is locked by storage/installed.lock. Keep that file in place — you do not need to delete an /install directory (installation is a route, not a folder).