What problem does Forge solve?
Preparing a site and securely deploying it are not the same task. The Forge approach decouples the project version, the client's workspace, and the deployment decision. This allows for tracking which version is running in which environment. For the client, the key benefits are that changes are not haphazardly pushed to the live site and that the delivered version is clearly defined.
What does licensing mean?
A license signifies the right to use the agreed-upon system within a specific scope and timeframe. A license key does not, in itself, grant domain ownership, the transfer of full source code, or unlimited development rights. Details regarding domain mapping, duration, terms of use, and any renewal requirements must be verified against the relevant agreement. Keys should not be shared in email groups or public documents.
Deployment and rollback
Deployment proceeds in stages: first preview and verification, followed by approved deployment. If an issue arises, the version to be rolled back to must be known in advance. Rolling back the code version does not automatically revert new records created in the database; therefore, data changes require separate planning. The active Forge features in your project are determined by the scope of delivery; it is not assumed that all modules are enabled in every package.
Your quick checklist
- Approve the version to be released.
- Record the scope and duration of the license.
- Distinguish between rollback and data restoration.