Kamil MrModest

🗓️ Daily Thinking Sheet

Date: ____________
Context (e.g. work / personal / mixed): ___________________

1. 🔄 What’s On My Mind

Quick dump of topics, ideas, or problems bouncing around in your head.

tags
meta

function getMonday(date) {
    const dayOfWeek = date.getDay();
    const diff = dayOfWeek >= 1 // 1 - for 'Monday', for Sunday - it will be '0'
      ? dayOfWeek - 1 // 1 - for 'Monday', for Sunday - it will be '0'
      : 6 - dayOfWeek;

	stacks:
	- name: authentik
	containers:
	- name: server
	image: ghcr.io/goauthentik/server
	version: 2025.6.4
	user: apps
	groups: [apps, sambashare]
	volumes:
	- /media

	{
	"annotations": {
	"list": [
	{
	"builtIn": 1,
	"datasource": {
	"type": "grafana",
	"uid": "-- Grafana --"
	},
	"enable": true,

	- .vault/
	- settings.yml
	- templates/
	- 7d6bc389-05af-46c7-b06b-a5b546fb99d3.yml
	- db/
	- db.sqlite // or Redis
	- notes/
	- cd5428b3-9d99-41f7-940f-0765a145ae83.md // or 1726839184.md
	- assets/
	- 960cd651-d3a4-482f-b5eb-119299f9ddc7.png

	# src/composes/immich/compose.d8s.yml
	kind: compose
	name: {{ .Name }}
	serviceCommons: # shortcut to describe the same property value for each service
	user: {{ .User }}
	restart: {{ .RestartMode }}
	networks:
	- {{ .Networks.ReverseProxy }}
	env: {{ .Name }}_envs # id of `env_vars` kind file
	services:

	data class Playbook(
	val name: String,
	val hosts: Host[],
	val remoteUser: User,
	val varFiles: File[],
	val vars: ObjectNode // need valitation so root will be only Map
	val tasks: Task[]
	)

	sealed class ObjectNode {

	/*
	The idea behind it to make something like 'TravelerBuddy', but simplier. Easy to write and easy to read.
	Just to have a chronological plan of points of interests and all crucial parts of journey. Also, to have all crucial info handy.

	Backend is as simple as a CRUD (if you aren't planned to implement multi-user/authorization support).
	The most work is expected on Frondend side. It needs to provide a convenient and very specific form for each TripItem.
	And also draw a "graph" like below.

	No need to support autocompletion for Address. It's enought to support "open in Map" feature. So even no needs in having a build-in map view.

	<!--
	Fields: Übersetzung; Artikel; Nomen; Plural; Beispiel
	-->

	{{FrontSide}} <!-- {{Übersetzung}} -->

	<hr id=answer>

	<span class="{{Artikel}}"><b>{{Artikel}}</b> {{Nomen}}</span>

	locals {
	stack_name = "immich"
	}