hassio-addons/addon-vscode
1
0
Fork 0
mirror of https://github.com/hassio-addons/addon-vscode.git synced 2025-05-03 18:51:23 +00:00
Code Issues Projects Releases Packages Wiki Activity

✨ Add support for setting the default configuration path

Browse source
This commit is contained in:
Franck Nijhof 2020-09-15 10:19:06 +02:00
parent 97c35599ad
commit 35cad4b5fd
No known key found for this signature in database
GPG key ID: D62583BA8AB11CA3
4 changed files with 37 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

31
vscode/DOCS.md
View file

@ -31,6 +31,7 @@ Example add-on configuration:
```yaml
log_level: info
config_path: /share/my_path
packages:
- mariadb-client
init_commands:
@ -49,7 +50,7 @@ dealing with an unknown issue. Possible values are:
- `debug`: Shows detailed debug information.
- `info`: Normal (usually) interesting events.
- `warning`: Exceptional occurrences that are not errors.
- `error`: Runtime errors that do not require immediate action.
- `error`: Runtime errors that do not require immediate action.
- `fatal`: Something went terribly wrong. Add-on becomes unusable.
Please note that each level automatically includes log messages from a
@ -57,6 +58,14 @@ more severe level, e.g., `debug` also shows `info` messages. By default,
the `log_level` is set to `info`, which is the recommended setting unless
you are troubleshooting.
### Option: `config_path`
This option allows you to override the default path the add-on will open
when accessing the web interface. For example, use a different
configuration directory like `/share/myconfig` instead of `/config`.
When not configured, the addon will automatically use the default: `/config`
### Option: `packages`
Allows you to specify additional [Ubuntu packages][ubuntu-packages] to be
@ -128,13 +137,13 @@ will come up with a better solution for this soon.
- "Visual Studio Code is unable to watch for file changes in this large
workspace" (error ENOSPC)
This issue is caused by your system not having enough file handles,
which causes VSCode to be unable to watch all your files. For HassOS,
currently the only option is to click on the little cog when the
notification appears and tell it to not show again. In case you have
a generic Linux setup (e.g., Ubuntu), follow this guide by Microsoft:
This issue is caused by your system not having enough file handles,
which causes VSCode to be unable to watch all your files. For HassOS,
currently the only option is to click on the little cog when the
notification appears and tell it to not show again. In case you have
a generic Linux setup (e.g., Ubuntu), follow this guide by Microsoft:
<https://code.visualstudio.com/docs/setup/linux#_visual-studio-code-is-unable-to-watch-for-file-changes-in-this-large-workspace-error-enospc>
<https://code.visualstudio.com/docs/setup/linux#_visual-studio-code-is-unable-to-watch-for-file-changes-in-this-large-workspace-error-enospc>
## Changelog & Releases
@ -143,12 +152,12 @@ functionality. The format of the log is based on
[Keep a Changelog][keepchangelog].
Releases are based on [Semantic Versioning][semver], and use the format
of ``MAJOR.MINOR.PATCH``. In a nutshell, the version will be incremented
of `MAJOR.MINOR.PATCH`. In a nutshell, the version will be incremented
based on the following:
- ``MAJOR``: Incompatible or major changes.
- ``MINOR``: Backwards-compatible new features and enhancements.
- ``PATCH``: Backwards-compatible bugfixes and package updates.
- `MAJOR`: Incompatible or major changes.
- `MINOR`: Backwards-compatible new features and enhancements.
- `PATCH`: Backwards-compatible bugfixes and package updates.
## Support