docs(README): set line length to 120

This commit is contained in:
2025-10-13 07:32:10 +02:00
parent 9c4c8396a2
commit be1824a06f
3 changed files with 31 additions and 20 deletions

View File

@@ -45,9 +45,9 @@ MD012:
# MD013/line-length - Line length
MD013:
# Number of characters
line_length: 80
line_length: 120
# Number of characters for headings
heading_line_length: 80
heading_line_length: 120
# Number of characters for code blocks
code_block_line_length: 80
# Include code blocks
@@ -56,8 +56,6 @@ MD013:
tables: false
# Include headings
headings: true
# Include headings
headers: true
# Strict length checking
strict: false
# Stern length checking
@@ -73,7 +71,7 @@ MD022:
# MD024/no-duplicate-heading/no-duplicate-header - Multiple headings with the same content
MD024:
# Only check sibling headings
allow_different_nesting: true
siblings_only: true
# MD025/single-title/single-h1 - Multiple top-level headings in the same document
MD025:
@@ -128,8 +126,21 @@ MD041:
# MD044/proper-names - Proper names should have the correct capitalization
MD044:
# List of proper names
# names:
# - drone
names:
- Git
- GitDevOps
- Gitea
- GitHub
- GitLab
- GitOps
- kube-prometheus-stack
- Memcached
- Oracle
- PostgreSQL
- Prometheus
- prometheus-exporter
- SSL
- TLS
# Include code blocks
code_blocks: false
@@ -141,4 +152,4 @@ MD046:
# MD048/code-fence-style - Code fence style
MD048:
# Code fence syle
style: "backtick"
style: "backtick"

4
.markdownlintignore Normal file
View File

@@ -0,0 +1,4 @@
.github/
Chart.lock
charts/
node_modules/

View File

@@ -4,8 +4,7 @@
This is a helm chart for [homeassistant](https://github.com/morpheus65535/homeassistant/).
This helm chart can be found on [artifacthub.io](https://artifacthub.io/) and
can be installed via helm.
This helm chart can be found on [artifacthub.io](https://artifacthub.io/) and can be installed via helm.
```bash
helm repo add volker.raschek https://charts.cryptic.systems/volker.raschek
@@ -16,16 +15,13 @@ helm install homeassistant volker.raschek/homeassistant
### Mountpoints
As default all configuration and media files will be stored inside the container
filesystem. Inside the `values.yaml` files the sections `volumes` and
`volumeMounts` to mount additional volumes inside the container. For example to
mount the directories containing configuration and media files on separate
mountpoints. The `values.yaml` contains also some examples to mount the
directories inside the host filesystem.
As default all configuration and media files will be stored inside the container filesystem. Inside the `values.yaml`
files the sections `volumes` and `volumeMounts` to mount additional volumes inside the container. For example to mount
the directories containing configuration and media files on separate mountpoints. The `values.yaml` contains also some
examples to mount the directories inside the host filesystem.
#### Troubleshooting
The application use as backend a sqlite database. If the database is stored on a
network filesystem like nfs, it is quite possible that the application lacks or
is unusable, because sqlite is not designed to be used as a database accesses
over network.
The application use as backend a sqlite database. If the database is stored on a network filesystem like nfs, it is
quite possible that the application lacks or is unusable, because sqlite is not designed to be used as a database
accesses over network.