AssetHub Documentation

Overview

AssetHub is a complete asset management system built with Laravel 11, Vue 3, and Tailwind CSS. Version 3.0 adds a full Translation Editor, custom locales, CSV import/export, and effective timezone/currency localization — on top of v2 batch/lot tracking, allocations, disposals, and public QR handover pages.

Server Requirements

• PHP 8.2 or higher
• MySQL 5.7+ or MariaDB 10.3+
• Composer 2.x
• Node.js 18+ and npm 9+
• Web server: Apache or Nginx

Required PHP Extensions

• OpenSSL, PDO, PDO_MySQL, Mbstring, Tokenizer, XML, Ctype, JSON, GD, Fileinfo

Disk space

~ 200 MB minimum. Allow extra space for asset photos and document attachments.

Installation

Option A — Web Installer (Recommended)

1. Upload the project files to your web server.
2. Point your domain document root to public/.
3. Set permissions: storage/ and bootstrap/cache/ must be writable (chmod 775).
4. Copy .env.example to .env and set APP_KEY (run php artisan key:generate if you have SSH/Terminal, or see cPanel Setup → Step 5 for File Manager alternatives).
5. Visit https://yourdomain.com/install in your browser.
6. Follow the wizard — Requirements → Database → Migrate → Admin Account → Done.

Option B — CLI Installation

# 1. Install dependencies
composer install --no-dev --optimize-autoloader
npm install
npm run build

# 2. Configure environment
cp .env.example .env
php artisan key:generate

# 3. Edit .env to set DB credentials
# DB_HOST, DB_PORT, DB_DATABASE, DB_USERNAME, DB_PASSWORD

# 4. Create database tables and seed initial data
php artisan migrate --seed

# 5. Create storage symlink for uploads
php artisan storage:link

# 6. Cache config for production
php artisan config:cache
php artisan route:cache
php artisan view:cache

# 7. Mark as installed
echo "Installed" > storage/installed.lock

Wizard Step 2 — Database Configuration

When the wizard reaches Step 2, you must enter the MySQL connection details for the database you created in your hosting panel. The database must already exist (it can be empty — the next wizard step will create the tables).

Where to find these credentials by hosting panel

• Hostinger: hPanel → Databases → Management → click your database. The page shows name, username, and a "Show password" button.
• cPanel: cPanel → MySQL Databases. The database list shows names; users are listed below. Use "Change Password" if needed.
• Plesk: Plesk → Databases → click the database name. The detail page shows credentials and offers a password reset.
• DirectAdmin: DirectAdmin → MySQL Management → click the database. Credentials and password reset are on the database detail page.
• External / managed DB: AWS RDS, DigitalOcean Managed Database, etc. Use the custom hostname, port (often 3306 but verify), DB name, user, and password from your cloud console. Make sure the server's IP is whitelisted in the DB firewall.

Common errors and how to fix them

Localhost (Local Development)

Quick guide to run AssetHub on your computer for testing or development before deploying to production. Pick the environment that matches your operating system.

Option 1 — Laravel Herd (Recommended, macOS & Windows)

Laravel Herd is the official local environment from the Laravel team — free, native, no Docker. Bundles PHP 8.2/8.3/8.4, Nginx, and (in Herd Pro) MySQL/Redis.

1. Download and install Laravel Herd from herd.laravel.com.
2. Place the AssetHub project folder inside ~/Herd/ (macOS) or %USERPROFILE%\Herd\ (Windows). Herd auto-creates a .test domain — e.g. http://assethub.test.
3. Open Herd → Sites and confirm PHP version is 8.2 or 8.3. Right-click the site → Secure to enable HTTPS (needed for QR scanner).
4. Create a MySQL database. With Herd Pro, use Services → MySQL → Open in TablePlus. Otherwise install MySQL Community or use SQLite (DB_CONNECTION=sqlite, touch database/database.sqlite).
5. Copy .env.example to .env, fill in DB credentials, then run php artisan key:generate from the project root.
6. Open http://assethub.test/install in your browser and follow the installer wizard.

Option 2 — XAMPP (Windows, macOS, Linux)

XAMPP bundles Apache, MySQL/MariaDB, and PHP. Free and cross-platform. Make sure to pick a version with PHP 8.2 or newer.

1. Download XAMPP 8.2+ from apachefriends.org and install it.
2. Copy the AssetHub project into C:\xampp\htdocs\AssetHub\ (Windows) or /Applications/XAMPP/htdocs/AssetHub/ (macOS).
3. Open XAMPP Control Panel and start Apache and MySQL. If the ports are busy, use Config → service.conf to switch Apache to 8080.
4. Go to http://localhost/phpmyadmin → New → create a database named assethub with utf8mb4 collation.
5. In the project folder: copy .env.example to .env, set DB_DATABASE=assethub, DB_USERNAME=root, leave DB_PASSWORD empty (XAMPP default). Run php artisan key:generate.
6. Visit http://localhost/AssetHub/public/install to run the installer wizard.

Option 3 — Laragon (Windows)

Laragon is a portable Windows stack designed for Laravel — auto vhosts, pretty URLs, MySQL/MariaDB, and bundled HeidiSQL.

1. Download Laragon Full from laragon.org and install it.
2. In Laragon: Menu → PHP → Version — switch to PHP 8.2 or 8.3.
3. Copy the AssetHub project into C:\laragon\www\AssetHub\.
4. Click Start All. Laragon auto-creates the vhost: http://assethub.test (pointing to the public/ folder).
5. Open HeidiSQL (bundled) → create a database assethub. Default credentials: user root, password empty.
6. Edit .env with the DB credentials, run php artisan key:generate, then visit http://assethub.test/install.

Option 4 — Built-in PHP server (no web server needed)

The simplest option: Laravel ships with artisan serve, which starts a development PHP server. No Apache or Nginx required. Best for quick testing.

# Install dependencies and configure
cd /path/to/AssetHub
composer install
cp .env.example .env
php artisan key:generate

# Run migrations and seed initial data
php artisan migrate --seed

# Start the development server
php artisan serve
# Then visit: http://127.0.0.1:8000/install

Common localhost gotchas

QR scanner camera doesn't open on http://

Browser camera APIs require HTTPS, with one exception: http://localhost and http://127.0.0.1 are treated as secure contexts. If you access AssetHub via your LAN IP (e.g. http://192.168.1.10), the camera will refuse. Use localhost for dev, or enable HTTPS via Herd / mkcert.

Permission denied on storage (macOS / Linux)

If you see write errors when the app tries to log or cache, fix permissions: chmod -R 775 storage bootstrap/cache. On Windows this isn't usually needed.

Port already in use

If port 8000 is taken by another app, use a different port:

php artisan serve --port=8001

Testing emails locally

Real SMTP isn't available on most localhost setups. Two safe options: (1) set MAIL_MAILER=log in .env — emails are dumped to storage/logs/laravel.log instead of being sent; or (2) use Mailtrap / MailHog to capture outgoing mail in a fake inbox.

MAIL_MAILER=log
# All emails are written to storage/logs/laravel.log

Frontend assets (Vite / Tailwind)

AssetHub's Vue/Tailwind frontend is pre-built in the package. If you edit Vue components or Tailwind config you'll need Node.js 18+:

npm install
npm run dev    # Hot-reload during development
npm run build  # Production build (run before deploying)

Deploying to Hostinger Single (Shared Hosting)

This is the recommended path for users without VPS or technical experience. AssetHub is fully compatible with the cheapest Hostinger Single Web Hosting plan (~$2.99/month). No SSH, no Composer, no command line needed — Single includes native cron jobs, PHP 8.3, and free SSL out of the box.

Step 1 — Prepare your hosting

1. Login to Hostinger hPanel.
2. Go to Hosting → Manage for your domain.
3. Set PHP version to 8.2 or 8.3 via Advanced → PHP Configuration.
4. Make sure these PHP extensions are enabled (usually default):
   • OpenSSL, PDO, PDO_MySQL, Mbstring, GD, Tokenizer, XML, Ctype, JSON, Fileinfo

Step 2 — Create MySQL database

1. In hPanel, go to Databases → MySQL Databases.
2. Click Create New Database.
3. Note these 3 values:
   • Database name — e.g. u123_AssetHub
   • Username — e.g. u123_admin
   • Password — auto-generated, keep it safe

Step 3 — Upload files

1. Go to Files → File Manager in hPanel.
2. Navigate to public_html/ (this is your domain's root).
3. Delete any default index.html or default.php in that folder.
4. Click Upload Files and upload the entire source.zip from the package.
   Or upload the contents of /source/ folder directly via FTP if you prefer.
5. If you uploaded a ZIP, right-click → Extract. After extraction, all files should be at the root of public_html/.
6. Verify public_html/ contains: app/, public/, vendor/, .htaccess, index.php (in public/), .env, etc.

Step 4 — Run the installer

1. Open your browser and go to https://yourdomain.com/install.
2. You'll see the AssetHub Installer.
3. Step 1: Requirements — All checks should pass (green). If any fail, contact Hostinger support to enable the missing PHP extension.
4. Step 2: Database — Enter the credentials from Step 2 above:
   • Host: localhost
   • Port: 3306
   • Database: u123_AssetHub
   • Username: u123_admin
   • Password: (the one Hostinger generated)
5. Step 3: Migrate — Click "Run Migrations & Seed". Takes ~10 seconds. Don't refresh.
6. Step 4: Admin — Create your administrator account. Use a strong password.
7. Done! — You'll see the Cron URL (save this!) and a button to login.

Step 5 — Setup automatic email alerts via Hostinger Cron

AssetHub uses Laravel's scheduler for background tasks: warranty alerts, maintenance reminders, document expiry, depreciation refresh, and overdue checkouts. Set up one cron job in hPanel and Laravel decides which task to run when.

1. In hPanel, go to Advanced → Cron Jobs.
2. Click Create Cron job.
3. Select type: Custom (not "PHP" — we need to pass an argument).
4. For the command, enter (replace uXXXXXX with your Hostinger account username):

   /usr/bin/php /home/uXXXXXX/public_html/artisan schedule:run

   Tip: open File Manager, locate the artisan file (root of your project), right-click → Properties to copy the full path.
5. Set schedule to Every minute — all five fields (Minute, Hour, Day, Month, Day of week) set to *.
6. Click Save.

That's it — AssetHub now sends overdue checkout reminders, maintenance alerts, document expiry alerts, warranty alerts, and refreshes asset depreciation values automatically. Laravel internally schedules each job at its correct frequency (daily 08:00, monthly, etc.).

Step 6 — Configure email (SMTP)

Hostinger provides email accounts with each plan. To use them for AssetHub notifications:

1. In hPanel, go to Emails → Email Accounts and create one (e.g. noreply@yourdomain.com).
2. Edit the .env file in public_html/ via File Manager:

   MAIL_MAILER=smtp
   MAIL_HOST=smtp.hostinger.com
   MAIL_PORT=587
   MAIL_USERNAME=noreply@yourdomain.com
   MAIL_PASSWORD=your_email_password
   MAIL_ENCRYPTION=tls
   MAIL_FROM_ADDRESS=noreply@yourdomain.com
   MAIL_FROM_NAME="Your Company Name"

3. Save the file.
4. Login to AssetHub → Settings → Email tab → Send Test Email. If you receive it, you're done.

Common issues on Hostinger Single

"500 Internal Server Error" after upload

• Verify .htaccess exists at public_html/ root and contains the rewrite rules.
• Verify PHP version is set to 8.2 or 8.3 in hPanel.
• Check storage/logs/laravel.log via File Manager for the actual error.

"Permission denied" on uploads

Hostinger usually sets correct permissions, but if not:

• Right-click storage/ in File Manager → Permissions → set to 755 recursively.
• Same for bootstrap/cache/.

QR code scanner camera doesn't open

Browser camera APIs require HTTPS. Hostinger provides free SSL via Let's Encrypt — enable it in hPanel under SSL → Manage.

Scheduled emails aren't being sent

• In hPanel → Cron Jobs → check the Last run column on your cron entry. If empty, the cron isn't firing — verify the artisan path is correct.
• Test the command manually: open Terminal in hPanel (if available) and run the cron command. If it errors, the error message will pinpoint the issue (wrong PHP version, wrong path, etc.).
• Verify SMTP is correctly configured (Settings → Email → Send Test).
• Check storage/logs/laravel.log for scheduler errors.

Slow performance

Hostinger Single has shared CPU/RAM. If your team is more than 20 users, consider:

• Upgrading to Premium (~$3.99/month) — faster servers, more resources, multiple databases.
• Or Business (~$5.99/month) — dedicated resources, daily backups, staging environment.

Deploying to cPanel (Shared Hosting)

This guide covers standard cPanel shared hosting (Namecheap, Bluehost, GoDaddy, and most budget hosts). AssetHub ships with vendor/ and pre-built frontend assets — no Composer, npm, or web Terminal required. If your cPanel lacks Terminal, use SSH Access or the File Manager workarounds below.

Step 1 — Set PHP version and extensions

1. Login to cPanel.
2. Open MultiPHP Manager (or Select PHP Version) and set your domain to PHP 8.2 or 8.3.
3. Open MultiPHP INI Editor or PHP Extensions and confirm these are enabled:
   • OpenSSL, PDO, PDO_MySQL, Mbstring, GD, Tokenizer, XML, Ctype, JSON, Fileinfo
4. If an extension is missing, enable it in the extensions list or contact your host's support.

Step 2 — Enable SSL (HTTPS)

1. Go to SSL/TLS Status (or Let's Encrypt SSL / AutoSSL).
2. Run AutoSSL or install a free certificate for your domain.
3. HTTPS is required for the in-browser QR scanner to access the camera.

Step 3 — Create MySQL database and user

1. Open Manage My Databases (under Databases).
2. Under Create New Database, enter a name (e.g. assethub) and click Create. cPanel adds your account prefix automatically — the full name will look like cpaneluser_assethub.
3. Under MySQL Users, create a user with a strong password. Copy the full prefixed username.
4. Under Add User To Database, select the user and database, click Add, then grant ALL PRIVILEGES. This step is easy to miss — without it you get Access denied (1045) errors.
5. Note these three values exactly as shown in cPanel:
   • Database name — e.g. u123_AssetHub
   • Username — e.g. u123_admin
   • Password — auto-generated, keep it safe

Step 4 — Upload files

1. Open File Manager and go to public_html/ (your domain's document root).
2. Enable Settings → Show Hidden Files so you can see .htaccess and .env.
3. Delete any default index.html in public_html/ if present.
4. Upload the package source.zip and Extract it, or upload the contents of the /source/ folder via FTP.
5. After extraction, public_html/ should contain app/, public/, vendor/, root .htaccess, and artisan at the same level.

Step 5 — Prepare .env before running the installer

Complete this step before visiting /install. Laravel requires a valid APP_KEY and correct database settings in .env.

1. In File Manager, copy .env.example to .env (same folder as artisan).
2. Edit .env and set at minimum:

   APP_NAME=AssetHub
   APP_ENV=production
   APP_DEBUG=false
   APP_URL=https://yourdomain.com
   
   DB_CONNECTION=mysql
   DB_HOST=127.0.0.1
   DB_PORT=3306
   DB_DATABASE=cpaneluser_assethub
   DB_USERNAME=cpaneluser_admin
   DB_PASSWORD="your_password"
   
   SESSION_DRIVER=file
   CACHE_STORE=file

3. Set DB_CONNECTION=mysql — the default .env.example uses SQLite; shared hosting requires MySQL.
4. Set SESSION_DRIVER=file and CACHE_STORE=file before the first migration (avoids "sessions table not found" errors).
5. Wrap DB_PASSWORD in double quotes if it contains special characters (#, $, !, etc.).

Generate APP_KEY (no Terminal required)

Many cPanel plans don't include a web Terminal. Use one of these methods:

• SSH Access (cPanel → Security → SSH Access): connect with PuTTY or PowerShell, then run cd ~/public_html && php artisan key:generate.
• File Manager helper — create public/genkey.php temporarily, visit it in your browser, copy the output into APP_KEY=, then delete the file immediately.

  <?php
  echo 'base64:' . base64_encode(random_bytes(32));

• On your PC — if PHP is installed locally, run php -r "echo 'base64:'.base64_encode(random_bytes(32));" and paste the result into .env.

• Set storage/ and bootstrap/cache/ permissions to 755 (recursive) if the installer reports write errors.

Step 6 — Run the web installer

1. Open https://yourdomain.com/install in your browser.
2. Step 1: Requirements — all checks must pass (green). Fix any missing PHP extensions in Step 1 above.
3. Step 2: Database — enter the exact prefixed names from Step 3:
   • Host: 127.0.0.1 or localhost
   • Port: 3306
   • Database: cpaneluser_assethub
   • Username: cpaneluser_admin
   • Password: (your MySQL password)
4. Step 3: Migrate — click "Run Migrations & Seed". Takes ~10 seconds. Do not refresh the page.
5. Uncheck Include demo data for a clean production install.
6. Step 4: Admin — create your administrator account.
7. Done! — save the Cron URL shown on the final screen.

Step 7 — Setup Cron Jobs for email alerts

AssetHub needs one cron job running every minute so Laravel can send warranty alerts, maintenance reminders, and other scheduled emails.

1. In cPanel, go to Advanced → Cron Jobs.
2. Under Add New Cron Job, set schedule to Every minute (* * * * *).
3. Enter the command (replace CPANELUSER with your cPanel username from General Information):

   /usr/local/bin/php /home/CPANELUSER/public_html/artisan schedule:run

   Tip: the PHP path may be /usr/local/bin/php or /usr/bin/php — ask your host if unsure. The artisan path is where you uploaded the project (usually /home/CPANELUSER/public_html/artisan).
4. Click Add New Cron Job to save.

Step 8 — Configure email (SMTP)

Create a cPanel email account for outgoing notifications:

1. Go to Email Accounts → create e.g. noreply@yourdomain.com.
2. Edit .env in File Manager:

   MAIL_MAILER=smtp
   MAIL_HOST=mail.yourdomain.com
   MAIL_PORT=587
   MAIL_USERNAME=noreply@yourdomain.com
   MAIL_PASSWORD=your_email_password
   MAIL_ENCRYPTION=tls
   MAIL_FROM_ADDRESS=noreply@yourdomain.com
   MAIL_FROM_NAME="Your Company Name"

3. Save, then in AssetHub: Settings → Email → Send Test Email.

Common issues on cPanel

"Access denied for user" (SQLSTATE 1045)

• Copy database name and username exactly from cPanel — including the account prefix.
• Confirm you completed Add User To Database with ALL PRIVILEGES.
• Reset the MySQL password in cPanel and update .env — use quotes around DB_PASSWORD if it contains special characters.

Migration fails after Database step passed

• The wizard tests credentials from the form, but Migrate reads .env. Make sure both match.
• Delete bootstrap/cache/config.php if it exists, then retry.
• Ensure DB_CONNECTION=mysql is set in .env (not sqlite).

"Invalid default value" during migration (1067)

Fixed in AssetHub v2.1.0+ (checkouts table uses dateTime columns). If you have an older copy, update the migration file or download the latest package from CodeCanyon.

"500 Internal Server Error" after upload

• Verify root .htaccess exists and PHP is 8.2+.
• Check storage/logs/laravel.log for the real error.
• Confirm APP_KEY is set in .env — empty key causes 500 errors.

No Terminal in cPanel

This is normal on many shared plans. Use SSH Access (if enabled), the temporary genkey.php method in Step 5, or generate the key on your local PC.

QR scanner camera doesn't open

Enable SSL via SSL/TLS Status → AutoSSL and access the site via https://.

Configuration

.env File

In-app Settings

Most non-sensitive options are configurable from Admin → Settings:

• General: company name/email/phone, asset tag prefix
• Email: send a test email to verify SMTP
• Notifications: warranty alert thresholds, maintenance reminder window
• Localization: timezone (searchable list incl. Europe/Skopje), date format, currency code (incl. MKD — Macedonian Denar), symbol, and symbol position — applied app-wide after save
• General → Public Asset Page: QR visibility (public / login / disabled) and regenerate all QR codes after URL changes
• Localization tab links to Administration → Translations for the full Translation Editor (admin-only)
• Branding: app name and logo — updates login logo, footer, badge, and browser page title (v4.0+). Login subtitle: edit auth.login_subtitle in Administration → Translations
• Appearance (v4.0+): customize brand, status, and text colors for light and dark mode — see rebrand guide in the FAQ

Multi-Language Support

AssetHub ships with 11 languages out of the box, including RTL Arabic and Hindi. Users switch language via the flag dropdown in the top-right header.

Shipped languages

How to switch language

1. Click the flag icon in the top-right header to open the dropdown.
2. Pick your language from the list.
3. The page reloads; all UI labels, dates, and currency formats switch.
4. Your choice is saved in both your user account and a cookie (1 year).

Adding a custom language (admin)

Go to Administration → Translations (admin users with manage translations permission):

• Click "Add Locale" — provide a code (e.g. mk for Macedonian), display name, native name, flag SVG filename, direction (LTR/RTL), and a base locale to copy translations from.
• The new locale appears in the language switcher and Settings → Localization default-language list.
• DB-stored translations automatically override file translations in lang/{code}/.

Translation Editor

The editor lists every translation key grouped by file (e.g. assets, nav, settings). Keys show the file baseline and any database override.

• Filter by locale, translation group, or search text.
• Click a value to edit inline; changes save to the database immediately.
• Reset a key to revert to the file baseline.
• Built-in locales (en, vi, es, …) can be edited; custom locales are fully DB-driven.
• Only users with the manage translations permission can access this page.

CSV import / export

• Export — download all keys for a locale as CSV (group,key,value).
• Import — upload a CSV with the same columns; existing DB overrides are updated, new keys are inserted.

Per-user default locale

Each user has a locale column. Email notifications are automatically sent in the recipient's preferred language thanks to Laravel's HasLocalePreference contract.

The site default language is set under Settings → Localization → Default Language. Individual users override this via the header language switcher.

Feature List

Users & Roles

AssetHub ships with 5 pre-configured roles:

Permissions are stored as Spatie roles — administrators can fine-tune per-permission via the database.

Asset Management

Creating Assets

1. Navigate to Assets → New Asset.
2. Fill in name, category, brand, model, serial number.
3. Add purchase date and price (required for depreciation).
4. Upload images (multiple files supported, max 5 MB each).
5. Save — asset tag and QR code are auto-generated.

Asset Tag Format

Default: {PREFIX}-{YEAR}-{NNNN}, e.g. AS-2026-0001. Configurable via Settings → General → Asset Tag Prefix.

Bulk Import

1. Click Import on the Assets page.
2. Download the Excel template.
3. Fill in your data — required columns: name, category_name.
4. Upload the file.

Batch / Lot Assets (v2)

For identical items in quantity (chairs, keyboards, uniforms), choose Tracking type → Batch / Lot on the New Asset form instead of creating duplicate records.

1. Enter quantity and unit (piece, set, box). On save, stock is placed in the warehouse pool.
2. Open the asset → Allocations tab → Allocate units to an employee or department.
3. Use Return, Adjust (damaged/lost/repair), or disposition actions — the live summary must reconcile to total quantity.
4. Batch assets support unit price only; depreciation is optional and off by default for faster setup.

QR Codes

Every asset automatically receives a QR code on creation. Scanning opens the asset's public or authenticated page (see below). In-app scanning jumps to the asset detail screen.

Printing Labels

• Single label: Click the printer icon on any asset row.
• PDF format: A4, 2 labels per row, includes asset tag, name, brand, serial.

Scanning

Click Scan QR on the Assets page. Allow camera permission. The scanner uses html5-qrcode and works on any modern browser. Note: camera access requires HTTPS or localhost.

Public QR Handover Page (v2)

Each asset also has a printable public URL at /a/{asset_tag} — useful for physical handover without logging in.

• Configure in Settings → General → Public Asset Page: Public, Login required, or Disabled.
• The page shows photo, key fields, and (for batches) quantity breakdown. Users can print it as a handover sheet.
• After changing APP_URL, click Regenerate all QR codes in the same settings panel.

Workflows

Asset Assignment

1. Open an asset detail page.
2. Click Assign (visible if asset is available).
3. Pick a user, optional return date, notes.
4. Submit — transaction is created and email notification sent.

Asset Requests

Employees can submit requests for assets they need. Requests have 4 statuses: pending → approved → fulfilled, or rejected. Approval emails are sent automatically.

Check-in / Check-out

For shared assets (cameras, projectors, vehicles). Bookings have date ranges; the system prevents overlapping checkouts. Calendar view shows all bookings at a glance.

Disposals — Formal Write-off (v2)

Worn or damaged items are written off in documented batches with separation of duty (proposer ≠ approver). Requires permissions manage disposals and approve disposals.

1. Sidebar → Disposals → New Disposal. Set title and period (Q1–Q4, yearly, or ad-hoc).
2. Open the draft → Add items — eligible damaged batch units or single assets in Poor condition.
3. Click Submit for approval — the batch locks.
4. A different approver clicks Approve & execute — assets/units are marked disposed.
5. Print disposal minutes (PDF) for compliance records.

Depreciation

AssetHub calculates asset depreciation using one of three methods:

Defaults are inherited from the asset's category. Schedule entries are generated monthly. Asset's current_value is auto-updated on the 1st of each month.

Custom Fields

Admin → Custom Fields lets you add unlimited custom attributes to assets:

• Types: text, number, date, select (dropdown), textarea, file, checkbox
• Scope: apply to all categories or specific category
• Reorder: drag-and-drop the grip handle
• Required fields are validated on asset save

Reports

Twelve built-in reports, accessible from the Reports menu:

1. Asset Summary — totals by status, condition, category, department
2. Depreciation — value loss per category, top depreciated assets
3. Transactions — assignment, return, transfer activity over time
4. Maintenance Cost — spending by month, category, type
5. Warranty Expiry — assets needing attention in 30/60/180 days
6. Department Assets — asset distribution & budget utilization by department
7. Assets by Source — distribution across procurement, project, donation, transfer sources
8. Inventory Audit Summary — discrepancies across periodic audit cycles
9. Employee Assignments (v2) — who holds what, including batch allocations
10. Department / Location (v2) — assets and quantities by department or location
11. Inventory Reconciliation (v2) — stock vs allocated vs damaged/lost/disposed
12. Damaged Assets (v2) — items flagged for repair or write-off

All reports support Excel and PDF export via buttons in the page header. v2 reports are quantity-aware (asset count + total units).

Webhooks

AssetHub can notify external services on key events.

Available Events

• asset.created, asset.updated, asset.deleted
• asset.assigned, asset.returned, asset.transferred
• request.created, request.approved, request.rejected, request.fulfilled
• maintenance.scheduled, maintenance.started, maintenance.completed
• checkout.created, checkout.returned

Payload Format

{
  "event": "asset.assigned",
  "timestamp": "2026-05-05T08:00:00+00:00",
  "data": {
    "asset_id": 1,
    "asset_tag": "AS-2026-0001",
    "asset_name": "HP EliteDesk 800",
    "to_user_id": 4,
    "transaction_id": 12
  }
}

Signature Verification

If a secret is configured, requests include header X-AssetHub-Signature containing HMAC-SHA256 of the payload body. Verify on your end:

$expected = hash_hmac('sha256', $rawBody, $secret);
if (hash_equals($expected, $request->header('X-AssetHub-Signature'))) {
  // valid
}

Retry Policy

Failed deliveries retry 3 times with 200 ms delay. After 10 consecutive failures, the webhook is auto-disabled.

Scheduled Tasks

AssetHub uses Laravel's scheduler for background jobs. You only need one cron entry — Laravel internally dispatches each job at the right time.

Shared hosting (cPanel / Hostinger Cron Jobs UI)

See cPanel Setup → Step 7 or Hostinger Setup → Step 5. In short: Advanced → Cron Jobs, command:

/usr/bin/php /home/uXXXXXX/public_html/artisan schedule:run

Schedule: every minute (* in all five fields).

cPanel cron command

Replace CPANELUSER with your cPanel username:

/usr/local/bin/php /home/CPANELUSER/public_html/artisan schedule:run

VPS / dedicated server (crontab)

Run crontab -e as your web user (often www-data) and add:

* * * * * cd /path/to/AssetHub && php artisan schedule:run >> /dev/null 2>&1

Fallback: external URL pinger

If your host has no cron at all, use the in-app Cron URL (Settings → System tab) with cron-job.org (free, every 15 min).

Jobs that run automatically

Upgrade Guides

Step-by-step guides for updating an existing installation. Open the guide that matches your current version.

• v3.1 → v4.0 — Full upgrade guide — Appearance settings, browser tab title from Branding. No migration required.
• v3.0 → v3.1 — Full upgrade guide — Visible languages checklist in navbar picker. No migration required.
• v2.x → v3.0 — Full upgrade guide — Translation Editor, custom locales, localization settings.
• v1.x → v2.0 — Full upgrade guide — Batch assets, disposals, public QR page, operational reports.

Troubleshooting

"Permission denied" on storage

chmod -R 775 storage bootstrap/cache
chown -R www-data:www-data storage bootstrap/cache

QR code scanner doesn't open camera

Browser camera APIs require HTTPS. Either install an SSL certificate or use localhost for testing.

Emails not arriving

Check storage/logs/laravel.log for errors. Use Settings → Email → Send Test Email to verify SMTP credentials. Make sure your SMTP server allows the sending IP.

Database "Access denied" (1045) on cPanel

Wrong username/password, missing user-to-database assignment, or special characters in password breaking .env parsing. See cPanel Setup → Common issues.

Migration error 1067 (Invalid default value)

MySQL strict mode on shared hosting rejects multiple NOT NULL timestamp columns. Fixed in v2.1.0+. Update your package or change checkout_date / expected_return_date to dateTime in the checkouts migration.

Missing APP_KEY / 500 error before install

Laravel requires APP_KEY in .env before the app loads. If cPanel has no Terminal, see cPanel Setup → Step 5 for SSH, genkey.php, or local generation methods.

Reset installation

Delete storage/installed.lock and visit /install again. Existing data will be erased if you re-run migrations.

Performance — slow asset list

Run php artisan optimize to cache config, routes, views. Ensure MySQL has indexes on assets.asset_tag, assets.serial_number, assets.status (created automatically by migrations).

Upgrading from v3.0.x to v3.1

Download the v3.1 package from CodeCanyon, replace application files (keep your .env and storage/ uploads). No new migrations are required. The new visible_locales setting is optional — if unset, all languages remain visible in the navbar picker.

v3.0 → v3.1 — Full upgrade guide

Upgrading from v2.x to v3.0

Download the v3 ZIP from CodeCanyon, replace application files (keep your .env and storage/ uploads), then run php artisan migrate. New tables for custom locales and translation overrides are added automatically. Existing settings and assets are preserved.

v2.x → v3.0 — Full upgrade guide

Upgrading from v1.x to v2.0

Download the v2 ZIP from CodeCanyon, replace application files (keep your .env and storage/ uploads), then run php artisan migrate. The upgrade is non-breaking — existing single assets continue to work; new batch/disposal tables are added automatically.

v1.x → v2.0 — Full upgrade guide

Changelog

v4.0.0 — Appearance & Branding (2026-06-20)

• Appearance settings — Settings → Appearance: customize brand, status, and text colors separately for light and dark mode; live preview; save to database
• App version — config('app.version') (default 4.0.0); shown in Settings → System → Environment
• Browser tab title — uses Settings → Branding → App Name at runtime instead of build-time VITE_APP_NAME only
• Login page branding — footer copyright and right-panel badge follow Settings → Branding → App Name automatically
• No database migration required — upgrade is file-replace only
• Documentation and user guide updated for v4.0

v3.1.0 — Visible Language Picker (2026-06)

• Settings → Localization: checklist to choose which languages appear in the navbar language dropdown (built-in + custom locales)
• Default language is always visible; picker auto-hides when only one language is selected
• Backend validates locale switches; users on a hidden locale fall back to the default language
• No database migration required — upgrade is file-replace only
• Login page branding: footer copyright and right-panel badge follow Settings → Branding → App Name (no code edit required)

v3.0.0 — Localization & Translation Editor (2026-06)

• Translation Editor UI at Administration → Translations (Add Locale, inline edit, search/filter by group)
• Custom locales stored in DB — code, display name, native name, flag SVG, direction, base locale
• CSV import/export for bulk translation updates
• Timezone and currency settings now applied app-wide (config/localization.php incl. Europe/Skopje, MKD)
• Settings → Localization: searchable timezone/currency dropdowns with custom value support
• Hindi (hi) added as 11th built-in locale; date_format respected across Vue pages
• Permission-gated manage translations; database overrides merge with lang/ file baseline

v2.0.0 — Operational Release (2026-06)

• Batch / lot assets — quantity tracking, allocations, returns, live reconciliation
• 4 operational reports: Employee Assignments, Department/Location, Inventory Reconciliation, Damaged Assets
• Disposals module — write-off batches, separation-of-duty approval, printable minutes PDF
• Public QR asset page at /a/{tag} with configurable visibility
• Legacy reports updated to show asset count + total units
• QR codes link to public handover page; transaction log records quantity on batch moves
• Updated demo data, user guide (shipped separately in documentation/), and i18n strings

v1.0.0 — Initial Release (2026-05)

• Asset CRUD with QR code auto-generation
• 5 user roles (Admin, IT Manager, Accountant, Supervisor, Employee) with granular permissions
• Asset Source tracking (centralized procurement, decentralized procurement, investment project, donation, internal transfer)
• Assignment, return workflows with email notifications
• Transfer Approval Workflow (pending → approved/rejected) with permission gating
• Asset request approval flow
• Check-in/check-out with calendar view
• Maintenance scheduling with auto-renewal
• Document attachments with expiry alerts
• Depreciation with 3 calculation methods + end-of-life alerts
• Inventory Audit module — periodic stocktake with discrepancy tracking
• Custom fields with 7 input types and drag-drop sort
• 8 reports with charts, Excel and PDF export (incl. Assets by Source, Inventory Audit Summary)
• Audit log via Spatie Activitylog with diff viewer
• Webhooks with HMAC signing and auto-retry
• Multi-language UI: 10 locales (en, vi, es, fr, de, zh, ja, pt-BR, ru, ar with RTL)
• Settings UI for company, email, notifications, localization, translations
• Web-based installation wizard
• Dark mode with emerald-teal brand palette

Credits

Open-source libraries used

• Laravel 11 — MIT
• Vue 3 — MIT
• Inertia.js — MIT
• Tailwind CSS — MIT
• Spatie Permission, Media Library, Activitylog — MIT
• Phosphor Icons — MIT (duotone weight)
• ApexCharts — MIT
• html5-qrcode — Apache 2.0
• Simple QrCode — MIT
• Laravel Excel — MIT
• Laravel DomPDF — MIT