|
| 1 | +--- |
| 2 | +layout: docs |
| 3 | +title: Project settings |
| 4 | +description: Project settings tell Codewind the specifics of your project and application |
| 5 | +keywords: project, settings, Codewind, application, configuring, workspace |
| 6 | +duration: 1 minute |
| 7 | +permalink: project-settings |
| 8 | +type: document |
| 9 | +order: 4 |
| 10 | +parent: developing-projects |
| 11 | +--- |
| 12 | + |
| 13 | +# Project settings |
| 14 | + |
| 15 | +Project settings tell Codewind more about the specifics of your project and can affect the status or behavior of your application. Project settings can be configured from the `Project Overview` page that is accessible from a project's context menu. You can also find the project settings in the `.cw-settings` file of the project which you can edit from the IDE. The workspace automatically picks up changes to these fields. |
| 16 | + |
| 17 | +Supported project settings include: |
| 18 | +* [Context root](#context-root) |
| 19 | +* [Health check endpoint](#health-check-endpoint) |
| 20 | +* [HTTPS application](#https-application) |
| 21 | +* [Internal application port](#internal-application-port) |
| 22 | +* [Internal debug port](#internal-debug-port) |
| 23 | +* [Maven profiles](#maven-profiles) |
| 24 | +* [Maven properties](#maven-properties) |
| 25 | +* [Paths to ignore for file changes](#paths-to-ignore-for-file-changes) |
| 26 | +* [Project status ping timeout](#project-status-ping-timeout) |
| 27 | + |
| 28 | +## **Context root** |
| 29 | +`contextRoot: <string>` |
| 30 | +- Codewind uses the value to determine the project state. |
| 31 | +- When the Open Application action is used, it uses the value as the initial endpoint. |
| 32 | +- If an incorrect context root is set, the project continuously pings the wrong endpoint, keeping the project stuck in the starting state. |
| 33 | +- If the health check endpoint is set, the context root is not used to determine the project state. |
| 34 | +- If the value is not set, the default value is `/`. |
| 35 | + |
| 36 | +## **Health check endpoint** |
| 37 | +`healthCheck: <string>` |
| 38 | +- Codewind uses the value to determine the project state. |
| 39 | +- Codewind expects to use this value for the application health check endpoint. |
| 40 | +- If a wrong health check endpoint is set, the project continuously pings the wrong endpoint, keeping the project stuck in the starting state. |
| 41 | +- If the health check endpoint is set, the context root is not used to determine the project state. |
| 42 | +- If the value is not set, the default value is `/`. |
| 43 | + |
| 44 | +## HTTPS application |
| 45 | +`isHttps: <boolean>` |
| 46 | +- This value tells Codewind to use the HTTPS protocol when Codewind detects the application status, and also when Codewind launches the application in a browser. |
| 47 | +- If your application supports HTTPS, set `isHttps` to `true`, and Codewind uses HTTPS instead of HTTP to detect the application status and to open browser URLs. |
| 48 | +- The default value of this setting is `false`. |
| 49 | + |
| 50 | +## **Internal application port** |
| 51 | +`internalPort: <string>` |
| 52 | +- Codewind gets the port from the container information, so by default, the port is the same as the one exposed in Dockerfile. |
| 53 | +- Codewind uses the value in conjunction with the context root to determine the project state. |
| 54 | +- If an incorrect port is set, the project continuously pings the wrong endpoint, keeping the project stuck in the starting state. |
| 55 | + |
| 56 | +## **Internal debug port** |
| 57 | +`internalDebugPort: <string>` |
| 58 | +- Only applicable to Microprofile, Spring and Node.js projects. |
| 59 | +- Only applicable to a local installation of Codewind. |
| 60 | +- Can be assigned to a non-exposed port, then Codewind helps expose the port for you. |
| 61 | +- If the project is already in debug mode, restart the project in debug mode in order to pick up the new debug port. |
| 62 | +- If the project is in run mode, the next restart picks up and uses the new debug port and completes a debug mode. |
| 63 | + |
| 64 | +## **Paths to ignore for file changes** |
| 65 | +`ignoredPaths: <string[]>` |
| 66 | +- A list of file paths that indicate a build must be triggered on file change events in relation to the paths. |
| 67 | +- Each item is expected to be a regex (`"*/node_modules*"` ) or a path relative to the project's root directory (`"/README.md"`). |
| 68 | + |
| 69 | +## **Maven profiles** |
| 70 | +`mavenProfiles: <string[]>` |
| 71 | +- Only applicable to Microprofile and Spring projects. |
| 72 | +- Set a list of profiles if your project requires to use additional Maven profiles when Codewind issues Maven commands. |
| 73 | +- Do not overwrite nor remove the microclimate profile. |
| 74 | +- Maven profiles can be used in conjunction with Maven properties. |
| 75 | + |
| 76 | +## **Maven properties** |
| 77 | +`mavenProperties: <string[]>` |
| 78 | +- Only for Microprofile and Spring projects. |
| 79 | +- Maven properties can be entered in the form `key=value`. |
| 80 | +- Do not overwrite the microclimate property. |
| 81 | +- Maven properties can be used in conjunction with Maven profiles. |
| 82 | + |
| 83 | +## Project status ping timeout |
| 84 | +`statusPingTimeout: <string>` |
| 85 | +- This value is the total number of pings used by Codewind to determine if the project has timeout issues during the starting state. |
| 86 | +- Each ping takes 2 seconds. For example, if the value is set to 30 seconds, the timeout is 60 seconds. |
| 87 | +- If the value is not set, the default value is set to `90` (3 minutes) for Appsody projects, and `30` (1 minute) for all other project types. |
0 commit comments