Arroyo Systems are defined by a set of org-mode documents and a database caching layer. This repository is that database caching layer.
 
 
 
 
Go to file
Ryan Rix 320c4d7f4e another try at in_public_heading filtering woops 2024-04-19 10:34:53 -07:00
arroyo make the python wrapper have a command to parse a file agian 2024-04-01 19:44:06 -07:00
src another try at in_public_heading filtering woops 2024-04-19 10:34:53 -07:00
test deprecate the atom feed API, begin working on subheading export 2024-02-04 17:06:19 -08:00
.envrc switch to flake for direnv 2023-12-27 18:18:48 -08:00
.gitignore update gitignore 2023-10-26 00:49:35 -07:00
Cargo.lock customized html exporting 2023-12-11 00:07:25 -08:00
Cargo.toml customized html exporting 2023-12-11 00:07:25 -08:00
README.org [arroyo] point to README for git etc 2021-08-14 20:21:20 -07:00
arroyo-db.el update to new keywords 2023-12-17 16:06:19 -08:00
arroyo-emacs.el fix arroyo-generate-imports commands 2024-02-14 14:34:25 -08:00
arroyo-emacs.org fix arroyo-generate-imports commands 2024-02-14 14:34:25 -08:00
arroyo-feed-cache.org Arroyo is now reliant on the Arcology's commands, yikes! 2024-02-02 15:42:51 -08:00
arroyo-feed.yasnippet.org_archive [feeds] generate ggs fragments on key/value pairs 2021-08-29 18:54:33 -07:00
arroyo-feeds.el [feeds] add commands, use ugly call-block function 2021-11-19 22:11:33 -08:00
arroyo-home-manager.el Arroyo is now reliant on the Arcology's commands, yikes! 2024-02-02 15:42:51 -08:00
arroyo-home-manager.org Arroyo is now reliant on the Arcology's commands, yikes! 2024-02-02 15:42:51 -08:00
arroyo-native-parser.org another try at in_public_heading filtering woops 2024-04-19 10:34:53 -07:00
arroyo-nix.org update drawingbotv3 premium version in my personal package override 2024-01-12 12:13:54 -08:00
arroyo-nixos.el fix arroyo-generate-imports commands 2024-02-14 14:34:25 -08:00
arroyo-nixos.org fix arroyo-generate-imports commands 2024-02-14 14:34:25 -08:00
arroyo-system-cache.org update to new keywords 2023-12-17 16:06:19 -08:00
arroyo-utils.el pass files through to dep ordering command instead of s-exps 2021-12-10 14:35:44 -08:00
arroyo-utils.org arcology metadata 2022-09-12 14:02:54 -07:00
arroyo.org add greetz 2024-02-02 15:50:01 -08:00
default.nix took some nonsense to disable manylinux builds to get the nix build to work 2024-02-15 15:03:50 -08:00
flake.lock use my nixpkgs fork 2024-02-26 17:58:03 -08:00
flake.nix use my nixpkgs fork 2024-02-26 17:58:03 -08:00
pyproject.toml took some nonsense to disable manylinux builds to get the nix build to work 2024-02-15 15:03:50 -08:00
rustfmt.toml enable detangle comments 2023-10-24 10:35:58 -07:00
shell.nix cleanup before i rip a bunch of shit out 2023-11-10 14:18:24 -08:00

README.org

Arroyo Systems Management

What are Arroyo Systems?

Arroyo systems are the underlying design systems for the CCE Emacs init.el generator and Concept Operating System. It's used for managing my laptops' and desktop's and servers' and mobiles' software around an NixOS, Emacs, KDE, and Evil Mode. Arroyo Systems are distributed and developed as a collection of org-mode documents which can be used to provision and upgrade the system and are published on the web to enrich the lives of weirdos like me.

Arroyo allows you to build context-specific databases from a sort of hypermedia application which integrate with org-roam. Rather than extending or working within the API-space of org-roam itself, Arroyo is an org-mode parser and metadata extractor, and a database cache model layer which can be queried to assemble a NixOS system and highly-customized Emacs installation-and-configuration.

it's designed such that a user can plug various pieces of system configuration together in the form of org-mode documents downloaded or synced from trustworthy friends, creating a system which is literally (literately) self-documented.

An Arroyo System's configuration can be published on the web using Arcology, an python web document publishing framework built using Arroyo's parser and philosophies with the end goal of managing socially-maintained, hand-crafted, and user-customized Linux systems.

Arroyo Systems are "designed" to develop in fits and bursts

Arroyos are a type of stream bed biome common in the American southwest and northern Mexico Sonora Bioregion which is dry for most of the year and gets most of its rain in brief torrential surface flows. When I was young, I lived in a home which backed up to an arroyo and I spent quite some time wandering its trails and its unkept willows and catching my clothes on catclaws, using it as a shortcut through the neighborhood and an escape in to an increasingly developed suburban sprawl.

I was always enchanted with the arroyo during and after the torrential downpours Phoenix would have in the late summers, as tonnes of water passed through willows and waterweed. The arroyo would teem with life during the monsoon season as the brief intense rains pushed life out of its shaded cracks and in to a frenzy of growth and development and used it as a migration route just as the humans in the built environment around it did in its dry periods.

The Arroyo system pulls inspiration from this as a lens to look at how personal systems management is spurred on by

  • keeping up with ecosystem development and migration without undue effort
  • external changes and new tools should be easy to try and easy to then disregard
  • slow thinking and quick implementation of internal development to match with life needs
  • management of overgrowth through periods of careful usage and evaluation
  • an oasis path that cuts through the status quo

This system develops when I feel like it, and has slowly over the course of a decade developed in to something which can be shared and perhaps replicated. When a beautiful summer's day spurs me to investigate a new library or I learn about a new paradigm I sit and think about it. The Arroyo floods and growth follows quickly; there might not be another rain of insight until winter, after all.

NEXT Assembling an Arroyo System

Rebuild of The Complete Computer

  • How do I use these libraries to generate an Emacs init file?
  • How do I use these libraries to build a NixOS system?
  • How do I use these libraries to build an emacs-native-comp with packages provided by NixOS at build time?
  • How do I use these libraries to install and manage software for my user account?
  • How do I build more generators on top of this system?

Arroyo is itself an Arroyo Emacs module

It should probably be defined as a Arroyo Home Manager module, too, once the code has stabilized..

(add-to-list 'load-path "~/org/arroyo")
(require 'org-roam)
; (require 'arroyo-db)
; (require 'arroyo-utils)
(require 'arroyo-home-manager)
(require 'arroyo-nixos)
(require 'arroyo-emacs)
; (require 'arroyo-feeds)

Structure of the Arroyo (Or: Table of Contents)

(These are spread across multiple projects right now, I am still nailing down the exact structure of the Arroyo, Arcology, and CCE)

Greetz and Thanks

the emacs and nixpkgs communities

org-roam

pulling inspiration from vulpea and vino

Torbjorn Loken

alphapapa

maya kate

Yoshiki Shmitz (RIP to a real one)

Malleable Systems Collective