# Admin User Credentials

## Primary Admin (Public Contact)
- **Name**: Primary Admin
- **Phone**: 01628178114
- **Password**: password
- **Role**: admin
- **Contact Display**: YES (shown in website contact info)

## Secondary Admin (Internal Use)
- **Name**: Secondary Admin
- **Phone**: 01913988543
- **Password**: password
- **Role**: admin
- **Contact Display**: NO (not shown in website contact info)

## Customer Test Account
- **Name**: John Customer
- **Phone**: 01887654321
- **Password**: password
- **Role**: customer

## Login Instructions
1. Go to `/admin` for admin panel access
2. Go to `/login` for customer login
3. Use phone number as username
4. Default password for all test accounts: `password`

## Notes
- Both admin users have full administrative privileges
- Primary admin phone number is displayed in website contact information
- Secondary admin is for internal use and not displayed publicly
- All test accounts have verified phone numbers

## GitHub Actions / Deployment (InfinityFree)

This repository includes a GitHub Actions workflow to build the project and deploy it to InfinityFree via FTP:

- Workflow path: `.github/workflows/deploy-infinityfree.yml`
- Trigger: push to the `master` branch (adjust the workflow if you use a different branch)

Required repository secrets (set them in the repository Settings → Secrets → Actions):

- `INFINITYFREE_FTP_HOST` — your FTP host (e.g. `ftpupload.net` or `ftp.epizy.com`)
- `INFINITYFREE_FTP_USERNAME` — FTP username for your InfinityFree account
- `INFINITYFREE_FTP_PASSWORD` — FTP password for your InfinityFree account
- `INFINITYFREE_FTP_REMOTE_PATH` — (optional) remote path to upload into. Default used by the workflow: `/htdocs`

Notes and recommendations:

- The workflow runs a frontend build (if `package.json` exists) and installs Composer dependencies, then uses `lftp` to mirror the repository to the remote path.
- On many shared hosts (including InfinityFree) the public web root is `/htdocs`. If you only want files from the Laravel `public` directory served, consider uploading the `public` contents to `/htdocs` and other application files to a different folder — adjust the workflow's `FTP_REMOTE_PATH` or lftp `mirror` parameters accordingly.
- Be careful with committing or uploading sensitive files (for example a production `.env`). Manage secrets via GitHub secrets or remove/transform the `.env` before deployment if necessary.
- After configuring the secrets, push to `master` to trigger a deploy. Check the Actions tab for logs and troubleshooting information.
