dchuk dchuk

lnr Work Management System

Overview

lnr is an append-only, file-based lnr work management system designed for AI coding agents. Lnr work is organized into phases - coherent units of effort that match how AI agents naturally operate. The system requires no indices, no status tracking, and no complex tooling. State is derived entirely from which files exist in the directory.

Core Principles

Lnr work happens in phases, not issues or tickets. Each phase represents a coherent push toward a specific goal. Phases can be small (refactor a function) or large (implement authentication system).

How to deploy a Rails 7.1 app with Postgres and Kamal on a single server

I think you have looked at the tutorial from Mr. Heinemeier Hansson at least once or twice and have a similar setup.

rails new kamal_pg --css tailwind --skip-test --database=postgresql

cd kamal_pg

Weekly Agenda (created on a different day, and embedded with /Block Reference)
[[Morning Questions]]
- {{[[slider]]}} How many hours of sleep did I get?
- What's one thing top of mind today?
- What's the one thing I need to get done today to make progress?
- Review #[[Index: Questions]] #values
Agenda
- {{[[TODO]]}} Morning walk #goal-health #habit
- {{[[TODO]]}} Check calendar for scheduled events
{{[[TODO]]}} Morning focus hour

	CONFIG WAS UPDATED - SEE COMMENTS

	DEPRECATED
	# This file contains pin mappings for the NON stock 2020 Creality Ender 3
	# with the 32-bit Creality 4.2.2 board. To use this config, during
	# "make menuconfig" select the STM32F103 with a "28KiB bootloader" and
	# serial (on USART1 PA10/PA9) communication.
	# adapted for my printer ender3-4.2.2 with some modifications and without the BLTouch.

	# If you prefer a direct serial connection, in "make menuconfig"

	import plotly.graph_objects as go
	import pandas as pd

	def serp_heatmap(df, num_domains=10, select_domain=None):
	df = df.rename(columns={'domain': 'displayLink',
	'searchTerms': 'keyword'})
	top_domains = df['displayLink'].value_counts()[:num_domains].index.tolist()
	top_domains = df['displayLink'].value_counts()[:num_domains].index.tolist()
	top_df = df[df['displayLink'].isin(top_domains) & df['displayLink'].ne('')]

	# Rails production setup via SQLite3 made durable by https://litestream.io/
	# Copy this to Dockerfile on a fresh rails app. Deploy to fly.io or any other container engine.
	#
	# try locally: docker build . -t rails && docker run -p3000:3000 -it rails
	#
	# in production you might want to map /data to somewhere on the host,
	# but you don't have to!
	#
	FROM ruby:3.0.2

	# set ruby/rails version
	export DOCKER_RAILS_VERSION="7.0.1"
	export DOCKER_RUBY_VERSION="3.1.0"
	export RAILS_PROJECT_NAME="rails7"
	# create folder for the project and add Gemfile with necessary rails version
	mkdir "$RAILS_PROJECT_NAME"
	cd "$RAILS_PROJECT_NAME"
	echo "ruby '$DOCKER_RUBY_VERSION'
	source 'https://rubygems.org'
	gem 'rails', '$DOCKER_RAILS_VERSION'" > Gemfile

	# This file contains pin mappings for the Creality "v4.2.7" board. To
	# use this config, during "make menuconfig" select the STM32F103 with
	# a "28KiB bootloader" and serial (on USART1 PA10/PA9) communication.

	# If you prefer a direct serial connection, in "make menuconfig"
	# select "Enable extra low-level configuration options" and select
	# serial (on USART3 PB11/PB10), which is broken out on the 10 pin IDC
	# cable used for the LCD module as follows:
	# 3: Tx, 4: Rx, 9: GND, 10: VCC

	FROM ruby:3.0-alpine

	RUN apk add --no-cache --update \
	ack \
	bash \
	build-base \
	curl \
	git \
	htop \
	less \

	// This code is to be used with https://turbo.hotwire.dev. By default Turbo keeps visited pages in its cache
	// so that when you visit one of those pages again, Turbo will fetch the copy from cache first and present that to the user, then
	// it will fetch the updated page from the server and replace the preview. This makes for a much more responsive navigation
	// between pages. We can improve this further with the code in this file. It enables automatic prefetching of a page when you
	// hover with the mouse on a link or touch it on a mobile device. There is a delay between the mouseover event and the click
	// event, so with this trick the page is already being fetched before the click happens, speeding up also the first
	// view of a page not yet in cache. When the page has been prefetched it is then added to Turbo's cache so it's available for
	// the next visit during the same session. Turbo's default behavior plus this trick make for much more responsive UIs (non SPA).