The console/environments directory and .env files already exist in the
repository. The install script overwrites these existing files with
the correct configuration values. Updated comments to say 'Update'
instead of 'Write/Create' and removed unnecessary mkdir -p command.
This commit updates the docker-install.sh script to create/update the
console environment files (.env.development and .env.production) before
starting Docker containers.
## Changes
- Added section 6b to create console/environments directory
- Create .env.development with HTTP configuration
- Create .env.production with HTTPS configuration
- Both files include API_HOST, SOCKETCLUSTER settings, and OSRM_HOST
- Production file includes API_SECURE=true flag
## Rationale
Production builds no longer use fleetbase.config.json for runtime
configuration. Instead, they rely on .env.production files that are
baked into the build at compile time. This ensures proper configuration
for both development and production environments.
## Files Created
1. console/environments/.env.development
- HTTP API endpoint (http://<host>:8000)
- SOCKETCLUSTER_SECURE=false
- Uses provided host value
2. console/environments/.env.production
- HTTPS API endpoint (https://<host>:8000)
- SOCKETCLUSTER_SECURE=true
- API_SECURE=true
- Uses provided host value
## Impact
This ensures that when users run `ember build --environment=production`,
the compiled assets have the correct API endpoints and SocketCluster
configuration embedded, rather than relying on runtime configuration
which is only available in development mode.
## Related
This change mirrors the update made to the CLI install-fleetbase command
in fleetbase/fleetbase-cli PR #3.
The script contained typographic curly quotes instead of standard ASCII
quotes around the DB_SERVICE variable, causing bash to fail with:
DB_SERVICE: unbound variable
Also replaced the unicode ellipsis with ASCII dots for shell compatibility.
