BullionXE installer
Self-hosted setup
Upload one package, open /install, and complete a guided setup for the storefront, admin, API, subscriptions, CRM, and bullion operations stack.
Installation flow
Each step writes only the minimum required configuration, then BullionXE validates and bootstraps the production runtime for you.
Writable paths
Permissions check
The installer needs temporary write access to create runtime files, cache optimized configuration, and write the environment file.
| Path | Status | Location | Purpose |
|---|---|---|---|
| Storage directory | pass | /home/bullionxe/public_html/backend/storage | Logs, sessions, cache and uploaded runtime files must be writable. |
| Bootstrap cache | pass | /home/bullionxe/public_html/backend/bootstrap/cache | Laravel stores optimized config, route and service cache here. |
| Public uploads | pass | /home/bullionxe/public_html/backend/public/uploads | Shared hosting installs need a writable public upload target. |
| Installer lock path | pass | /home/bullionxe/public_html/backend | The installer must be able to create install.lock after a successful deployment. |
| .env creation | pass | /home/bullionxe/public_html/backend/.env | The installer must be able to create or update the application environment file. |
These permissions are needed only for normal runtime and installer bootstrap. They should remain writable after launch.