add ARCOLOGY_KEYs
parent
9a0e87d53f
commit
5d9b2fd250
|
@ -2,6 +2,7 @@
|
|||
#+ROAM_ALIAS: Arcology "Arcology README"
|
||||
#+CREATED: [2020-09-22]
|
||||
#+MODIFIED: [2020-09-22]
|
||||
#+ARCOLOGY_KEY: arcology/index
|
||||
|
||||
The Arcology is a system for publishing my org-mode documents to the web, an important component of Ryan Rix's [[file:../cce/cce.org][Complete Computing Environment]]. Rather than a pure static-site design, a directory full of "compiled HTML", the Arcology aims to provide *just enough* dynamicity to make publishing on the web simple, transparent, and powerful. Arcology uses the same database caching that Org Roam uses with some custom extensions to provide a web-view of a *subset of documents in my knowledge base*, and "indieweb" facilities around this like microformats, webmentions, indieauth, and some day a full ActivityPub implementation for my Journal and a "link blog" of my Archive posts.
|
||||
|
||||
|
|
|
@ -1,6 +1,7 @@
|
|||
#+TITLE: The Visual Identity of arcology
|
||||
#+CREATED: [2020-09-22]
|
||||
#+MODIFIED: [2020-09-22]
|
||||
#+ARCOLOGY_KEY: arcology/aesthetics
|
||||
|
||||
This module contains the base HTML templates for the application, as well as the webpack and scss configuration so that it's clear how all this fits together. I am not sure how to manage this reasonably for now. There's not a lot of assets for now, luckily.
|
||||
|
||||
|
|
|
@ -1,6 +1,7 @@
|
|||
#+TITLE: arcology backend application
|
||||
#+CREATED: [2020-09-22]
|
||||
#+MODIFIED: [2020-09-22]
|
||||
#+ARCOLOGY_KEY: arcology/application
|
||||
|
||||
In Elixir there is usually a frontend application which serves the Phoenix web site, and a backend service which it communicates with over Erlang messaging to do state management, business logic, and tasks like that, so that the frontend can stay as a "pure" MVC setup.
|
||||
|
||||
|
|
|
@ -1,5 +1,6 @@
|
|||
#+TITLE: Arcology DB Creates a Queryable Cache of Knowledge
|
||||
#+ROAM_ALIAS: "Arcology DB" "arcology-db"
|
||||
#+ARCOLOGY_KEY: arcology/arcology-db
|
||||
|
||||
I organize my personal [[file:../knowledge_base.org][Knowledge Base]] in [[file:../cce/org-roam.org][org-roam]] and org-roam creates a SQLite cache to achieve its performance and dynamicity. I extend this further, adding caching of page keywords, tracking the upstream code but for now a fork of it. I would love to reintegrate this code some time. This elisp code is based on Jethro Kuan's org-roam code and shares copyright with him.
|
||||
|
||||
|
|
|
@ -1,6 +1,7 @@
|
|||
#+TITLE: Arcology Page Module
|
||||
#+ROAM_TAGS: Arcology
|
||||
#+ROAM_ALIAS: Arcology.Page
|
||||
#+ARCOLOGY_KEY: arcology/page
|
||||
|
||||
The [[file:arcology_roam.org][Arcology Roam Models]] provide Ecto support for the [[file:arcology_db.org][arcology-db]], including =Arcology.Roam.File= which provides associations to the full data-model but is not *designed* to be programmed against. And since these are read-only concerns, a "smarter" structure can be built without having to worry about moving between the facile interface and the data models. This structure contains the relations in easy to use fashions. The titles are a list of strings instead of [[file:arcology_roam.org][Arcology.Roam.Titles]], y'know, stuff like that. I do wonder how to implement some sort of "proxy" interface like this which can create better views of data, while (somehow) supporting write-backs.
|
||||
|
||||
|
|
|
@ -2,6 +2,7 @@
|
|||
#+ROAM_TAGS: Arcology
|
||||
#+ROAM_ALIAS: "Arcology.Roam" "Arcology.Roam.File" "Arcology.Roam.Keyword" "Arcology.Roam.Link" "Arcology.Roam.Reference" "Arcology.Roam.Tag" "Arcology.Roam.Title"
|
||||
#+ROAM_KEY: https://code.rix.si/rrix/arcology/src/branch/main/arcology_roam.org
|
||||
#+ARCOLOGY_KEY: arcology/roam
|
||||
|
||||
These are the Ecto models and support functionality for the database tables provided by [[file:arcology_db.org][Arcology DB]]. These are all *read only* concerns, the write-path is in Arcology DB right now, where the org-mode parser is. Any database which I intend to write to should probably be an =postgrex= =ecto 3= model in its own OTP application, and is out of scope for this file.
|
||||
|
||||
|
|
|
@ -1,5 +1,6 @@
|
|||
#+TITLE: ArcologyWeb Phoenix Frontend
|
||||
#+ROAM_ALIAS: ArcologyWeb.Endpoint ArcologyWeb ArcologyWeb.Router ArcologyWeb.GetText
|
||||
#+ARCOLOGY_KEY: arcology/web
|
||||
#+CREATED: [2020-09-22]
|
||||
#+MODIFIED: [2020-10-11]
|
||||
|
||||
|
|
|
@ -1,5 +1,6 @@
|
|||
#+TITLE: Project Configuration for arcology
|
||||
#+ROAM_ALIAS: "Arcology Phoenix"
|
||||
#+ARCOLOGY_KEY: arcology/project
|
||||
#+CREATED: [2020-09-22]
|
||||
#+MODIFIED: [2020-09-22]
|
||||
|
||||
|
|
|
@ -1,13 +1,14 @@
|
|||
#+TITLE: arcology Test Support
|
||||
#+CREATED: [2020-09-22]
|
||||
#+MODIFIED: [2020-09-22]
|
||||
#+MODIFIED: [2020-10-11]
|
||||
#+ARCOLOGY_KEY: arcology/testing
|
||||
|
||||
#+begin_src elixir :tangle test/test_helper.exs :mkdirp yes
|
||||
ExUnit.start()
|
||||
Ecto.Adapters.SQL.Sandbox.mode(Arcology.Repo, :manual)
|
||||
#+end_src
|
||||
|
||||
* Support for Connection Cases
|
||||
* Support for Connection Cases
|
||||
|
||||
#+begin_src elixir :tangle test/support/conn_case.ex :mkdirp yes
|
||||
defmodule ArcologyWeb.ConnCase do
|
||||
|
|
|
@ -1,4 +1,5 @@
|
|||
#+TITLE: arcology client/server push socket
|
||||
#+ARCOLOGY_KEY: arcology/usersocket
|
||||
#+CREATED: [2020-09-22]
|
||||
#+MODIFIED: [2020-09-22]
|
||||
|
||||
|
|
Loading…
Reference in New Issue