Development system setup
Last update: April 21, 2023
- Topics:
- Configuration
CREATED FOR:
- Experienced
- Admin
- Developer
You can have any number of development systems, provided the following is true of all of them:
-
They all run Commerce 2.2 or later
-
All Commerce code is under source control in the same repository as the build and production systems
-
Each development system should use either default mode or developer mode
-
It has file system ownership and permissions set as discussed in Prerequisite for your development, build, and production systems.
-
Make sure all of the following are excluded from source control:
vendor
directory (and subdirectories)generated
directory (and subdirectories)pub/static
directory (and subdirectories)app/etc/env.php
file
-
Make sure
app/etc/config.php
is included in source control
If you use Git, the .gitignore
file provides most of the preceding. See the .gitignore
reference.
Previous pagePrerequisites
Next pageBuild 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