Prerequisites for development, build, and production systems
Last update: May 17, 2023
- Topics:
- Configuration
- Deploy
CREATED FOR:
- Experienced
- Admin
- Developer
File permissions and ownership must be consistent across development, build, and production systems. To make this work, you must either:
-
All of the following:
- Set up the same file system owner username on all systems
- Make sure the web server runs as the same user on all systems
- Make sure that the file system owner is in the web server group on all systems
-
Change Commerce file system permissions and ownership on each system as necessary using the following guidelines:
- Development and build: Set pre-installation ownership and permissions (two users)
- Production: Commerce ownership and permissions in development and production
If you choose this approach, you must set file system permissions and ownership every time you pull code from your build system (if the file system owner or web server user are different on your build system).
Previous pagePipeline deployment
Next pageDevelopment system setup
Commerce
- Overview
- General setup
- Deployment
- Cache
- Command Line
- Command-line tool
- Common commands
- Enable logging
- Manage the cache
- Manage indexers
- Configure cron jobs
- Compile code
- Operation mode
- Start message queue consumers
- URN highlighter
- Dependency reports
- Localization
- Configuration management
- Static view
- Create symlinks
- Run unit tests
- Convert layout files
- Generate data for performance testing
- Run support utilities (Commerce only)
- Configuration files
- Configuration paths
- Cron Jobs
- Logs
- Message Queues
- Multiple sites
- Search Engine
- Security
- Storage
- Return to Operational Guides