Create and edit deployment configurations for target deployment environments.
- You can create and edit configuration files in each application components' repository. CodeNOW will collect those configuration files to make a deployment configuration if you have never provided one for your target deployment environment. For more information on how CodeNOW selects a deployment configuration, see Deployment configurations.
- You can create and edit deployment configurations through CodeNOW's user interface at deployment time (as part of the deployment process) or at any other time.
Create a deployment configuration
CodeNOW’s deployment configuration files are uniquely associated with a target deployment environment and a given application package (i.e., a deployment target). As a result, the target deployment environment and application package must exist prior to specifying a deployment configuration.
If that is not the case, you may want to review:
For more information, see Deployment configurations.
Creating a deployment configuration is easy and quick:
Once the deployment configuration is created, you may review, edit, and delete it through CodeNOW’s user interface with just a few clicks.
Step 1: Select a deployment target
- Navigate to the Application Detail screen of the target application.
- Click Create New Configuration in the Deployment Configurations section.
- Select an environment and an application package (Deployment Target).
Step 2: Edit the relevant configuration files
After Step 1 is finalized, CodeNOW’s user interface will display application configuration files for each component of the chosen application package. You can then:
- Individually select the configuration files that you wish to edit (click on the configuration file link to display/hide the configuration file contents).
- Edit the file with the embedded text editor.
The embedded text editor implements keyboard shortcuts for recurring editing needs (e.g., find, replace, indent, rectangular text selection, multiple cursor). Those shortcuts aim at making CodeNOW users update configuration files faster. Power users will appreciate them!
Step 3: Review and create the new deployment configuration
After Step 2 is finalized, you can quickly review your changes and click Confirm to request the creation of the new deployment configuration. You will then be redirected to the Deploy Application screen. From there, you may:
- Continue the deployment process and deploy the application package with the newly created deployment configuration.
- Return to the Application Detail screen.
The newly created deployment configuration will appear together with the previously existing deployment configurations in the Deployment Configurations section of the Application Detail screen. Note that there is no need to name deployment configurations — they are uniquely identified by their deployment target, i.e., the target environment and the application package’s version. Similarly, if you create a new deployment configuration for a deployment target that already has one, you will in fact edit the existing deployment configuration. In other words, have no doubts: there is only ever one deployment configuration per deployment target!
CodeNOW strives to minimize your configuration work by reusing one of your previous deployment configurations when you do not specify one. For more information, see Deployment configurations
Edit a deployment configuration
- Existing deployment configuration
Modify a deployment configuration
You can review the list of existing deployment configurations for an application by navigating to the Application Detail screen for that application (section Deployment Configurations).
You can use the search input field to look for a specific target environment or application package version. Once you have found the deployment configuration you are looking for, click on Edit to edit the deployment configuration.
Create/Modify configuration files in an application component's repository
CodeNOW strives to speed up your development process by having scaffolders for a set of predefined technology stacks (e.g., Java/Maven). Each of those scaffolders comes with default configuration files. You can modify these files at will by simply committing your changes to the component's repository.
CodeNOW also lets you define custom stacks. Create and edit configuration files for your components in the
For more information on creating custom stacks, see Custom stacks.
- You have created the related components in CodeNOW.
Modify configuration files
Application components' configuration files are located in the
runtime-configuration.js file in the