As anyone can see, programs and code can be either used for liberation, access, and education - or for harassment, intimidation, surveillance, and terrorization.

buymy.codes is a chance to decide properly.

Engineers really fumbled, it seems. The heady rush of early online communication threw us into a frenzy; with hackers leading the charge, and of course hoarding all of the keys to the kingdom they came across - the keys to the engines, machines, and programs.

Threatened by the hackers, the lawyers and business managers huddled up as usual. They decided on the Computer Fraud and Abuse Act, and began criminalizing some common norms of online conduct.

Popular media began to engage in online discussions, through blogs - although the media conglomerates had more reach. The 2000 merger of AOL and Time Warner began to herald the inexhaustible push of cinema and television, their sails full of advertising currents.

Only a couple years earlier in 1998, Google had launched. They now needed to earn their place in competition among AOL, MSN, and Yahoo - all major news sources that could only repackage considerable journalism pieces into click-bait five-minute dead-end reads; the dominant form of media in our reach today.

Far from the public gaze, the machinery of immediate advertising was being passed around; from Facebook to Instagram to Amazon & Google Shopping, the moment was poised to cascade into the current machine-learning hypnoscape. The media had decayed beyond common sense, beyond uncommon sense, into mere commercial (non)sense.

Bad morals became good business, around the same moment Gordon Gekko's resurgence characterized the raison d'être of the modern financial-tech boom. High-speed trading became less fashionable than hyper-speed ad bidding.

Bidding on peoples' conscious energy sure made more sense for business, also - more measurable consequences to be sure. This subcurrent lurked far enough from public gaze to be eerily effective at making us second-guess our human agency in a communication landscape whose rules remained hidden.

Then, only when a small collusion of the most greed-compelled media firms launched a state-capture operation on the American empire, decapitating its figurehead role and replacing it with the tropes and icons of reality television, did we begin to realize that bids on a placement is no measure of an articles' journalistic soul.

Only when we could finaly examine the mechanisms of bidding could we realize that propaganda by hundreds of corporations does as much social damage as the ideologies of a single demagogue. Our generation tasted each flavor in succession.

Soon, the means of propaganda fed a popular ideology; allegiance to corporation and party ahead of land and neighbor. The commerce of high-speed bids began to auction off people, as has happened in the early days of our nation, now sending people already insecure in employment, healthcare, education, into forced migration - labeled as trafficking in any other era, forcing an existential crisis surgically choosing some homes and encouraging bliss, and ignorance-of-any-issue-at-all, in the buildings next door.

Our generation's collection of corporations, who choose to sell people, forcing displacement from home and family bonds, ending a life and career and a home all in one go, so as to punish full nations of people for seeming to scare the old guard of leaders into yelling a bit too loudly and insensibly; as though erasure of an ecology could make some damn crazy men suddenly find peace, and as though we could find peace in the ensuing silence.

Perhaps other means could be found to silence some damn crazy men, before the price of their loudness adds more days and more thousands to the names of those who no longer are.

The propaganda is as banal as ever; uninspired puns, mainly, and designed to inspire only those who are the most desparate for air.

The man whose buddy runs the boring company happens to be bored of peace - and uses the membership role to emphasize his upbringing's forced masculinity by holding the singular profiled lady-on-board in a position under-standing, compared to the clearly-proud dicks surrounding.

The sad piece of propaganda at the core of our problem could be said to be a discussion on deficit; the nation has failed to sell enough, perhaps? Only our advanced manufacturing has long been monogamously embraced to warfare; "selling more" can only mean more munitions, in hands of people eager to cause death.

Our nation, or empire, is pleased and peachy keen to keep an image as the "world's police". Indeed, some American police do sell arms to violent murderers. "America's Finest" are then eager to sell out their customers when payday comes up short.

The shame is inescapable in the propaganda engine also; violent members of the military, alongside any aggressor of the mob or criminal syndicate, are commonly known through the ages as "goons"; they rebranded to pipe hitter, as though that were a nod to the gooner label now passed along to the aimless masses of conscientious objectors. These drugged-under-influence cyber consumers can only seek company to mourn and commiserate, as their chances of peaceful employment now require a passport; and good luck if you can acquire one any more.

If you fail to help in manufacturing the machinery of war, you can help in the planning, the logical complex of code and inference. Or the hospice and venues and psychological healthcare positioned as required brakes on a moving train running too close to the tracks' limits.

Enough has long been enough, and years are going by in the same scenario. The propaganda, as deployed by the thousands of small page-cuts, has displayed more resilience to our demands for sense and decency than we are able to comprehend.

If one is to pursue education, and social upbringing, and humane social roles, then their communications need to challenge the mechanisms of propaganda.

Any challenge to a social problem begins by assailing the biases that reflect the problem in our minds. Propaganda especially occurs in our minds, and so our language and norms of relationship need to be rearranged for more guarded composure.

These are the core philosophical and social underpinnings of a new domain and program by Operand Company; buymy.codes encourages engineers to decide more nuance in the causes and applications their code is used to accomplish.

buymy.codes is going through a build process, in parallel to 0.legal and haiku.space, all based on the nucleus program base.

The design needs include...

• describe a program's aims and boundaries (non-aims).
• describe chosen uses the program's composer espouses.
• ensure uses are humane.
• engage program consumers aligned to chosen usage.
• encourage user pledges in exchange for code access.
• encourage reciprocal payment for coders' energies, by binding pledges to a release cycle. Imagine, rather than "bug bounties", "feature bounties" paid to the publisher.
• encourage modular program design, by packaging small releases.
• fail to equip or arm social aggressors.

Please email your pledges for now; and read more soon.

I missed my handy guidance - the grand plan that I published long ago. I figured enough has changed to rebuild this, and the process was far smoother now; the diagram command is now able to quickly reload the browser (brave, change the code if necessary) for each change I make in my .d2 code. I was done in only a few considerable hours, and could spend more energy rearranging - to keep the dependency lines and my own ideas from colliding too much.

See and zoom the combined map, or click on the images for a zoomable copy.

Real

Cyber

Philosophy teachers say, "All things change."

Economics teachers say, "Some things never change."

Political Science teachers say, "Some things are never changed."

Grammar teachers say, "My career prospects changed."

My remaining grandparents are dying (more quickly each day) and I'm heading away from them towards New York City. I'll likely say goodbye to someone(s) before spring is here, so I suppose this is going to be a cold Michigan winter for me.

I sure am sorry I spent so many years failing at relationships. People can be so complex, and death always renders us so simple.

A peace game is similar to a war game. The same, I suppose, only the rules are more encouraging of diplomacy.

Legislatures Passes Law to Examine Users' Online Presence.

A ring of three mass shootings occur in large cities, within hours of each other. The murderers are each young men, and detectives manage to unlock their computers and gain access to their social media pages. They keep a minimal presence on social media, and their browser histories are all cleaned up.

One of the computers has a folder called ~/.mozilla, and although Firefox is no longer installed, this folder includes the remnants of the users' actions while briefly using Firefox a few months before. The page log displays domain names for a number of forums, and the detectives quickly locate the murderers' social media handles as users on those forums.

A couple weeks of stake-out on the forums earns FBI agents enough permission to glimpse the discussions, leading up to the bloody hour. These three men had corresponded, and been encouraged by peers who preyed on loneliness and isolation, and promised glory and immortality; perhaps the same reason the forum discussions remained inside of semi-public reach.

The forum's users each notched up another rung in the FBI's alarm profiles, and the forum operators gained some new hidden admirers among international intelligence profilers.

The three nations that experienced the murders on this day reached a new echelon of diplomacy, and decided that response is no good in comparison to thorough preparation. Banking on the lessons learned in the aftermath of January 6, intelligence officers globally began complaining and affirming the record of how unprepared and blind they, ahead of threats to the public; how unequipped to disarm or lead the threat into submission.

These nations' legislatures, fearing rapid duplication of the pre-planned horrors, demanded a glimpse of the planning phases. Modernized nations pushed forth from "war on terror", into a phase for "disruption of terror". Of course; unless disrupted, horrors erupt.

The legislators, each of them conditioned by childhoods wherein buildings crumbled and train stations exploded, where cars barreled into crowds, and wherein select social media messaging could spur a protest into deadly riot, siezed their means and demanded thorough comprehension of the cyber-landscape; the federated enemy's real stronghold.

Browsers were a losing field, being so numerous and niche, and so the legislatures closed in on the internet service providers (ISP), whose close franchised relationships to one another and prior compliance to FCC and similar regulatory schemes seemed to display clearer inroads. New policies ensured that three months of each users' online sessions should be recorded for examination, that specific online actions could send users through additional channels for presumptive risk appraisal, and that - crucially for the bid to earn the sordid public's reluctant shrug, a user could quickly sample an immediate reading of their logged records.

Dialogue.

1. Which agencies are quick to abuse this new mechanism?
2. Describe properly gainful businesses that experience harm from the profiling.
3. Does this lead to additional policies such as "license to publish"?
4. Play through the ensuing discussions from the angle of "freedom of speech" / "ban hate speech".

• [ ] combine uscode releases into single git codebase

On @c4lliope's channel, (and c4lliope online, many places), see some upcoming and prior recording sessions:

recorded in michigan, amerinordo.

• [code] record hopping! (plumber deploys nushell; pipes shudder).
• 07-31 04:00 [code] Spelunc! Legal Rules-as-Code engine from Axiom.
• 07-29 23:30 [code] add legal sources!
• 07-25 [code] query congress.gov!
• 07-24 pick up the pace! deploying operand.
• 07-24 problems around the globe.
• 07-23 coding session! page index.
• 07-22 a bordering-on-magic show!
• 07-21 superuser (Zero Day!)

Rainy days remind me of the sound and lakes around the city called by the name of Seattle, the sloping roads draining a simple, measurable flow of the sky into the sea.

These days remind me of Tokyo, and I hope they could possibly drag on, and on, seemingly endless days of bored focus, charging into the sudden moment wherein a necessary errand can no longer be delayed - the dash to a normally immemorable shop requiring a full dress of slicked armor, umbrellas held high and shaken before binned at the door.

The mood on these days helps me feel human, more real than the clinical square boxes of our era. As my fingers pad around sqares inside a metal square beneath a shining square, on a squared-off desk on four square legs, and each sharp edge of our language reinforcing this as righteous, that 90 is the only permissible degree wherein sanity can be found.

Odd, no?

The 90, this four-square slice of 360, is an homage to the philosophers of greece from aeons long dust, philosophers who cared deeply for ideas and communication, and care nothing for the home you designed as a perpetually diminishing blend of a parthenon or athena's temple.

In Tokyo, a holiday means seeing a shrine, serious labor of legs and laces for such a young age. Those shrines held their place for hundreds of years, through the bouncing pressure of many millions of pilgrims plodding through. Many thousands of rainy days, when the typhoons pounded for a month as reliably and unbreakingly as the sea onshore.

I can embrace my memories, on rainy days, the moments of reckless negligence on a ship I scarcely could handle, moments after escaping harbor in the Chesapeake, no plan or reading of the weather to prepare me for the sudden onrush, of sky into sea, and there being me in the middle, hugging the sail that asked to rip through me, that spent the dark hours curled beside me in bed, both of us dripping the fresh drops of dense cloud.

Commotion is in my core, is the lesson I embodied more than any. Expedition is the calling I ache to respond to, if our chosen social leaders could call us any place aside from the office desk or into the path of munitions.

A desk causes me anger, causes me pain and the aches of age. Send me to a dojo to shake free of those holds. Send me on a long road to find connections to a place, to a people, to a land.

How do you suppose we should manage our current crises? The burning Boreal ash in the air, some including some small pieces now drying in my hair, is supposed to be remedied from your desk? The complex boundary zones of shoreline and basin and levee, or the insensible flush of landslide, are supposed to be mapped in real time, and barely addressed in real space?

I took a class for dance yesterday, because the burden of days at desk had me sinking. I long again, now, for motion - for a chance to honor the body I occupy, after 34 years of memory gradually has persuaded me that my body is most excellent in the frigid cold early-morning damp, or the rush of a close-held grip on a cliffside, as I ease through a hazardous path for a purposeful aim.

Architecture has been held up as an honorable hobby, or career. The honor has all fallen on the arches; the tectonics simply a challenge of quarrying, a plunge of hand, or spade, or blade, or drill into soil. A pull and push of perilous loads, craning higher as all of us chase closer to the sky.

As some go up, many sink. Those radios that keep us on air require minerals to read the frequencies we seek; the lines of communication demanding a fractured labyrinth, chiseled by bloody hands, unmapped to the the public eye, whose air is recycled again, and again by the mouths and lungs of those who go their to take up their place, their spades and drills, the managed combustions and explosions an unpurgeable echo in their memories, though unheard and no alarm to those whose pay calls them forth.

As I begin re-launching operand.online, many problems and old pains reappear. I had been ignoring my failed domain for months, because I've been engrossed in occupying a new nomadic residence, my camper has gone from Grand Rapids to Baltimore to Los Angeles, to Baltimore to Chicago to Grand Rapids, this year alone.

I've been finding conferences to go to, although they've been of less use than I assumed. The long hours on the road and hurried composure that I normally embody mean that I'm late to show up and a mess when I do. I'm learning that there are other more sensible methods of spending my days, and this domain is one superb manner of being in many places at once.

Beside my human concerns, I'm spending more energy absorbing the news of global chaos, and I'm sad as each day begins that my sleep has likely carried me through someone elses' tragedy. I'm aligning my business to ending these ongoing and expanding horrors.

Whereas before I used my essays to explore my psychology and relationships, now I am beginning to see how much I had been lacking any purpose. I had a chance to briefly meet and collaborate with 404 Media, I had chances to learn from peers at OpenGovHub, and I am coming to see how my passions are indeed aligned, both to the quirks of my unique education and to the compelling demands of the now.

Rearrange.

I begin by erasing a couple unnecessary pieces of my app's homepage, the summary and the sidebar, and collapse the codebase index; these seem to only occupy space with no purpose.

As I record my source changes I realize that this new deployment machine needs a copy, because I am unable to push my code.

• I double-check that I can access the machine using ssh, to the public ip address.
• I double-check that I opened the router port (UDP 60001) needed by Mosh.
• I've already loaded in some code under share/gram/: nue, nux, mech, and pool. These are my baseline programs that I can use to quickly push programs into place.
• mkcd share/gram/op; c init on the domain machine.
• on local, cd share/gram/op; c r set-url share nixos@<public-ip>:share/gram/op; c k
• check that gram:op has a basic public copy.

Preliminaries: loading baseline code.

A number of days ago I breezed through some preliminaries on this machine.

I've already loaded in some code under share/gram/: nue, nux, mech, and pool. These are my baseline programs that I can use to quickly push programs into place.

Here's how this happened; these are copied from a raspberry pi's ~/.bash_history and ~/.config/nushell/history.txt, as I ran through a similar process.

These logs are redundant because many of the commands failed, and needed to be rephrased or re-run after changing a config. They are here so a full and more concise deployment guide can be made someday, by slicing through to the core commands.

          git diff
sudo rm -r /etc/nixos
sudo ln -s /home/nixos/.nux /etc/nixos
nix flake update
hx ~/.config/nixpkgs/config.nix
mkdir ~/.config/nix/
mkdir -p ~/.config/nix/
hx ~/.config/nix/nix.conf
nix flake update
hx flake.nix 
nix flake update
sudo nixos-rebuild --flake /etc/nixos/#pebble
sudo nixos-rebuild --flake /etc/nixos/#pebble build
ls -alD /etc/nixos
cd /etc/nixos
sudo nixos-rebuild --flake .#pebble build
hx flake.nix
hx cell/pebble/index.nix 
sudo nixos-rebuild --flake .#pebble build
ls /dev/disk/by-uuid/
hx cell/pebble/index.nix 
sudo nixos-rebuild --flake .#pebble build
hx cell/pebble/index.nix 
sudo nixos-rebuild --flake .#pebble build
sudo nixos-rebuild --flake .#pebble switch
hx .
sudo nixos-rebuild --flake .#pebble switch
hx .
sudo nixos-rebuild --flake .#pebble switch
sudo passwd
passwd
sudo nixos-rebuild --flake .#pebble switch
reboot
nix-shell -p elixir --run iex
hop home
ls .nue
nix-shell -p elixir --run iex
nix-shell -p elixir --run iex
ls -a
date
wget https://share.operand.online/gram/nux/?download=tar_gz
nsh wget wget https://share.operand.online/gram/nux/?download=tar_gz
nix-shell -p wget --run wget https://share.operand.online/gram/nux/?download=tar_gz
nix-shell -p wget --run 'wget https://share.operand.online/gram/nux/?download=tar_gz'
nix-shell -p gnutar --run 'tar -xzvf ./index.html?download=tar_gz'
mv nux .nux
nix-shell -p wget --run 'wget https://share.operand.online/gram/nux/?download=tar_gz -O nux.tar.gz'
mv index.html\?download\=tar_gz nux.tar.gz
nix-shell -p wget --run 'wget https://share.operand.online/gram/nue/?download=tar_gz -O nue.tar.gz'
nix-shell -p gnutar --run 'tar -xzvf ./nue.tar.gz'
nix-shell -p wget --run 'wget https://share.operand.online/gram/mech/?download=tar_gz -O mech.tar.gz'; nix-shell -p gnutar --run 'tar -xzvf ./mech.tar.gz'
ls mech
mv nue .nue
ls nue
sudo chown nixos nue
ls nue
sudo chown -R nixos nue
ls -al
ls .nux
ls .nue
ls mech
nix-shell -p wget --run 'wget https://share.operand.online/gram/mech/?download=tar_gz -O mech.tar.gz'; nix-shell -p gnutar --run 'tar -xzvf ./mech.tar.gz'; mv mech .mech
nix-shell -p wget --run 'wget https://share.operand.online/gram/mech/?download=tar_gz -O mech.tar.gz'; nix-shell -p gnutar --run 'tar -xzvf ./mech.tar.gz'; mv mech .mech
rm mech.tar.gz mech; nix-shell -p wget --run 'wget https://share.operand.online/gram/mech/?download=tar_gz -O mech.tar.gz'; nix-shell -p gnutar --run 'tar -xzvf ./mech.tar.gz'; mv mech .mech
rm mech.tar.gz mech; nix-shell -p wget --run 'wget https://share.operand.online/gram/mech/?download=tar_gz -O mech.tar.gz'; nix-shell -p gnutar --run 'tar -xzvf ./mech.tar.gz'; mv mech .mech
rm mech.tar.gz mech; nix-shell -p wget --run 'wget https://share.operand.online/gram/mech/?download=zip -O mech.zip'
hx mech.zip 
ls -al mech.zip 
rm mech.zip
sudo ls /etc/nixos/
ls /etc
ls /etc/nixos/
nixos-generate-config
sudo nixos-generate-config
sudo cp /etc/nixos/hardware-configuration.nix ~/.nux/cell/pebble/machine.nix
cd .nux
git status
nix-shell -p git
nix-shell -p git helix

          

          rm -r ~/.config/nushell; ln -s ~/.nue ~/.config/nushell
ls ~/.config/nushell/
session hop
hx ~/.nue/page.nu
hx ~/.nue/media.nu
atuin init nushell
mkdir ~/.local/share/atuin
atuin init nu | save ~/.local/share/atuin/init.nu
$env.NU_VERSION
hx ~/.local/share/atuin/init.nu
zoxide init nu | save ~/.zoxide.nu
zoxide init nushell | save ~/.zoxide.nu
starship init nu
starship init nu | save ~/.cache/starship/init.nu
nsh elixir iex
sudo nix-channel --add https://nixos.org/channels/nixpkgs-stable nixos
sudo nix-channel --update
ip a
hx /etc/nixos
hostname
x -r
hx /etc/nixos
x -r
x
hx /etc/nixos
h -r
x
rg hypr cell
ag hypr cell
grep hypr
x -r
pwd
ls
c s
clear
ls
nsh elixir iex
sudo nix-channel --add https://nixos.org/channels/nixpkgs-stable nixos
sudo nix-channel --update
ip a
date
date now
zellij action dump-session
zellij action dump-layout
zellij action dump-layout | save ~/.config/zellij/session/home.kdl
zellij attach -c home
hop home
mkdir ~/.config/zellij/session
zellij action dump-layout | save ~/.config/zellij/session/home.kdl
zellij attach -c home
hop home
date now
sudo nix-channel --update
cycle { date now }
sudo nix-channel --update
sudo ntpdate
h
date now
x
date now
sudo ntpdate time.nist.gov
sudo systemctl stop ntpdate
h -r
http get https://python.org
ping python.org
ping nixos.org
ip a
x
iex
which elixir
h
iex
mkcd relay
cd ..
rmdir relay
mix new relay
cd relay
hx mix.exs
iex -S mix
mix deps.get
iex -S mix
mix compile
http get https://share.operand.online/gram/op/flake.nix
http get https://share.operand.online/gram/op/flake.nix | save flake.nix
hx flake.nix
nd mix compile
hx flake.nix
mix compile
nd mix compile
hx flake.nix
nd mix compile
hx flake.nix
nd mix compile
hx flake.nix
nd mix compile
iex -S mix
hx ~/.bash_history ~/.config/nushell/history.txt
x
ip a
x

          

Upgrading Node Packages

NodeJS is infamous for "dependency hell", a condition where a full day or occasionally a week can be expended in researching how packages have been upgraded, and how each package depends on others.

For this essay, i'm hoping to use the collapsible feature of DaisyUI, and I saw that the package had an upgrade. As I tried to upgrade that package, I began seeing myself pulled into a dependency hell loop. Here are the immediate symptoms;

error Invariant Violation: expected workspace package to exist for "eslint"
error Invariant Violation: expected workspace package to exist for "ts-jest"
error Invariant Violation: expected workspace package to exist for "@babel/plugin-bugfix-firefox-class-in-computed-class-key"
error Invariant Violation: expected workspace package to exist for "@babel/plugin-bugfix-safari-class-field-initializer-scope"
error Invariant Violation: expected workspace package to exist for "@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression"
error Invariant Violation: expected workspace package to exist for "@eslint/plugin-kit"
error Invariant Violation: expected workspace package to exist for "minimatch"
error Invariant Violation: expected workspace package to exist for "glob"    at invariant (/nix/store/8j2jw3v2vzjl9z4xkw2m9xsqxaxzdw89-yarn-1.22.22/libexec/yarn/lib/cli.js:2318:15)
error Invariant Violation: expected workspace package to exist for "@babel/cli"
error Invariant Violation: expected workspace package to exist for "@eslint/config-array"

Each one of these lines indicates one-or-more runs of yarn install, after changing the dependency index inside gram:op/assets/package.json; each of these errors also required me to head to npm, and search for the missing package so I could include the proper recent version number. This was a failing method, and new problems kept appearing.

I realized a more dominant error was higher in the logs, preceding these "invariant violations": the "unmet peer dependency".

warning " > @babel/plugin-bugfix-firefox-class-in-computed-class-key@7.28.5" has unmet peer dependency "@babel/core@^7.0.0".
warning " > @babel/plugin-bugfix-safari-class-field-initializer-scope@7.27.1" has unmet peer dependency "@babel/core@^7.0.0".
warning " > @babel/preset-env@7.29.5" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-bugfix-firefox-class-in-computed-class-key@7.28.5" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > @babel/plugin-bugfix-safari-class-field-initializer-scope@7.27.1" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > @babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression@7.27.1" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > @babel/plugin-bugfix-safari-rest-destructuring-rhs-array@7.29.3" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > @babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@7.27.1" has unmet peer dependency "@babel/core@^7.13.0".
warning "@babel/preset-env > @babel/plugin-bugfix-v8-static-class-fields-redefine-readonly@7.28.6" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > babel-plugin-polyfill-corejs2@0.4.17" has unmet peer dependency "@babel/core@^7.4.0 || ^8.0.0-0 <8.0.0".
warning "@babel/preset-env > babel-plugin-polyfill-corejs2@0.4.17" has unmet peer dependency "@babel/core@^7.4.0 || ^8.0.0-0 <8.0.0".warning "@babel/preset-env > babel-plugin-polyfill-regenerator@0.6.8" has unmet peer dependency "@babel/core@^7.4.0 || ^8.0.0-0 <8.0.0".
warning "@babel/preset-env > babel-plugin-polyfill-corejs2 > @babel/helper-define-polyfill-provider@0.6.8" has unmet peer dependency "@babel/core@^7.4.0 || ^8.0.0-0 <8.0.0".
warning "@babel/preset-env > babel-plugin-polyfill-corejs2 > @babel/helper-define-polyfill-provider@0.6.8" has unmet peer dependency "@babel/core@^7.4.0 || ^8.0.0-0 <8.0.0".warning " > postcss-import@16.1.1" has unmet peer dependency "postcss@^8.0.0".
warning "@babel/preset-env > babel-plugin-polyfill-corejs3@0.14.2" has unmet peer dependency "@babel/core@^7.4.0 || ^8.0.0-0 <8.0.0".
warning "@babel/preset-env > babel-plugin-polyfill-corejs3@0.14.2" has unmet peer dependency "@babel/core@^7.4.0 || ^8.0.0-0 <8.0.0".warning "@babel/preset-env > @babel/plugin-transform-async-to-generator > @babel/helper-remap-async-to-generator@7.27.1" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > babel-plugin-polyfill-corejs3 > @babel/helper-define-polyfill-provider@0.6.8" has unmet peer dependency "@babel/core@^7.4.0 || ^8.0.0-0 <8.0.0".
warning "@babel/preset-env > babel-plugin-polyfill-regenerator@0.6.8" has unmet peer dependency "@babel/core@^7.4.0 || ^8.0.0-0 <8.0.0".
warning "@babel/preset-env > @babel/plugin-proposal-private-property-in-object@7.21.0-placeholder-for-preset-env.2" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-syntax-import-assertions@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-syntax-import-attributes@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-syntax-unicode-sets-regex@7.18.6" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > @babel/plugin-syntax-unicode-sets-regex > @babel/helper-create-regexp-features-plugin@7.28.5" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > @babel/plugin-syntax-unicode-sets-regex > @babel/helper-create-regexp-features-plugin@7.28.5" has unmet peer dependency "@babel/core@^7.0.0".warning "@babel/preset-env > @babel/plugin-transform-class-static-block > @babel/helper-create-class-features-plugin@7.29.3" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > @babel/plugin-transform-arrow-functions@7.27.1" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-async-generator-functions@7.29.0" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-async-generator-functions > @babel/helper-remap-async-to-generator@7.27.1" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > @babel/plugin-transform-async-to-generator@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-async-to-generator > @babel/helper-remap-async-to-generator@7.27.1" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > @babel/plugin-transform-block-scoped-functions@7.27.1" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-block-scoping@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-classes@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-classes > @babel/helper-replace-supers@7.28.6" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > @babel/plugin-transform-class-properties@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-class-properties > @babel/helper-create-class-features-plugin@7.29.3" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > @babel/plugin-transform-class-static-block@7.28.6" has unmet peer dependency "@babel/core@^7.12.0".
warning "@babel/preset-env > @babel/plugin-transform-class-static-block > @babel/helper-create-class-features-plugin@7.29.3" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > @babel/plugin-transform-computed-properties@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-destructuring@7.28.5" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-dotall-regex@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-duplicate-keys@7.27.1" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-duplicate-named-capturing-groups-regex@7.29.0" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > @babel/plugin-transform-dynamic-import@7.27.1" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-explicit-resource-management@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-exponentiation-operator@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-export-namespace-from@7.27.1" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-for-of@7.27.1" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-function-name@7.27.1" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-json-strings@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-literals@7.27.1" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-logical-assignment-operators@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-member-expression-literals@7.27.1" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-modules-amd@7.27.1" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-modules-amd > @babel/helper-module-transforms@7.28.6" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > @babel/plugin-transform-modules-commonjs@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-modules-commonjs > @babel/helper-module-transforms@7.28.6" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > @babel/plugin-transform-modules-systemjs@7.29.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-modules-umd@7.27.1" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-modules-umd > @babel/helper-module-transforms@7.28.6" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > @babel/plugin-transform-named-capturing-groups-regex@7.29.0" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > @babel/plugin-transform-new-target@7.27.1" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-nullish-coalescing-operator@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-numeric-separator@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-object-rest-spread@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-object-super@7.27.1" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-optional-catch-binding@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-optional-chaining@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-parameters@7.27.7" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-private-methods@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-private-methods > @babel/helper-create-class-features-plugin@7.29.3" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > @babel/plugin-transform-private-property-in-object@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-property-literals@7.27.1" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-regenerator@7.29.0" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-regexp-modifiers@7.28.6" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > @babel/plugin-transform-reserved-words@7.27.1" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-shorthand-properties@7.27.1" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-spread@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-sticky-regex@7.27.1" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-template-literals@7.27.1" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-typeof-symbol@7.27.1" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-unicode-escapes@7.27.1" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-unicode-property-regex@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-unicode-regex@7.27.1" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-env > @babel/plugin-transform-unicode-regex > @babel/helper-create-regexp-features-plugin@7.28.5" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > @babel/plugin-transform-unicode-sets-regex@7.28.6" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-env > @babel/preset-modules@0.1.6-no-external-plugins" has unmet peer dependency "@babel/core@^7.0.0-0 || ^8.0.0-0 <8.0.0".
warning " > @babel/preset-typescript@7.28.5" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-typescript > @babel/plugin-syntax-jsx@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-typescript > @babel/plugin-transform-modules-commonjs@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-typescript > @babel/plugin-transform-modules-commonjs > @babel/helper-module-transforms@7.28.6" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-typescript > @babel/plugin-transform-typescript@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-typescript > @babel/plugin-transform-typescript > @babel/helper-create-class-features-plugin@7.29.3" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-typescript > @babel/plugin-transform-typescript > @babel/helper-create-class-features-plugin > @babel/helper-replace-supers@7.28.6" has unmet peer dependency "@babel/core@^7.0.0".
warning "@babel/preset-typescript > @babel/plugin-transform-typescript > @babel/plugin-syntax-typescript@7.28.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning: Git tree '/home/calliope/share/gram/op' is dirty
warning " > postcss-import@16.1.1" has unmet peer dependency "postcss@^8.0.0".
warning " > ts-jest@29.4.9" has unmet peer dependency "jest@^29.0.0 || ^30.0.0".
warning " > ts-jest@29.4.9" has unmet peer dependency "typescript@>=4.3 <7".
warning " > ts-jest@29.4.9" has unmet peer dependency "typescript@>=4.3 <7".warning " > vite-plugin-babel@1.6.0" has unmet peer dependency "@babel/core@^7.0.0".
warning " > vite-plugin-babel@1.6.0" has unmet peer dependency "@babel/core@^7.0.0".

If you take these ~100 errors, place them in a helix buffer, place a cursor on each line, skim to the third quote, and erase the preceding phrase, you have ~100 lines of only the peer dependencies that are being called for. If you then select the full buffer and run :pipe sort , you can see the minimal requirements:

"@babel/core@^7.0.0".
"@babel/core@^7.0.0-0".
"@babel/core@^7.0.0-0 || ^8.0.0-0 <8.0.0".
"@babel/core@^7.12.0".
"@babel/core@^7.13.0".
"@babel/core@^7.4.0 || ^8.0.0-0 <8.0.0".
"jest@^29.0.0 || ^30.0.0".
"postcss@^8.0.0".
"typescript@>=4.3 <7".

try {rm -r deps assets/node_modules}
nd mix deps.get
nd yarn install --cwd assets
nd mix assets.build

This really did nothing for me; after going through the process I had remaining invariant violations, and my package.json was expanding beyond means.

Before:

{
  "private": true,
  "workspaces": [
    "../deps/*"
  ],
  "dependencies": {
    "daisyui": "^5.5",
    "phoenix": "workspace:*",
    "phoenix_html": "workspace:*",
    "phoenix_live_view": "workspace:*",
    "postcss-import": "^16.1",
    "tailwindcss": "^4.3",
    "theme-change": "^2.5",
    "topbar": "^3.0",
    "vite": "^8.0",
  }
}

an hour in:

{
  "private": true,
  "workspaces": [
    "../deps/*"
  ],
  "dependencies": {
    "@babel/core": "^7.0",
    "@babel/preset-env": "^7.29",
    "@eslint/config-array": "*",
    "@eslint/plugin-kit": "*",
    "@jest/reporters": "*",
    "@tailwindcss/vite": "^4.3",
    "daisyui": "^5.5",
    "eslint": "^10.3",
    "glob": "^13.0",
    "json5": "*",
    "minimatch": "^10.2",
    "phoenix": "workspace:*",
    "phoenix_html": "workspace:*",
    "phoenix_live_view": "workspace:*",
    "postcss": "^8",
    "postcss-import": "^16.1",
    "tailwindcss": "^4.3",
    "theme-change": "^2.5",
    "topbar": "^3.0",
    "typescript": "^6.0",
    "vite": "^8.0"
  }
}

Re-sparking

I rigged up most of my JS-compiler procedure using phoenix_vite, and this package includes an Igniter module to spark the necessary code and configs. I decide to erase the package.json index and begin again.

➜ rm package.json
➜ rm assets/yarn.lock
➜ nd mix igniter.install phoenix_vite

warning: Git tree '/home/calliope/share/gram/op' is dirty
checking for igniter in project ✔
Updating project's igniter dependency ✔
compiling igniter ✔
compile ✔
Dependency phoenix_vite is already in mix.exs. Should we replace it?

Desired: `{:phoenix_vite, "~> 0.4"}`
Found: `{:phoenix_vite, "~> 0.4.3"}`
 [Y/n] n
`phoenix_vite.install` x

Issues:

* assets/vite.config.mjs: File already exists
* Cannot move priv/static/corp/dlcp.cert.pdf to assets/public/corp/dlcp.cert.pdf, as assets/public/corp/dlcp.cert.pdf already exists.
* Cannot move priv/static/corp/2024-04-21.dlcp.png to assets/public/corp/2024-04-21.dlcp.png, as assets/public/corp/2024-04-21.dlcp.png already exists.
* Cannot move priv/static/corp/dlcp.CorpForProfitDomesticInitialFiling.pdf to assets/public/corp/dlcp.CorpForProfitDomesticInitialFiling.pdf, as assets/public/corp/dlcp.CorpForProfitDomesticInitialFiling.pdf already exists.
* Cannot move priv/static/cache_manifest.json to assets/public/cache_manifest.json, as assets/public/cache_manifest.json already exists.
* Cannot move priv/static/corp/CP575Notice_1704499942839.pdf to assets/public/corp/CP575Notice_1704499942839.pdf, as assets/public/corp/CP575Notice_1704499942839.pdf already exists.
* Cannot move priv/static/images/favicon.ico to assets/public/images/favicon.ico, as assets/public/images/favicon.ico already exists.
* Cannot move priv/static/robots.txt to assets/public/robots.txt, as assets/public/robots.txt already exists.
* Cannot move priv/static/images/logo.svg to assets/public/images/logo.svg, as assets/public/images/logo.svg already exists.
* Cannot move priv/static/fonts/fa-solid-900.ttf to assets/public/fonts/fa-solid-900.ttf, as assets/public/fonts/fa-solid-900.ttf already exists.
* Cannot move priv/static/images/screen.png to assets/public/images/screen.png, as assets/public/images/screen.png already exists.

➜ try { rm -r assets/vite.config.mjs priv/static assets/package.json assets/yarn.lock }
➜ nd mix igniter.install phoenix_vite

These folders will be created:

/assets/public


These files will be removed:

* assets/vendor/daisyui-theme.js
* assets/vendor/daisyui.js
* assets/vendor/topbar.js


The following installer was found and executed: `phoenix_vite.install` - Warnings:

* Failed to remove dependency :esbuild from `mix.exs`.

  Please remove the old dependency manually.

* Failed to remove dependency :tailwind from `mix.exs`.

  Please remove the old dependency manually.



These tasks will be run after the above changes:

* deps.clean --unlock --unused esbuild
* deps.clean --unlock --unused tailwind
* assets.setup

Warning! Uncommitted git changes detected in the project.

You may want to save these changes and rerun this command.
This ensures that you can run `git reset` to undo the changes.

Output of `git status -s --porcelain`:

 D assets/package.json
 D assets/vite.config.mjs
 D assets/yarn.lock
 M config/dev.exs
 M config/prod.exs
 M config/runtime.exs
 M flake.lock
 M flake.nix
 M lib/op_web/live/chronicle/show.ex
 M lib/op_web/router.ex
 M lib/render.ex
 M mix.exs
 M mix.lock
 D priv/static/images/logo.svg


Proceed with changes?
 [Y/n] y
Resolving Hex dependencies...
Resolution completed in 0.274s
Unchanged:
  bandit 1.11.0
  cachex 4.1.1
  call 0.0.2
  db_connection 2.10.1
  decimal 3.1.0
  dns_cluster 0.2.0
  earmark_parser 1.4.44
  eternal 1.2.2
  ex_ast 0.11.2
  ex_doc 0.40.2
  ex_hash_ring 6.0.4
  ex_heroicons 3.1.0
  expo 1.1.1
  file_system 1.1.1
  finch 0.22.0
  floki 0.38.1
  gettext 0.26.2
  git_cli 0.3.0
  glob_ex 0.1.11
  hpax 1.0.3
  igniter 0.8.0
  jason 1.4.5
  jumper 1.0.2
  live_debugger 0.3.2
  lumis 0.5.0
  makeup 1.2.1
  makeup_elixir 1.0.1
  makeup_erlang 1.1.0
  mdex 0.12.2
  mime 2.0.7
  mint 1.8.0
  nimble_options 1.1.1
  nimble_parsec 1.4.2
  nimble_pool 1.1.0
  owl 0.13.0
  phoenix 1.8.7
  phoenix_html 4.3.0
  phoenix_html_helpers 1.0.1
  phoenix_live_dashboard 0.8.7
  phoenix_live_reload 1.6.2
  phoenix_live_view 1.1.30
  phoenix_pubsub 2.2.0
  phoenix_template 1.0.4
  phoenix_vite 0.4.3
  plug 1.19.1
  plug_crypto 2.1.1
  postgrex 0.22.2
  req 0.5.17
  rewrite 1.3.0
  rustler_precompiled 0.9.0
  sleeplocks 1.1.4
  sobelow 0.14.1
  sourceror 1.12.0
  spitfire 0.3.11
  telemetry 1.4.2
  telemetry_metrics 1.1.0
  telemetry_poller 1.3.0
  text_diff 0.1.0
  thousand_island 1.4.3
  tox 0.2.3
  unsafe 1.0.2
  websock 0.5.3
  websock_adapter 0.5.9
  yamerl 0.10.0
  yaml_elixir 2.12.1
  yaml_front_matter 1.0.0
All dependencies are up to date
** (File.Error) could not remove file "assets/vendor/daisyui-theme.js": no such file or directory
    (elixir 1.18.4) lib/file.ex:1222: File.rm!/1
    (elixir 1.18.4) lib/enum.ex:987: Enum."-each/2-lists^foreach/1-0-"/2
    (igniter 0.8.0) lib/igniter.ex:1253: Igniter.do_or_dry_run/2
    (igniter 0.8.0) lib/igniter/util/install.ex:211: Igniter.Util.Install.run_installers/5
    (mix 1.18.4) lib/mix/task.ex:495: anonymous fn/3 in Mix.Task.run_task/5
    (mix 1.18.4) lib/mix/cli.ex:107: Mix.CLI.run_task/2
    /nix/store/4nvnygngnha29ycn4lilh5iazc6hikff-elixir-1.18.4/bin/mix:2: (file)

So, an error appears after much helpful guidance. good enough. obey guidance.

I check mix.exs and see there is no dependency on esbuild or tailwindcss. odd. Maybe my dependencies are old.

➜ try { rm -r deps }; nd mix deps.update --all
➜ try { rm -r assets/vendor assets/vite.config.mjs priv/static assets/package.json assets/yarn.lock }; nd mix igniter.install phoenix_vite

This final error occurred again,

** (File.Error) could not remove file "assets/vendor/daisyui-theme.js": no such file or directory

so I added some quirky placeholder-insertions into my command:

[ assets/vendor assets/vite.config.mjs priv/static assets/package.json assets/yarn.lock ] | each {|n| try { rm -r $n } }
[ assets/vendor/daisyui-theme.js
] | each { mkdir ($in | path dirname); touch $in; }
nd mix igniter.install phoenix_vite

This also failed.

Why was I doing all this?

I remembered the reason - I planned to make those code snippets above accordion-able. This is not worth the hours of dependency upgrades. I was miserable and pulled in so deep.

One source of my misery here is that I am currently supposed to be in DC; these computer upgrades have had me pegged to the desk for 24 hours longer than planned, and there's more hardware issues to address before I go. I need to pull back out of this unplanned upgrade cycle.

Undue.

I run c co -b vite, making a branch for my changes. I run cap, my alias for git add -p.

Anything to do with these dependency upgrades goes into the branch.

I commit, then change back to main. Clean branch.

As I try to rebuild again and reclaim the normal experience, I see a line inside mix.exs for installing dependencies. yarn install --production.

I run:

nd yarn install --cwd assets --production

Success. Goddamn, one missing option this whole day.

Resume, deploy.

So, up and running locally. Yay? Seems like a small consolation. Now I need to log on to the lab and proxy the code to the domain.

Begin by seeing if I can push the changes, to [gram:op] and [gram:page].

I had some code to help on this, inside [gram:nue/gram.nu] (naming issue?) though that's basically useless now, obscured through many broken layers.

➜ c r set-url share nixos@76.112.8.171:unshare/page
➜ c k share
Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 24 threads
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 548 bytes | 548.00 KiB/s, done.
Total 3 (delta 1), reused 0 (delta 0), pack-reused 0 (from 0)
remote: error: refusing to update checked out branch: refs/heads/main
remote: error: By default, updating the current branch in a non-bare repository
remote: is denied, because it will make the index and work tree inconsistent
remote: with what you pushed, and will require 'git reset --hard' to match
remote: the work tree to HEAD.
remote:
remote: You can set the 'receive.denyCurrentBranch' configuration variable
remote: to 'ignore' or 'warn' in the remote repository to allow pushing into
remote: its current branch; however, this is not recommended unless you
remote: arranged to update its work tree to match what you pushed in some
remote: other way.
remote:
remote: To squelch this message and still keep the default behaviour, set
remote: 'receive.denyCurrentBranch' configuration variable to 'refuse'.
To 76.112.8.171:unshare/page
 ! [remote rejected] main -> main (branch is currently checked out)
error: failed to push some refs to '76.112.8.171:unshare/page'

“Static Site Generation” is the process of rendering html from a codebase, where you can describe the pages succinctly using humane markup languages like Markdown. They are more secure than Wordpress or other dynamically-rendered content management systems, because any changes require access to the source code - in our case, permissions in the GitHub org. This thread is a place to explore libraries and themes.

Before the library dump, I should include that we could do interactive elements through iframes, including the popular giscus and utterances. These need nearly no management and can be easily moderated through GitHub issues; basically making our GitHub codebase a public discussion running parallel to this forum.

So, choices.

Zola builds domains using Rust. Some of these themes are more for blogging, but I think you may like some.

• serene
• zola-theme-nivis
• tanuki
• terminus
• zap
• apollo
• boring
• pico
• papermod
• zola-theme-terminimal
• juice
• shadharon
• papaya
• zola-386

Hugo is an option using Go (of course) (Themes)

• Newsroom has a nice look

Lume is popping up in the Deno land. (Themes)

Docusaurus is based on simple and approachable ideas, designed for readable guides.

Gatsby is Javascript & React. Discouraged, because things seem up in the air during an acquisition.

NextJS is popular, had a full hype cycle.

Quartz is like a knowledge base similar to Obsidian, but public on the web. Could be plugged on top of a wiki or some such arrangement.

Quarto is more for data dashboards, probably beyond scope. Same for Framework.

Deploys

GitHub can handle all of the publishing for us using GitHub actions; this takes less than an hour to set up, and then you never have to think of it again. If you do have to make changes, it’s easy to find people who have used it or can pick it up quickly.

Deno Deploy is a new option that is based on similar principles, and is designed for Lume or Fresh (below). I helped a friend deploy here once, and the process had been easy as can be. Requires a credit card on file for antispam purposes; their free plan is the most generous I’ve seen. They also support dynamic-rendered apps, which brings us to…

Bonus: Dynamic Rendering

I’m already dumping links, so here are directions to look if we outgrow SSG.

• WikiJS is a fully managed wiki with a one-line deploy. I’d recommend upgrading our wiki to this soon. Has serious benefits for content management.
• DataStar
• HTMX
• Deno Fresh
• Astro

To begin, I use Brave.

Brave is more secure than normal; imagine Chrome with a bunch of the Google ripped out. This means any Google plugin runs in Brave.

Also, Firefox copied the plugins from Chrome, so you can probably find the same plugins in their web stores.

You may see plugins called "extensions"; that's a hairy issue.

Here are the plugins I use daily.

• uBlock Origin

  Blocks so many ads that some days I forget that most people still have ads. Also keeps me from clicking through on some clickbait.

• ToS;DR

  If you pin this to the menu bar, you'll see an A -> F letter grade for each domain. Click to read the main concerns before signing up, or flushing your cookies and running.

• Vimium (source)

  Move around and through pages using your keyboard alone. The mouse-to-keyboard loop is gradually breaking your mobility, so load this up and press ? on any page to see your new commands.

• Proton Pass (sign up!)

  You need a password manager that has encrypted sync, and your browser's built-in one is a cheap replica. As you use Proton Pass you'll be pleased to see the pop-ups for "passkeys", which enable one-click, no-pass logins.

• TabFS

  For the real hackers in the audience, because this plugin requires moving some config files around. When you're done though, you'll see a local file share that mirrors the open tabs in your browser. This plugin encouraged me to change from Firefox -> Brave, because independent plugin management is simpler in Chromium. Omar's one-page explanation is superb.

Hi, I am here to tell you about Argentina's Shamballa Permaculture Project. We are representatives of Armenia's ARK Armenia, happy to be here. Down in Australia we've connected up our Aboriginal Wetland Burning, Shoalwater Culture, Gawula, Greening Australia, How Aboriginals Made Australia, Kachana Land Restoration, One Acre Small Permaculture Project, Permaculture Research Institute, Purple Pear Farm, Rehydrating the Landscape, Regenerate Australia, and the Yarra Yarra Biodiversity Corridor. We're a busy crowd!

We are from Belize's Coral Reef Restoration. I represent Bolivia's Food Security. I, Borneo's How to Restore a Rainforest. We are from Brazil's Centro de Experimentos Forestasis, also Restoration Through Agroforestry. We come to you from Burkina Faso's The Forest of Lilengo, and the group Reforesting with Ancient African Farming Practices. Cameroon here: the Bafut Ecovillage.

Canada's delegation represents Bkejwanong Traditional Knowledge, Jardins d'Ambroisie, the Great Bear Rainforest, Miracle Farms, Taking Root, and Water for the Future. China's delegation is happy to speak for A Man Plants a Forest, Eco-Civilization, Greening China's Desert, Horqin Desert Reforestation, Karamay Ecological District, Kbuqi Desert Greening the Silk Road, Loess Plateau Watershed Restoration, Transforming Deserts to Cropland, World's Largest Man-made Forest, and Zhejiang Green Rural Revival Program.

From the Congo we are Bonobo Conservation, Participatory Mapping, and Virunga National Park. From Costa Rica, we are the Orange Peel Experiment, Punta Mona, and Vida Verde Water Retention. I am here to proudly speak for Cuba's Sustainable Agriculture Revolution, on its eighty-fifth birthday. We are from Denmark's Vitsohus Permakultur. I have been sent to you by Ecuador's Cloudforest Agroforestry. I from Egypt's Creating a Forest in the Desert. From England we represent Agroforestry Research Trust, the Eden Project, Knepp Estate Rewilding, Rewilding Britain, and River Restoration.

From Eritrea we are Manazares Mango Regeneration, from Ethiopia, Ethiopia Rising, the Miracle of Merere, Regreening Ethiopia's Highlands, Restoring Ecosystems, and the Watershed Movement. For France we happily represent Pur Projet Agroforestry. From Guatemala we are Reserva de Biosfera Maya and the Asociac'on de Comunidades Forestales. We speak for Reforesting Haiti. From Holland we represent the Land Life Company and Tiny Forest.

Honduras sends you the Roots of Migration. The Hopi Nation is here with Hopi Raincatchers. Iceland sends you Afforesting Iceland, and Regenerating Forests. From India we come to tell you of Agroforestry in Arau, Aravali Institute of Management, Barren Land into Luscious Forest, Cooperative Sustainable Agriculture, Creating a Forest in a Cold Desert, Crowd Foresting, the Farmer Scientist, Fishing Cat Conservancy, Food Sovereignty, Foundation for Ecological Security, Hand-Planting a 300-Acre Forest, Mangrove Restoration in the Sundarbans, Miracle Water Village, Miyawaki Afforestation Program, Natural Farming, Navdanya Biodiversity Farm, Planting 50 Million Trees in One Day, Planting 66 Million Trees in 12 Hours, Protecting Rice Diversity, Rejuvenated Lakes in Bangalore, Sadhana Forest, Sai Sanctuary, Seeds of Life, Sikkim the First Organic State, Water Fields, Water Harvesting, and River Restoration.

Indonesia greets you with its Biorock Coral Reef Restoration, Mangrove Action Project, Mangrove Restoration, and Manta Reef Restoration Project. Israel present its Growing Forests in the Desert, and Kibbutz. We are from Japan and bring news of Creating Forests to Reduce Tsunamis. I come from Jordan to tell you of Greening the Desert. We Kenyans are proud to represent East African Hydrologic Corridor, Green Belt Movement, Kaikipia Permaculture Center, Northern Rangelands Trust, and Rainwater Harvesting. Madagascar celebrates its Great Forest Restoration by the example of Project Moringa, and Using Trees to Save Lives.

Mexico presents Greening the Chihuahuan Desert, Intensive Silvopasture, Hidden Rivers, Reforestation and Water Protection Group, and Via Organica. Morocco brings you its organization Making the Desert Bloom. We come from Nepal to describe the Beyul Project and the Anthropocene Wilderness Group. New Zealand here: Hinewai Reserve, Mangarara Ecco Farm, and the Regenerators. As with all the other countries gathered here, tip of the iceberg really.

I come from Niger to tell you of Farmer Managed Natural Regeneration, and Re-greening in Niger. From Norway we speak of Polar Permaculture Solutions. The Oglala Lakota Nation sense a representative from the Oglala Lakota Culture Economic Revitalization. We are from Panama's Mamoni Valley Preserve. Peru wants to tell you of its Biocorredor Martin Sagrado. We from the Philippines have news of Forest Regernation, National Greening Program, and Saving a Fishery and Coral Reef.

We from Portugal celebrate the Fazenda Tomati Permaculture, Sown Biodiverse Pastures, Tamera Water Retention Landscape, and Wildlings. I am from Qatar's Sahara Forest Projet. From Russia with love: Pleistocene Park, Wet Carbon Storage, and Siberian Wildlife Support. I am from Rwanda's Forests of Hope. We Scots are here for Britain's Oldest Forest, Dendreggan Forest Restoration, Isle Martin Regeneration, On the Deep Wealth of This Nation, and Peat Bog Restoration. I speak to you for Senegal's Great Green Wall Initiative, also Rolling Back the Desert. From South Africa we speak about EcoPlanet Bamboo, Joe's Garden, Making the Desert Bloom, and Restoring the Baviaanskloof.

I am from the South Korean project Reforestation with 350+ Million Trees. I am from the Syrian project The Art of Regeneration, please help us. I come from Tajikistan to tell you of Reforesting Tajikistan. From Tanzania we speak for Reforesting Kokota Island and Reforesting Gombe's Surround. Tasmania here, we've got a great Giant Kelp Restoration Project, also Restoring Pine Plantations. I am from Thailand to tell you about Indigenous Knowledge and Forestry, Planting Mangroves, and Sahainan Permaculture Farm. Uganda sent me to speak of Permagardens and Uganda's New Forests.

We come from the United States as representatives of Accelerating Appalachia, American Prairie Reserve, Broken Ground Permaculture, Food Forest Farm, Holistically Managed Bison, Homegrown Revolution, Institute of Permaculture, Kiss the Ground, Klamath River Basin Restoration, Lake Erie Bill of Rights, the Land Institute, the Leopold Institute, Los Angeles Green Regeneration, Mirroring Nature's Management, Permaculture for the People, Planetary Healing, Planting Justice Farms, Regenerative Ranching, Restoring the Colorado River, Restoring the Redwoods, Restoring the Snake River, Rodale Institute, Saving the West, the Sierra Club, Singing Frogs Farm, Soil Health Institute, Stewards of the Wild Sea, Tabula Rasa Farms, Tending the Wild, Weaving Earth, Wild Idea Buffalo Company, and Wild Oyster Project.

I am from Zambia to tell you of the Betterworld Mine Regeneration. I am from Zimbabwe to speak for the Africa Centre for Holistic Management, and the Chikukwa Ecological Land Use Community Trust.

We are all here together to share what we are doing, to see each other, and to tell you our stories. We are already out there working hard, everywherere around this Earth. Healing the Earth is our sacred work, our duty to the seven generations. There are many more projects like ours already in existence, look us up on your YourLock account and see, maybe support us, maybe join us. You will find us out there already, now, and then you must also realize we are only about one percent of all the projects out there doing good things. And more still are waiting to be born. Come in, talk to us. Listen to our stories. See where you can help. Build your own project. You will love it as we do. There is no other world.

For me, August 2025 is going to remain the most spectacularly unplanned and chaotic mess of garbled memories, where each day carried so much nuance, and so many challenges, that there has been scarce occasion to pause and breathe, to reshape the experiences into more than the layered percussions of sun, moon, sea, sail, spoke, and signal.

I hope there is a chance to re-use that opening paragraph, in a closer examination of the days of August, only I need to begin by describing changes happening across this domain.

If you happen to be reading this, or perhaps if your RSS reader is doing a refresh, before 6pm on Thurs 09-04, you may only see a partial essay.

Background: Realizing a long-held dream.

I had good reason, cause, and chance to move my app deployment, from the basement where I lease a static IP address, to my local laptop, which I've had to leave up and running all night, in a hacker-space called the Baltimore Node.

I'm sure others have likely managed before me, a production online app running from a laptop. In my case I am especially pleased to do so, as a reinforcement of the aims described in the business' incorporación proposal.

When I composed the proposal in 2024 I was inexperienced in essays, and I need to apologize to the DC employees who had to read through that rubbish; moreso because as I began this company I was also in a phase of psychedelic experimentación.

If you dig through that essay, in a sense a legally binding one, you'll see the key theme is an idea I call "sublimación".

I realize now that my founding essay was simply a poor re-hashing of an idea explained much more clearly and simply in the Local-First Essay by Ink & Switch. They open by saying:

Cloud apps like Google Docs and Trello are popular because they enable real-time collaboration with colleagues, and they make it easy for us to access our work from all of our devices. However, by centralizing data storage on servers, cloud apps also take away ownership and agency from users. If a service shuts down, the software stops functioning, and data created with that software is lost.

It has been said before in the "local-first space" that numerous people are reaching the same conclusion from different initial conditions. The realización that our building processes are flawed, doomed to someday fail, is a process that can occur in a dispersed manner, like the many [origins of infintessimal calculus], or the rich explosion of humanist philosophies during the Axial Age

However the conclusion is reached, here we are.

Each of hundreds of programmers and small businesses are choosing a small niche in the local-first space. A full index is a good place to begin for end-users who are sick of usual app-store norms, and LoFi.so has many resources to choose from, including the Local-First Discord. Need to read more? See Local-First News.

The area I chose as a primary concern is unusual for the space, which is likely why I had been such a late-comer, missing the forest for the trees.

I chose to focus on web-app deployments.

2025 Aim: Reliable Deploys

Of course, 'web-app' can be seen as an antithesis to 'local-first'. If you agree, maybe I can change your mind.

Yesterday I came across an app I'd like to build into the mix, called Shiori. The purpose is to aggregate and label bookmarks, and enable an offline-reader mode for easy mobile access. There is no cloud-based company managing the program, and the features drop it categorically into the local-first space.

Shiori remains a web-app, and is capable enough for many users to access, although the primary audience is for a single-user per deployment. To run Shiori, users are encouraged to launch a web domain themselves.

Many apps are being produced in this manner because of the rising popularity of home-labbing, perhaps known to some as self-hosting. Besides, the web has made up some really amazing norms for apps that are dynamic and accessible, and is much more pleasing to build for than most "native" OS apps.

To launch your app's domain, the normal approach is to lease a machine from a cloud company. In this case, for such a simple app, the easiest option may be PikaPods. More experienced coders are familiar - and correspondingly sick of - flexible options like Linode and DigitalOcean, which probably are happy to lend our login credentials to the nearest NSA field office at the mere whisper of enforcement.

So, until now every domain manager had two choices:

• add to Amazon AWS or Akamai's global reach, by signing on to use their machines (usually repackaged by a cloud middle-manager)

• order a business internet plan, and consent to days-on-end of random phone calls with your ISP, to order a static IP address rigged up.

I'm partial to the second option, because reaching local-first dominance has to both amplify the share of local apps and programs, and crucially, reduce our dependence on cloud data centers.

I'd like to see a report each billing cycle, describing how much water my apps drank while they were being cooled by Google's electron-warehouse plumbing.

The deplorable shape of our industry is plain to see when passing through Ashburn, VA - a close suburb for me to reach, where there is no business, no one in sight, and only a bland shopping mall for amusement.

These are human prices of our industry that need to be recognized and addressed.

March 2025: Baseline Lab

Although my company's purpose is to bring the web back to the home, a further complicación had been... my lack of a home.

I am nomadic, carrying my home around in a pickup truck or a sailboat each day, and so I'd like to accomplish as many of my aims as possible while being as locación-independent as possible.

For the static IP address, I called up my pals in Upper Marlboro, MD; there is a home there full of the most generous people I know. I arranged for a business internet line to their home, and placed a couple machines in their basement.

I'd been commuting from place to place, and would occasionally find a chance to go by and check on the machines, manage upgrades, plug and unplug cords. The biggest flub had been encrypting the boot drive; each reboot required hands on a physical keybard. Nonetheless, the process remained in place through much of August. Six months on a static IP address!

Then... let's discuss how August went.

(beginning) August 2025: Sailing Fiasco

The "friend's basement" playbook is, eh, more or less manageable when you live in close proximity, are capable of a deep bond of co-reliance, and are equal shareholders in the success of the program.

I'm unsure how I scored on any one of those marks, though the deployment held up until a small crisis landed on Aug 1, requiring me to immediately set sail.

A sailboat is an ideal place to run cyber exercises. Because there is no escape from the physical isolación, the only connección you are likely to find to other humans has to be relayed to you through radio signals.

I dove deep into the Self-Hosted Podcast and Linux Unplugged, and called into many cancer research calls, where the group was far more eager (or enabled) for me to put the "comp" into "computational biology" than they were to put it into "compensation".

Of course, I had experiments to run. I launched Mumble. I launched Traccar. I launched n8n, and shoe-horned comment fields into the essay pages.

And I broke the lab. Again. And again.

To the dear residents of Larry Cat House,

I am so so sorry, sincerely and immensely so, for the endless calls on Signal where I explained complex passcodes and cable-plugging procedures, and the "quick sanity checks" where none was found.

I had to balance downtime for a core-business client app, my need for experimentación as a coping mechanism, for lonely breezeless days, and the superb annoyance I caused my pals back on land each day, immediately after promising it (probably?) wouldn't happen again.

I hung on like this until I got back to land, and spent one day fixing up the lab to get the blog running again before heading to HOPE. I promised myself I would do no experiments while I was in NYC, and besides I had no more energy to do so.

I was getting enough of a cyber-social buzz from the conference, and NYC is the deepest end of the social spectrum to drown in, after two weeks on a rolling bouncing bay.

After NYC, I headed back to the lab. I had ideas to manage, more grand plans. I had decided to separate the apps and the experiments, leave the production app running as I brought the bulk of the lab to Baltimore Node, where I could exhaust days on end running necessary experiments and building at high speed.

With all but the core production machine "baseboard" loaded into my truck, I locked the door to my friend's house behind me and began to pull out of their neighborhood.

Then I remembered. I should check if the app is online!

Not only no app, but no signal. No SSH.

I spun around, rang the doorbell, met the new roommate, and pulled the final cord out of Baseline Lab.

(end) August 2025: (re)Building Blocks

However much sleep I had lost in the preceding days, I was soon to lose more. My usually inattentive client quickly messaged me, saying "the app is down. Can we host it somewhere else?" and of course I said "yes, please".

I recommended fly.io because heck, I'm finally beginning to recognize my mission as a smidge on the idealistic side. If at all possible I can keep my ideals from holding up my pals' business, I suppose I should.

I burned a couple days building a proper Elixir/Phoenix Dockerfile, double-checking port and IP bindings between my config/*.exs files, and I finally had a reliable deployment that no longer breaks the memory limits.

On my breaks, I honed my process for launching NixOS on a Raspberry Pi, and soon headed back to Larry Cat House to plug one in; then a second.

The first pi I launched is called pebble, and for around a week this had been running the blog. On a couple occasions, I checked in, and thought I saw that the pi had crashed; then, a few hours or the next day, the app would be online again.

Clearly, the app is seeing more than zero traffic, and the pi is unable to keep up. No problem; the second pi I plugged in enabled me to experiment with Nebula. Nebula, in essence, enables me to spread the lab out to any number of geographically dispersed areas.

I placed some Nebula certificates on the two lab Pi's, assigned certs for my laptop (chesapeake), and with only a few days of config & network-address munging behind me, I can finally keep a reliable connection up between my chesapeake, in Baltimore, and pebble, in Upper Marlboro.

September 2025: Dispersed

As much as I like the reliable connection between here and there, the glory lies in the opposite direction: I can keep up a reliable connection from there to here.

Remember, there, where pebble is running, is the business line static IP address. pebble is only a low-grade Raspberry Pi 4B with 2GB RAM, purchased before I knew what to look for in a single-board computer. pebble kept choking and lagging when asked to compile markdown for a blogging engine.

When pebble can reach me here, on chesapeake, a full-blown x86 coding machine, the game fully changes. I kept the blog running at full capacity, by disabling my idle timer through the night, leaving the laptop plugged in to charge, on a residential wifi connection, reaching far higher speeds than the pi could manage.

I kept the blog running even as I ran Blender, and downloaded a bunch of YouTube videos explaining how to use Blender. I kept the blog running even as I compiled Blender from scratch, because that's how things go on NixOS, and there was no single hiccup in the response or lag from the app.

Finally, I logged on this morning and began playing around with the essay, and realized that as I saved my progress, the rendered page displayed the changes - on the public ://operand.online domain.

In essence, I signed up my pals for a static IP address, and made sure my domain's DNS records all point to that address. Then, I rigged up Nebula and Caddy to reference an address on a Nebula virtual-LAN; the magical, ephemeral, dispersed layer that replaces all networking headaches with certificate-management headaches.

As long as Nebula and Caddy agree on an IP address for the app machine, and Caddy and the app-machine agree on a port number for the app, and Caddy and the app agree on a domain name, then the app can be run on any machine, any place, regardless of network setup.

Of course, this experimentation process has required me to make serious changes to the business plan, so that much of what was described under BASE is now marked as 'broken' in red, and moved to NODE, where I can be more hands-on with my experiments, for much less risk.

A Moment, to Breathe

Some may say I am in a precarious posición, with my business. Why be nomadic, why go sailing, why be so un-employ-ed -able? There are few role models to choose from, when breaking so many norms, so I am lucky to rely on essays that stretch the seams on this world.

In her essays Ismatu examines the social scenarios of her tribe, and the consequences of being raised a child of two nacións.

I feel an immense bond with this composer, who I hope I shall be lucky enough to speak to, and collaborate alongside someday, by my own happenstance of being born in London, raised in Tokio, by midwestern parents.

Global children like us are fully incapable of considering the nonsense of a flat-earth hypotheses, because we have seen the curvature of the earth from the window seats of numerous long cross-oceanic flights.

Global children like us are less prone to ensnarement by a corporate mission statement,i spun around, rang the doorbell, met the new roommate, and pulled the final cord out of baseline lab. when we recognize that the mission ends where the state's boundary lies, less prone to being hooked by a viral ad campaign when we can examine a global virus campaigning through places once called home.

I'm sure that in the middle of the largest rapidly globalizing crisis our species has yet encountered, all one can hope to do is find an area where their skills can shine, press them into full gear, and share the consequences publicly as loud and openly as possible.

In my case, this consequence seems to be the simultaneous dissolución of the core mechanic underlying the business models of Amazon AWS, Google Cloud, and Microsoft Azure; the mechanism laid in place by ISP providers such as Comcast, AT&T, and Verizon, many years ago when the first phone lines began being repurposed for internet purposes.

The static IP has been the bane of my career, and in the end this windmill has been blown away by the deployment of a single Raspberry Pi, running a background Nebula process.

Going ahead: a Reproducible Base

Again, nearly nobody I know has a static IP address, and more and more people I know have apps they'd like to launch, and spare old machines lying around home with no purpose, and gradually depreciating innards. This is the problem of sublimación; the economic resource of silicon doomed to disuse, by lack of access to the demanded use cases.

By chance, Baseline Lab is my second failed static-IP experiment; the first one being in my parents' place of business in Michigan. Seeing as I have two static IPs to make use of, a business model comes to mind.

Soon, you'll be able to log in to ://operand.online, and for a choose-your-donación price, or pay-by-bandwidth for larger apps, you can send along your domain name to us, and I'll issue you a Nebula certificate. You can choose a static IP address from our list of nodes, to use as a relay for your web app. Any one should do, so choose based on geography.

You can assign your DNS records to our static IP, and our Caddy reverse proxy can begin handling your app's call-and-response through our Nebula mesh.

For memberships needing more nodes on a single mesh, perhaps you'd be open to on-demand cert allocación & revocación from a secure app, on a dedicated nebula mesh.

Of course, no one can build on such a core open-source library such as Nebula, unless you also run open-source. No problems here, this has been the case for Operand since day one.

I can see many docs pages ahead, for gradually-sharpened essay skills to go to use.

So, you're managing WordPress?
That's a popular thing to be doing!
How long have you had this running?

Oh, how rude of me to ask; probably much longer than you'd like to admit.

Here is how you can quickly back up a WordPress domain - focusing on the content of the pages, rather than the themes & style.

Throughout this guide we'll be making use of the WordPress REST API. Our code samples are prepared using Nushell.

Discover the API.

WordPress relies on a discovery mechanism to communicate each site's public API to one another.

In this example, we use wordpress.org - the same code applies, in theory, to any wordpress domain.

def "wp base" [domain: string] {
  http get --full $domain |
  get headers.response |
  where name == link |
  get value.0 |
  parse '<{link}>; rel="https://api.w.org/"' |
  get link.0
}

let base = wp base https://wordpress.org | tee { print }

Solid! We have a base URL.

Using the reference, we see that /wp/v2/posts is the path we need to use.

Depending on how your WordPress has been managed, other nice places to look are:

• /wp/v2/pages
• /wp/v2/tags
• /wp/v2/categories
• /wp/v2/comments
• /wp/v2/media
• /wp/v2/users

Again, see the reference for a more thorough appraisal.

To help us progress here, let's make a couple quick helper functions:

def "wp dump" [base: string, path: string, --form (-f): string = yml] {
  let node = [. ($base | url parse | get host) $"($path).($form)" ] |
    path join | path expand
  mkdir ($node | path dirname)
  try { http get ([ $base wp v2 $path ] | path join) | save -f $node }
}

Ready? Here goes.

let base = wp base 'https://wordpress.org'

timeit { [
 posts pages comments media users
 categories tags taxonomies types statuses
 settings themes search plugins
 block-types blocks block-renderer block-directory/search
] | each {|label| wp dump $base $label } }

# for a colleague's domain:
# 21sec 895ms 964µs 817ns

Of course, if you prefer a non-yml dump, pass in one of these extensions under -f:

➜ scope commands
    | where name starts-with "to "
    | insert extension { get name | str replace -r "^to " "" | $"*.($in)" }
    | select extension name
    | rename extension command

╭────┬────────────┬─────────────╮
│  # │ extension  │   command   │
├────┼────────────┼─────────────┤
│  0 │ *.csv      │ to csv      │
│  1 │ *.html     │ to html     │
│  2 │ *.json     │ to json     │
│  3 │ *.md       │ to md       │
│  4 │ *.msgpack  │ to msgpack  │
│  5 │ *.msgpackz │ to msgpackz │
│  6 │ *.nuon     │ to nuon     │
│  7 │ *.text     │ to text     │
│  8 │ *.toml     │ to toml     │
│  9 │ *.tsv      │ to tsv      │
│ 10 │ *.xml      │ to xml      │
│ 11 │ *.yaml     │ to yaml     │
│ 12 │ *.yml      │ to yml      │
╰────┴────────────┴─────────────╯

For completeness, here is a multi-format dump:

let base = wp base 'https://wordpress.org'

let labels = [
 posts pages comments media users
 categories tags taxonomies types statuses
 settings themes search plugins
 block-types blocks block-renderer block-directory/search
]

let forms = [ csv json yml ]

timeit { $labels | each {|l| $forms | each {|f|
  wp dump -f $f $base $l
} } }

Yeah! Such a nice backup already.

➜ tree wordpress.org
wordpress.org
├── block-directory
├── blocks.csv
├── blocks.json
├── blocks.yaml
├── blocks.yml
├── categories.json
├── categories.yaml
├── categories.yml
├── comments.json
├── comments.yaml
├── comments.yml
├── media.json
├── media.yaml
├── media.yml
├── pages.json
├── pages.yaml
├── pages.yml
├── posts.json
├── posts.yaml
├── posts.yml
├── search.json
├── search.yaml
├── search.yml
├── statuses.json
├── statuses.yaml
├── statuses.yml
├── tags.json
├── tags.yaml
├── tags.yml
├── taxonomies.json
├── taxonomies.yaml
├── taxonomies.yml
├── types.json
├── types.yaml
├── types.yml
├── users.json
├── users.yaml
└── users.yml

If you have a local copy of zip, yay!

zip -r wordpress.zip wordpress.org/*

Since I'm on NixOS I'm going to use a small prefix here:

nix-shell -p zip --run 'zip -r wordpress.zip wordpress.org/*'

Now, I'm going through this process to help a colleague, so this is a good place to email off the ZIP file, to see if she has any issues with how the records came back.

I'm eager to press ahead and look at a few newer CMS options for her! A couple ones I already have my eye on:

• Beacon
• Solid & MDX

Plus, the Awesome SelfHosted page has 40 more options for a CMS upgrade - of course, including WordPress.