clarkbw

Signal K plugins, by type — a community taxonomy

A working categorisation of the published Signal K plugin ecosystem, with the maintained/core plugins sorted into each type. Meant as an orientation map: "what kind of plugin is this, and what else lives in the same bucket?"

Data source: npm signalk-node-server-plugin keyword index (~479 packages), the @signalk npm scope, and github.com/SignalK, surveyed 2026-06-20. This is not exhaustive — it covers the maintained + historically-important core (~80 plugins), not the full long tail. Version/date stamps are point-in-time; re-query npm before trusting a "stale" verdict. Corrections welcome.

How the App Store works (context)

• The in-server App Store is a live npm keyword query — anything published with signalk-node-server-plugin (server plugins), signalk-webapp (webapps), or signalk-embeddable-webapp (components) shows up. No human curation.
• The @signalk/* scope marks officially-owned packages; the App Store lists everythi

clarkbw

Proposal: A received-message log in signalk-server core (DSC first)

Working draft for discussion, off the back of Teppo's suggestion (Discord) that the signalk-dsc plugin's call log become a first-class server feature.

Goal

A first-class log of received digital messages in signalk-server: a data model the server owns, a query/manipulate REST API in the likeness of the History API, and (later) a Kip-style panel like the autopilot control panel. DSC is the first

clarkbw

case
    when host like '%cluster-%.rds.amazonaws.com%' then 'Aurora'
    when host like '%rds.amazonaws.com%' then 'RDS'
    when host like 'ec2%' then 'EC2 Self-Hosted'
    when host like '%supabase.co%' then 'Supabase' -- db.project.supabase.co & region.supabase.com
    when host like '%timescale.com%' then 'Timescale'
    when host like '%postgres.vercel-storage.com%' then 'Vercel Postgres'
    when host like '%azure.neon.tech%' then 'Neon (Azure)'
    when host like '%aws.neon.tech%' then 'Neon (AWS)'
    when host like '%.turso.io%' then 'Turso'

clarkbw

name: PR Review
on:
  # Run this workflow on every PR event. Existing review apps will be updated when the PR is updated.
  # Neon branches are created and removed according to PR updates
  pull_request:
    types: [opened, reopened, synchronize, closed]

jobs:
  pr-preview:
    runs-on: ubuntu-latest

clarkbw

-- get existing index names and SQL definitions
SELECT indexname, indexdef
FROM pg_indexes
WHERE schemaname = 'public' AND tablename = 'table'
ORDER BY indexname;

-- create new tmp index (example)
CREATE INDEX tmp_name_of_the_index ON public.table USING btree (time ASC);
-- drop existing index
DROP INDEX name_of_the_index;

clarkbw

-- bring all examples together and clean up with some top level variables
WITH vars AS (
    SELECT INTERVAL '1 day' AS bucket,
    (now() - INTERVAL '3 months') as time_from,
    (now() + INTERVAL '1 month') as time_to
)

-- generate timeline into the past and future
,
timeline AS (

clarkbw

class ActionsHypertable < ActiveRecord::Migration[7.0]
  def change
    @table_name = 'actions'
    @time_column = 'created_at'
    reversible do |dir|
      dir.up do
        execute <<-SQL
          SELECT create_hypertable('#{@table_name}', '#{@time_column}', if_not_exists => TRUE, migrate_data => TRUE);
        SQL
      end

clarkbw

SELECT s.schemaname,
       s.relname AS tablename,
       s.indexrelname AS indexname,
       pg_size_pretty(pg_relation_size(s.indexrelid)) AS index_size
FROM pg_catalog.pg_stat_user_indexes s
   JOIN pg_catalog.pg_index i ON s.indexrelid = i.indexrelid
WHERE s.idx_scan = 0      -- has never been scanned
  AND 0 <>ALL (i.indkey)  -- no index column is an expression
  AND NOT i.indisunique   -- is not a UNIQUE index
  AND NOT EXISTS          -- does not enforce a constraint

clarkbw

<script>
{
	let a = "foo";
}
{
	let b = 42; // set breakpoint here: debugger shows b == "foo"!
}
</script>

clarkbw

const timing = store => next => action => {
  performance.mark(`${action.type}_start`);
  let result = next(action);
  performance.mark(`${action.type}_end`);
  performance.measure(
    `${action.type}`,
    `${action.type}_start`,
    `${action.type}_end`
  );
  return result;