which will result in a params hash { “submit” => “foo”} making params more easily handleable and keeps the button label uncommitted to the value.

SELECT r.rolname, d.datname, rs.setconfig
FROM   pg_db_role_setting rs
LEFT   JOIN pg_roles      r ON r.oid = rs.setrole
LEFT   JOIN pg_database   d ON d.oid = rs.setdatabase
WHERE  r.rolname = 'immich' OR d.datname = 'immich';

this shows the defaults in the current schema, here it was immich db and user, but for some reason it had mattermost as a result.

alter database immich set search_path = "$user", public ;

fixed this

what fixed it was looking up the oid and then just removing all its entries.

select from pg_depend where objid = MY_OID;

delete from pg_class where oid = MY_OID;
delete from pg_depend where objid = MY_OID;
delete from pg_constraint where conrelid = MY_OID;

might be very invasive, the state of that dataset was not too important.

Why we need this

If you are building your application with Hotwire, your Turbo streams will likely add, remove, and replace some HTML nodes. This mostly works except when you want to add HTML that comes with some JavaScript. Like a file picker, Trix editor, and the like.

Turbo itself won’t do anything about this. It’s a rather simple tool with simple purpose. JavaScript initialization should come with the HTML Turbo is about to add. Hotwire solves this with Stimulus.

The Hotwire way

The Hotwire answer to the problem is Stimulus controllers. Stimulus is build on top of MutationObserver which is a browser API providing the ability to watch for changes being made to the DOM.

When a Stimulus controller appears on the page, its connect method is called automatically. If our HTML doesn’t come with a Stimulus controller, we should create a new controller and put our initialization code inside its connect method:

// app/javascript/controllers/my_controller.js
import { Controller } from "@hotwired/stimulus"

export default class extends Controller {
  connect() {
    // Code to initialize something
  }
}

Then we simply add the controller to an element inside our Turbo Stream:

<turbo-stream>
  <div data-controller="my-controller">
  	Something that needs to be initialize with JavaScript.
  </div>
</turbo-stream>

When Stimulus is not an option

Sometimes Stimulus might not be what we want and we would love to have a Turbo Stream event to hook into anyways.

Luckily, Steve shared his little implementation of turbo:after-stream-render in this thread:

// application.js
const afterRenderEvent = new Event("turbo:after-stream-render");
addEventListener("turbo:before-stream-render", (event) => {
  const originalRender = event.detail.render

  event.detail.render = function (streamElement) {
    originalRender(streamElement)
    document.dispatchEvent(afterRenderEvent);
  }
})

As you can see, the idea is quite simple. We create a new custom Event and add an event listener for turbo:before-stream-render which already exist. We then run our event after we are done with original rendering.

To use it we create an event listener and paste the JavaScript that needs to run after rendering:

document.addEventListener("turbo:after-stream-render", () => {
  console.log("I will run after stream render")
});

<% if course_registration_form.errors[:email].any? %>
	<%= content_tag(:p, course_registration_form.errors[:email].first, class: "mt-2 text-sm text-red-600") %>
<% end %>

however, if you have a custom validation that groups errors on an arbitrary key that is not backed by an object’s attribute, you have to query differently:

<% if course_registration_form.errors.where(:person_info).any? %>
	<%= content_tag(:p, course_registration_form.where(:person_info).map(&:message), class: "mt-2 text-sm text-red-600") %>
<% end %>

env settings RAILS_ENV=staging RACK_ENV=staging

Application.css looks like this:

```css
@import "tailwindcss";

@theme {
	--brand-color: oklch(0.35 0.2153 266.44);
}

@layer base {
	html {
		@apply text-(--brand-color);
	}
}

so the color gets defined in the @theme directive, and it then gets applied by the base layer.

There are other ways, but this seems to me the cleanest, and when universally needed, the right choice.

Maybe when dynamic application of themes is important, it might be easier to manipulate the body tag like so:

<body class="text-{color}">

wwwwwwwwwwwwwwwwwyou might still have to define the color somewhere if it is a custom choice.

SELECT
    schemaname || '.' || tablename AS table_full_name,
    pg_size_pretty(pg_total_relation_size(quote_ident(schemaname) || '.' || quote_ident(tablename))) AS total_size
FROM pg_tables
WHERE schemaname NOT IN ('pg_catalog', 'information_schema')
ORDER BY pg_total_relation_size(quote_ident(schemaname) || '.' || quote_ident(tablename)) DESC;

Count mysql table rows (approximate)

SELECT 
    TABLE_SCHEMA,
    TABLE_NAME,
    TABLE_ROWS
FROM 
    information_schema.TABLES
WHERE 
    TABLE_TYPE = 'BASE TABLE'
    AND TABLE_SCHEMA NOT IN ('mysql', 'information_schema', 'performance_schema', 'sys')
ORDER BY 
    TABLE_ROWS DESC;

show mysql table size

SELECT 
    TABLE_SCHEMA,
    TABLE_NAME,
    ROUND((DATA_LENGTH + INDEX_LENGTH) / 1024 / 1024, 2) AS size_mb
FROM 
    information_schema.TABLES
WHERE 
    TABLE_TYPE = 'BASE TABLE'
    AND TABLE_SCHEMA NOT IN ('mysql', 'performance_schema', 'information_schema', 'sys')
ORDER BY 
    size_mb DESC;

show all unique values in a column

SELECT DISTINCT your_column
FROM your_table;

Tailscale version 1.54 or later used with a Linux 6.2 or later kernel enables UDP throughput improvements using transport layer offloads. If a Linux device is acting as an exit node or subnet router, ensure the following network device configuration is in place for the best results:

NETDEV=$(ip -o route get 8.8.8.8 | cut -f 5 -d " ")
sudo ethtool -K $NETDEV rx-udp-gro-forwarding on rx-gro-list off

By default, changes made using the ethtool don’t persistent after a reboot. On Linux distributions using networkd-dispatcher (which you can verify with systemctl is-enabled networkd-dispatcher), you can run the following commands to create a script that configures these settings on each boot.

printf '#!/bin/sh\n\nethtool -K %s rx-udp-gro-forwarding on rx-gro-list off \n' "$(ip -o route get 8.8.8.8 | cut -f 5 -d " ")" | sudo tee /etc/networkd-dispatcher/routable.d/50-tailscale
sudo chmod 755 /etc/networkd-dispatcher/routable.d/50-tailscale

Run the following commands to test the script to ensure it runs successfully on your devices:

sudo /etc/networkd-dispatcher/routable.d/50-tailscale
test $? -eq 0 || echo 'An error occurred.'