aesthetic.computer
Monorepo for Aesthetic.Computer
aesthetic.computer
1🧪 Dev Log
2Practical and conceptual notes weaved together.
3
4🚗 Migration:
5 - https://vercel.com/guides/migrate-to-vercel-from-netlify
6
7⛈️ Shortcuts / Bookmarks
8 - auth0 Templates: https://manage.auth0.com/dashboard/us/aesthetic/templates
9 - Netlify Environment Variables: https://app.netlify.com/sites/aesthetic-computer/configuration/env
10
11🕸️ W3C Proposals To Watch:
12- https://www.w3.org/TR/mediacapture-fromelement
13
14📽️ Research
15 - [] Watch WebXR on Apple Vision Demo: https://developer.apple.com/videos/play/wwdc2024/10066/
16 - [] Raaaga Basics: https://www.youtube.com/playlist?list=PLdOV4QmXfJcGGnhbCKyP-dD5nppGBY3kY
17
18☁️ Ideas
19- Maybe aesthetic.computer is more of an interface project
20 or search engine or *branded* prompt than it is a creative
21 platform?
22
23- Large scale re-organization:
24 - Every piece is a set of functions.
25 - Functions are like "plug-ins" to aesthetic.computer.
26 - They enable certain device features like the ability to make a sound or
27 display an image.
28 - Code modules / libraries in aesthetic.computer are loaded based on the
29 functions the piece uses.
30 - New functionality can always be added and improved upon, and new global APIs
31 can be created with this architecture in mind.
32 ✨ Perhaps there is more power in smaller APIs than there is in larger APIs?
33
34❓ Questions
35- How does aesthetic.computer relate to urbit?
36
37- What would editing lisp-like syntax feel like in VS code / my own
38 browser editor?
39
40🧑💻 Text Editor / Shell Notes
41- [] nvim guide: https://www.youtube.com/watch?v=0moS8UHupGc&t=7s
42 https://www.youtube.com/watch?v=stqUbv-5u2s
43- [] How would I make my own org-mode style editor with this feature? https://stackoverflow.com/questions/25161792/emacs-org-mode-how-can-i-fold-everything-but-the-current-headline
44- [] Install / try the new embedded neovim extension for VSCode.
45- [] https://github.com/ggandor/leap.nvim
46- [] Start a blog or journal of some kind - that is sourced from
47 this repository?
48- [] Add hybrid bindings to fish: https://github.com/fish-shell/fish-shell/blob/master/share/functions/fish_hybrid_key_bindings.fish
49
50💻 Docs
51
52 -> How to Deploy & Mint Contracts
53 - (Replace NETWORK with either: `local`, `rinkeby`, `ropsten` or `mainnet`)
54 - `cd` into `ethereum-lwge` directory
55 - (`local` only) Start running in a separate terminal:
56 `npm run NETWORK:node`
57 - In a terminal: `npm run NETWORK:balance`
58 - In a terminal: `npm run NETWORK:deploy`
59 - Copy the address after "💚 Deployed to:"
60 - `npm run NETWORK:verify -- [PASTED ADDRESS]` to add the source to etherscan.
61 - `npm run NETWORK:mint -- [PASTED ADDRESS]`
62
63-> Meta Quest Remote Debugging (Manual Setup):
64 https://developer.oculus.com/documentation/web/browser-remote-debugging/
65 (All commands can be entered in order except on Windows / WSL2 setups)
66
67 1 ❯ adb devices
68 List of devices attached
69 1WMHHA62V22187 device
70
71 2 ❯ adb shell ip route (also run in Windows?) (This is for websockets...)
72 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.31
73
74 3 ❯ adb tcpip 5555 (run in Windows)
75 restarting in TCP mode port: 5555
76
77 4 ❯ adb connect 192.168.1.31:5555 (run in WSL2)
78 connected to 192.168.1.31:5555
79
80 * On Windows with WSL2 some of these steps need to be duplicated across OS's.
81 - See also: https://stackoverflow.com/questions/60166965/adb-device-list-empty-using-wsl2
82
83-> GitHub Codespaces (Manual Setup):
84 A. Clone my dotfiles repo and install chezmoi via the chezmoi/dotfiles install.sh script.
85 B. For running the frontend:
86 1. install git lfs to get media files: `git lfs install; git lfs pull`
87 2. `cd` into `system` and then `npm install`
88 3. login to netlify via `npx netlify login` and link the site with `npx netlify link`
89 4. now you can `cd -` and then run `npm run code`
90 to start the frontend, fully simulating the netlify production environment
91 (with exception to the automatic https tunneling via nginx in the codespaces container)
92 (Outdated) C. For running the server backend:
93 1. `cd` into `server` and then `npm install`
94 2. add `NODE_ENV=development` to a `.env` file in `server`
95 3. Note: websockets (wss) cannot be port forwarded by codespaces atm
96
97-> Local Server (Notes):
98 Use `fnm` (https://github.com/Schniz/fnm) and the .node-version file under
99 `system` to manage node versions (currently the project is on lts/gallium [16])
100
10122.07.26.20.19
102
103***Recently Done***
104
105* Start over with my dotfiles
106 - [x] Get my dotfiles working (especially get fish running) in github codespaces.
107 - [x] Wipe dotfiles repository.
108 - [x] Start a fresh set from this codespace that simply symlinks a few things,
109 like my fish settings, and installs anything I need via an install.sh script.
110 - [x] Follow along here: https://bea.stollnitz.com/blog/codespaces-terminal