File permissions

File permissions control which files and directories a web application and the web-server process can read, write, or modify. Correct permissions are important for both application operation and security.

Exact permission requirements vary by DotwebApps product and by the hosting or server environment. Always follow the installation documentation for the specific product you are using.

Use the minimum permissions the application needs #

A web application normally needs to read its application files, while only certain files or directories may need write access for functions such as uploads, generated files, cache data, logs, or other product-specific operations.

Use the most restrictive permissions that still allow the application to operate correctly.

Avoid:

• making the entire application writable
• applying broad permissions to every file or directory
• copying permission settings from an unrelated application
• changing ownership or permissions without understanding how your hosting or server environment handles file ownership
• using an overly permissive setting as a blanket troubleshooting fix

DotwebApps does not publish one universal numeric permission value for every product. Values that are appropriate for one hosting environment or application may be inappropriate or insecure for another.

If the application reports a permission or write-access error #

Check the following:

1. Confirm that all application files were uploaded completely.
2. Confirm that the web-server process can read the files required by the application.
3. Confirm that only the locations identified by the product documentation as writable have the necessary write access.
4. Check file ownership where your hosting or server environment uses ownership rules that affect application access.
5. Review the relevant application or server error message for the affected file or directory.
6. Consult your hosting provider if permissions or ownership are controlled by the hosting environment.

Do not change permissions blindly. If the product documentation specifies particular writable locations or permissions, those instructions take precedence.

Security precautions #

Do not make the entire application writable simply to make an error disappear. Overly broad permissions can create unnecessary security exposure.

Also make sure that sensitive configuration files and credentials are not publicly accessible through the web server.

When requesting support, provide the relevant product name, the sanitized error message, and general hosting/server information. Never send passwords, private keys, API secrets, or other sensitive credentials.

For the broader installation process, see Uploading and installing software.