Permissions
Technical details of the Permissions installation phase.
The Permissions installation phase prepares the filesystem permissions required by APPNETOS.
Its responsibility is ensuring that all shared runtime directories are writable by the current runtime user while preserving a secure project structure.
The phase is executed automatically during every installation.
Goals
The Permissions installation phase has the following responsibilities:
- Prepare shared runtime directories.
- Configure required write permissions.
- Prevent permission-related runtime errors.
- Support Linux bind-mounted Docker environments.
Background
APPNETOS stores several runtime resources on the filesystem.
Examples include:
- Cache
- Logs
- Temporary files
- Generated resources
- Uploads
These directories must be writable by the executing PHP process.
Without the correct permissions, applications cannot operate correctly.
Shared Runtime Directories
The installer configures the required permissions for all shared runtime directories.
Applications therefore do not need to perform their own permission handling during installation.
The shared runtime remains consistent across all installed applications.
Docker Support
The Docker development environment maps the local Linux user into the PHP container.
Typical configuration:
LOCAL_UID=1000
LOCAL_GID=1000
LOCAL_USER=developer
LOCAL_GROUP=developer
This mapping ensures that files created by APPNETOS remain owned by the local development user instead
of
root
.
The Permissions installation phase complements this configuration by preparing the required writable directories.
Automatic Configuration
During installation the required permissions are configured automatically.
Typical installer output:
[ OK ] Shared permissions installed
No manual permission changes should be required after installation.
Idempotency
The Permissions installation phase is fully idempotent.
Running the installer multiple times safely verifies and reapplies the required permissions where necessary.
Existing project files are not modified unnecessarily.
Error Handling
If required permissions cannot be configured, the installation process stops immediately.
This prevents partially working installations that would later fail during runtime.
The installer reports the affected directory whenever possible.
Troubleshooting
Permission problems inside Docker are usually caused by incorrect user mapping.
Verify the values inside
.env
.
Example:
LOCAL_UID=1000
LOCAL_GID=1000
LOCAL_USER=developer
LOCAL_GROUP=developer
These values should match the local Linux user.
The current values can be determined using:
id
Summary
The Permissions installation phase provides:
- Automatic runtime permission configuration
- Docker-compatible filesystem permissions
- Shared runtime directory preparation
- Fully repeatable execution
- Stable application runtime