Fix markdownlint issues in notes
Some checks failed
CI / skip-ci-check (pull_request) Successful in 1m15s
CI / markdown-lint (pull_request) Failing after 1m18s
CI / yaml-validate (pull_request) Successful in 1m18s

This commit is contained in:
ilia 2025-12-30 23:05:47 -05:00
parent 835735a238
commit 7293e8a477
4 changed files with 11 additions and 3 deletions

View File

@ -2,3 +2,5 @@
# Notes repo: long lines (IPs, commands, URLs) are common. # Notes repo: long lines (IPs, commands, URLs) are common.
config: config:
MD013: false MD013: false
# Notes often use inline citation tokens like [web:123] (not real reference-style links).
MD052: false

View File

@ -144,4 +144,3 @@ sudo systemctl disable --now lightdm.service
``` ```
This gives you a reliable text console, and you can work purely over SSH for GPU workloads. This gives you a reliable text console, and you can work purely over SSH for GPU workloads.

View File

@ -112,7 +112,7 @@ Within **Tools → Options → Downloads**:
Use official torrents for testing: Use official torrents for testing:
- Debian images and torrents: https://www.debian.org/download [web:150] - Debian images and torrents: [debian.org/download](https://www.debian.org/download) [web:150]
- ArchWiki and other docs confirm Web UI default at `http://HOST_IP:8080` for verification. [web:146] - ArchWiki and other docs confirm Web UI default at `http://HOST_IP:8080` for verification. [web:146]
Add a magnet link or `.torrent` via **Add Torrent** in the Web UI and confirm files appear under `/data/Downloads`. Add a magnet link or `.torrent` via **Add Torrent** in the Web UI and confirm files appear under `/data/Downloads`.

View File

@ -18,6 +18,7 @@ Accessible at: `http://<LXC-IP>:3456/` (example: `http://10.0.10.159:3456/`).
Initial apt errors (“Temporary failure resolving `deb.debian.org` / `security.debian.org`”) were due to no route + bad DNS in the container. Initial apt errors (“Temporary failure resolving `deb.debian.org` / `security.debian.org`”) were due to no route + bad DNS in the container.
Fixed by: Fixed by:
- Setting the containers network device to bridge `vmbr0` with IPv4 DHCP and restarting the LXC. - Setting the containers network device to bridge `vmbr0` with IPv4 DHCP and restarting the LXC.
- Ensuring `/etc/resolv.conf` has working nameservers (router IP or `1.1.1.1`, `8.8.8.8`). - Ensuring `/etc/resolv.conf` has working nameservers (router IP or `1.1.1.1`, `8.8.8.8`).
@ -126,6 +127,7 @@ services:
``` ```
Replace: Replace:
- `10.0.10.159` with your LXC IP (or domain if you add a reverse proxy). - `10.0.10.159` with your LXC IP (or domain if you add a reverse proxy).
- `<your-hex-secret>` with a strong hex string: - `<your-hex-secret>` with a strong hex string:
@ -161,6 +163,7 @@ pq: password authentication failed for user "vikunja"
``` ```
Check that in `docker-compose.yml`: Check that in `docker-compose.yml`:
- `POSTGRES_USER` == `VIKUNJA_DATABASE_USER` - `POSTGRES_USER` == `VIKUNJA_DATABASE_USER`
- `POSTGRES_PASSWORD` == `VIKUNJA_DATABASE_PASSWORD` - `POSTGRES_PASSWORD` == `VIKUNJA_DATABASE_PASSWORD`
- `POSTGRES_DB` == `VIKUNJA_DATABASE_DATABASE` - `POSTGRES_DB` == `VIKUNJA_DATABASE_DATABASE`
@ -204,12 +207,14 @@ ping -c 3 deb.debian.org
### Vikunja keeps restarting ### Vikunja keeps restarting
Check `docker logs vikunja`: Check `docker logs vikunja`:
- DB auth error → fix credentials; reset DB if necessary. - DB auth error → fix credentials; reset DB if necessary.
- Other config errors → verify env vars (DB host/type, public URL, JWT secret). - Other config errors → verify env vars (DB host/type, public URL, JWT secret).
## Data and backups ## Data and backups
Per Vikunja docs, back up: Per Vikunja docs, back up:
- DB data: `/opt/vikunja/db` - DB data: `/opt/vikunja/db`
- Files: `/opt/vikunja/files` - Files: `/opt/vikunja/files`
@ -237,6 +242,7 @@ Ensure `/opt/vikunja/pg-dumps` is included in backups.
### Projects (namespaces) ### Projects (namespaces)
Projects in the sidebar: Projects in the sidebar:
- Family - Family
- Personal - Personal
- Properties - Properties
@ -247,12 +253,14 @@ Each project is its own list/board with multiple views (List, Gantt, Table, Kanb
### Labels ### Labels
Current labels: Current labels:
- **Context**: `@home`, `@computer`, `@call`, `@errands` - **Context**: `@home`, `@computer`, `@call`, `@errands`
- **Areas**: Finance, Health, Legal, Maintenance, Deep - **Areas**: Finance, Health, Legal, Maintenance, Deep
- **People**: Izik, Zane, Zoey - **People**: Izik, Zane, Zoey
- **Properties**: `#122`, `#153`, `#284`, `#45`, `#6`, `5`, `15` - **Properties**: `#122`, `#153`, `#284`, `#45`, `#6`, `5`, `15`
Suggestions: Suggestions:
- Normalize properties, e.g. `P-122`, `P-153`, etc. - Normalize properties, e.g. `P-122`, `P-153`, etc.
- Add time/energy labels like `5min`, `15min`, “Low energy”, “High energy” for better filtering. - Add time/energy labels like `5min`, `15min`, “Low energy”, “High energy” for better filtering.
@ -266,4 +274,3 @@ Use filters to combine labels (e.g. `@computer` + Deep, `P-122` + Maintenance).
- Full Docker example: `https://vikunja.io/docs/full-docker-example/` - Full Docker example: `https://vikunja.io/docs/full-docker-example/`
- What to back up: `https://vikunja.io/docs/what-to-backup/` - What to back up: `https://vikunja.io/docs/what-to-backup/`
- Community: `https://community.vikunja.io/` - Community: `https://community.vikunja.io/`