Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. It only takes a minute to sign up.
Sign up to join this community
I'm trying set up a development model in our organization using SFDX and scratch orgs. Following the SFDX Trailhead modules, I see that only the particular project at hand is being sourced.
How can I keep a constant baseline of an org as it stands? I'd like our development team to be able to have the full codebase to start with and create branches from that existing base. Is this not how SFDX was designed?
DX works well with multiple "packages" within your git project. In fact, I'd recommend this, as it allows easier merging and branching strategies, and you only need to deploy pieces at a time. The Trailhead examples are intentionally simple, because it's not supposed to be an entire org example, which would take much longer to understand.
For example, in our current design, we have tentatively adopted the following design:
This design allows us to install just parts of our org in to sandboxes/scratch orgs, reducing the amount of time it takes for us to spin up a new development cycle, as well as minimizing the deployment time by using unlocked packages with dependencies. We can also migrate our code from the old repository format to a new format with minimal fuss as developers are working on older features.
All of this metadata exists in a single repository, so all code is available to all developers, and SFDX allows us to write shell scripts to deploy various configurations to any org, even production.
