After you are redirected to your IDE, click File > Preferences > Open Settings.
Identify the section containing the setting that you want to edit, and then click the section header to display all possible values.
Change the desired setting.
The following screen shows an example setting:
Note
User preferences exist in the ~/.theia/settings.json file. Do not change this file as Acquia can overwrite it with new features and values.
Workspace preferences exist in the ~/project/.theia/settings.json file after you perform a change. This file has precedence over User preferences and includes custom settings.
Usually, Cloud IDE immediately uses your updated preferences. However, for certain preferences, you might need to reload the full page.
Tracking Cloud IDE preferences under version control
By design, Cloud IDEs are disposable. As such, you might want to delete an IDE or have multiple IDEs in parallel, and carry forward your preferences without having to configure new IDEs from scratch.
When the ~/project/.theia/settings.json file is available, it’s easy to add it to version control and track changes as part of your Cloud Platform application.
To track your Workspace settings.json file:
Verify that the .theia directory is currently not tracked under version control.
ide:~/project (master) $ git status
On branch master
Untracked files:
(use "git add <file>..." to include in what will be committed)
.theia/
nothing added to commit but untracked files present (use "git add" to track)
Add the .theia directory to your Git repository and verify that the changes are ready to be committed.
ide:~/project (master) $ git add .theia/ && git status
On branch master
Changes to be committed:
(use "git restore --staged <file>..." to unstage)
new file: .theia/settings.json
After you are redirected to your IDE, click File > Preferences > Open Settings.
Identify the section containing the setting that you want to edit, and then click the section header to display all possible values.
Change the desired setting.
The following screen shows an example setting:
Note
User preferences exist in the ~/.theia/settings.json file. Do not change this file as Acquia can overwrite it with new features and values.
Workspace preferences exist in the ~/project/.theia/settings.json file after you perform a change. This file has precedence over User preferences and includes custom settings.
Usually, Cloud IDE immediately uses your updated preferences. However, for certain preferences, you might need to reload the full page.
Tracking Cloud IDE preferences under version control
By design, Cloud IDEs are disposable. As such, you might want to delete an IDE or have multiple IDEs in parallel, and carry forward your preferences without having to configure new IDEs from scratch.
When the ~/project/.theia/settings.json file is available, it’s easy to add it to version control and track changes as part of your Cloud Platform application.
To track your Workspace settings.json file:
Verify that the .theia directory is currently not tracked under version control.
ide:~/project (master) $ git status
On branch master
Untracked files:
(use "git add <file>..." to include in what will be committed)
.theia/
nothing added to commit but untracked files present (use "git add" to track)
Add the .theia directory to your Git repository and verify that the changes are ready to be committed.
ide:~/project (master) $ git add .theia/ && git status
On branch master
Changes to be committed:
(use "git restore --staged <file>..." to unstage)
new file: .theia/settings.json