Foxream — job matching for Indonesian workers in Japan

Laravel 13, Filament 5 (admin panel at /admin, candidate dashboard at /dashboard), Livewire 4 and Tailwind 4. The brand name, legal name and logos are set in config/brand.php (BRAND_* in .env), never in the code.

Running it on a laptop

Double-click start-dev.bat: it serves http://localhost:8001 with SQLite (database/database.sqlite). After changing CSS or JavaScript, run npm run build.

Sample content to try the site with (FAQs, testimonials, companies, vacancies, a blog post, an event and an album) and one-click demo accounts:

php artisan db:seed --class=SampleContentSeeder
php artisan demo:setup

Never run these two on the live site.

Deploying

What the server needs

• PHP 8.3 or newer with the pdo_sqlite (or pdo_mysql), mbstring, intl, gd, zip, fileinfo and bcmath extensions
• Composer, and Node.js 20+ to build the CSS and JavaScript
• The web server's document root pointing at public/
• An SMTP mailbox: candidates must confirm their email before they can sign in
• Optional: LibreOffice, for the rirekisho (CV) PDF; without it a simpler PDF is made instead

No queue worker is needed. One cron line runs the nightly backup:

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

The .env file

Copy .env.example to .env and set at least:

Setting	Value
APP_ENV	production (this also hides the demo accounts and their switcher)
APP_DEBUG	false
APP_URL	the site's address, e.g. https://example.com
DB_*	the database; SQLite needs nothing else
MAIL_MAILER, MAIL_HOST, MAIL_PORT, MAIL_USERNAME, MAIL_PASSWORD, MAIL_FROM_ADDRESS	the SMTP mailbox
BOOTSTRAP_ADMIN_NAME, BOOTSTRAP_ADMIN_EMAIL, BOOTSTRAP_ADMIN_PASSWORD	the first admin account, created by db:seed
BRAND_NAME, BRAND_COMPANY, BRAND_LEARNING, BRAND_MAKER	the brand; BRAND_MAKER is the "Made by" line in the footer
DEEPL_API_KEY, GEMINI_API_KEY	optional: Japanese translation for the CV, and reading job orders
LIBREOFFICE_BIN	optional: path to soffice if it is not in a standard place
ALERT_EMAIL	who is emailed when the site hits an error or a backup fails
BACKUP_PASSWORD	encrypts the backups, which hold passports and documents; keep it in a password manager
BACKUP_KEEP_DAYS, BACKUP_AT, BACKUP_DISK	optional: days kept (14), time of the nightly run (02:00), where backups go
LOG_STACK	daily, so the log is one file a day and old ones are removed

Keep passwords and API keys in the server's .env only, never in the code or in chat.

First install

git clone https://github.com/SRAbizard/foxream-website.git
cd foxream-website
composer install --no-dev --optimize-autoloader
npm ci && npm run build
cp .env.example .env        # then fill it in, see above
php artisan key:generate
php artisan migrate --force
php artisan db:seed --force # roles, first admin, categories, visa steps; no sample content
php artisan storage:link
php artisan optimize
php artisan filament:optimize

The web server must be able to write to storage/ and bootstrap/cache/.

Every update

php artisan down
git pull
composer install --no-dev --optimize-autoloader
npm ci && npm run build
php artisan migrate --force
php artisan optimize:clear
php artisan optimize
php artisan filament:optimize
php artisan up

After the first install

Sign in at /admin with the bootstrap admin, change its password, then fill in:

• Website Settings: contact details, social media, offices, the numbers on the homepage and About page (empty ones are hidden), the page pictures and the learning platform's address
• Legal: privacy policy, terms and the anti-fraud warnings; have them checked against the company's real details
• the content itself: companies, job vacancies, FAQs, testimonials, blog, events and gallery

Uploaded files live in storage/app/public (pictures shown on the site) and storage/app/private (candidates' documents, contracts, COE, visa, tickets: opened only by the candidate and admins who manage students, never through a public link). To move them from another install, copy both folders; the database only stores their paths.

Backups

Every night php artisan backup:run puts the database and all uploaded files into one zip, encrypted with BACKUP_PASSWORD, in storage/app/backups (or the disk set in BACKUP_DISK). Backups older than BACKUP_KEEP_DAYS are deleted. A failed backup is emailed to ALERT_EMAIL. Run it by hand any time with php artisan backup:run.

A backup on the same server is lost with the server: copy the newest zip somewhere else regularly (download it, or point BACKUP_DISK at another server's disk).

To restore, open the zip with the password (7-Zip or another AES-capable tool), then put database.sqlite back in database/ (or import database.sql into MySQL) and copy public/ and private/ into storage/app/. Keep a copy of the server's .env too: it is not in the zip because it holds the passwords.

When something breaks

Errors are written to storage/logs and, on the live site, emailed to ALERT_EMAIL: what went wrong, on which page, and where in the code, never what people typed into forms. The same error is emailed once an hour at most, and no more than 30 a day. /up answers 200 while the site is running, for an uptime monitor.

Tests

php artisan test

They run on a fresh in-memory database and touch none of your data.