r/o

send emails in background with oban 2e8581ac parent 8fe5b1fd

authored by ~lotte

1
* [ ] https://github.com/GitoxideLabs/gitoxide instead of libgit2
2
3
* [ ] We might want to make an über-NIF including connecting to Comrak/ammonia/etc. ourselves (or a separate NIF for that), since overriding stuff in MDEx/Autumn is hard. See markdown.ex.
4
5
* [ ] show dag nav on mobile with popout
6
7
* [ ] use read replica where appropriate
8
* [ ] address our lack of sendmail in container; send mail to status.hostIP:25 (no auth)
9
* [ ] "hooks" also point HEAD to tags when received, oops
10
* [ ] autumn and mdex NIFs are both around 80MB; the latter includes the former. dedupe.
11
12
* [-] per-repo deploy keys: R/O, R/W
13
* i want this for flux
14
* [x] everything except the UI
15
* [ ] the UI
16
* [ ] update the unique index to be per-repo since we've changed auth anyway
17
18
* [ ] tree view isn't getting the right commits for files in subdirectories
19
since we're back to one-directory-at-a-time and need to redo how we search
20
for the last changed commit.
21
* [ ] relative URIs: ugc- prefix, #xyz shouldn't navigate away, etc.
22
* [ ] pressing browser forward/back should trigger fancy blob highlights, not
23
just the automatic :target ones
24
* [ ] some patch links really need to scroll back to top
25
* [ ] actually show commit details at top of tree/blob views
26
27
* [ ] https://talya.nossa.ee ?
28
29
* [ ] visual confirmation on "copy to clipboard" shouldn't be a modal, just temporarily change the icon
30
31
### short term
32
33
- [x] blob
34
- [x] images
35
- [ ] pdfs, etc.
36
- [ ] less polysaturated, leaner design
37
- [ ] do we use Binary explicitly to not have to pass Unk back as a linked list? @fun
38
- [ ] get our tests and coverage fixed again. @pls
39
- [ ] message to end-user when following a redirect (via git)
40
41
### features
42
43
- [ ] dag infinite scroll/load to context
44
- [ ] blob permalink
45
- [ ] responsive (mobile) styles
46
- [ ] override locale user option
47
- [ ] diff 2+ parent commit
48
- [ ] passkey support
49
- jfc https://shadowfacts.net/2023/phoenix-passkeys/
50
- [ ] default branch: choose from existing branches; non-UTF-8 support
51
52
### housekeeping
53
54
- [ ] tab indices on e.g. crear repositorio
55
- [ ] IPv6 check
56
- [ ] redirect to primary host if not on it
57
- [ ] reverse where the structs are defined (between Git2/Nossa.Storage*)
58
- [ ] rename RepositorySelf* to RepositorySettings*?
59
- [ ] extract CGI into its own application; stream request/response in/out
60
- [ ] consider erlexec, or write our own driver, so we can get stderr out of
61
the way
62
- [ ] gettext once-over in hard-to-reach spots
63
- [ ] verify typescript in compile step
64
- [ ] override elixir/erlang used in autumn/mdex to keep all together
65
- there's some wip of this in zmlqmwzq
66
67
### graceful degradation
68
69
- [x] branch selector disappears on safari with javascript on
70
- [ ] "method" links don't work with noscript since they don't do the right
71
thing
72
- [ ] can't dismiss flash
73
- [ ] javascriptless sidebar changes? (then they must go in the URL)
74
75
### production ops
76
77
- [ ] caching: nginx, varnish? fragment?, git object? how much does bandwidth
78
cost at ovh? bunny? integrate caching, backup into nix module.
79
- right now the pawiwo visibly reloads on every page
80
- [ ] DIY anubis? (for easy deploy to other Phoenix/etc. strength in diversity @fun
81
is a real consideration in this fight.)
82
- [ ] backup restore procedure/test
83
- [ ] feature that restores from backup as we make it. ez!
84
- [ ] admin diagnostics page (combine into/with live dashboard somehow?)
85
- [ ] per repo: audit log, pushes, etc. (git hooks?)
86
- [ ] LRU-ish app-level caching: memcached? redis? ets? mnesia?
87
88
### future
89
90
- [ ] avatar upload
91
- [ ] federation?
92
- identity: auth to other nossa instance
93
- auth another instance for avatars
94
- federated MR-type deal?
95
- don't want to redo a whole code review thing here, idt? check out gerrit
96
etc.
97
- see also simon tatham's thing on git; pull request is just "please check
98
again"
99
- opinionated about rebase/jj norms
100
- at the very least we could show interdiffs between pushes etc.
101
- [ ] merge queue? what do i need at work?
102
- [ ] Log in with GitHub/GitLab/Forgxejo? make it easy to work across, to not be
103
completely hecked by network effects?
104
105
106
## archivo
107
108
- [x] change "settings" top right to "account"
109
- [x] repository delete
110
- [x] repository storage
111
- [x] push keys
112
- [x] proper logging (insert some in e.g. storage creation failure)
113
- [x] some kind of log aggregation/interface on kala
114
- [x] test coverage back up
115
- [x] do some more!
116
- [x] work out why jj fails to push!
117
- [x] fix up this /blah/!url nonsense
118
- [x] git store tests
119
- [x] git tests async: use per-runner store
120
- [x] last controller tests
121
- [x] don't rename storage: use only numeric ids in storage
122
- [x] figure out why our distribution metrics ("phoenix.*") don't make it to
123
grafana (or appear in /metrics at all)
124
- [x] try ETS
125
- [x] pawiwo icon
126
- [x] clean up RepositoryGitControllerTest
127
- [x] Anubis/Nepenthes/?
128
- See https://lobste.rs/s/dmuad3/mitigating_sourcehut_s_partial_outage --- we
129
will need to be prepared; robots.txt, etc., and above all usage stats/graphs
130
so we can see it happen.
131
- [x] https://git.sr.ht/robots.txt is a good start, though of course it isn't
132
saving them. Still, no reason to start from zero.
133
- [x] start of gettext support
134
- [x] main browsing interface, ui polish/consistency
135
- [x] navigate tree
136
- [x] zindex fix for icons overlaying nav bit
137
- [x] select commit
138
- need to resolve a rev instead of a branch now
139
- [x] include breadcrumbs in Diff view
140
- [x] wherever "path=" is sneaking into our URLs, get it out (breadcrumbs)
141
- [x] liveview for navigating within
142
- [x] extract inline classes into css (w/ @apply)
143
- [x] dark mode styles
144
- [x] actual colour system
145
- [x] pawiwo svg for colours
146
- [x] ok dark mode again
147
- [x] safari, chromium
148
- [x] repository redirects
149
- [x] tailwind v4
150
https://elixirforum.com/t/mix-tailwind-4-0-0-beta-1-support/67636/17
151
- [x] more post-liveview cleanup of repository controller; check over
152
auth-related stuff.
153
- [x] then back to (re)design
154
- [x] work out whether diff view will be within the same liveview, a different
155
one, etc.? - it may be overkill; navigating the tree responsively is nice,
156
but the huge diffs might make browsers sick. gotta test!
157
- [x] decide on the repository view design; do we keep the commits there? do
158
we make the sidebar collapsable a la ~~yuta~~ hexdocs etc.? something
159
else entirely?
160
- what do i want to see when i hit a root of a repo? what are the various
161
reasons i end up on one of those on github/srht/etc.?
162
* linked to as a project's "home page", searched and the first result (or
163
apparent best result for an official download or similar)
164
* directly navigated to because i want to browse the source of something
165
i don't have a local clone of (and i haven't yet hit the threshold
166
where i need to use tools to look thru; source aware views can sometimes
167
abrogate the need but often (e.g. github's views + semantic index)
168
they're an untenable degree of both meh design usability (in e.g., links
169
are all too small, everything bunched up on the side, often starting to
170
scroll horizontally by this point; not a priority) and flawed impl (in
171
e.g. elixir outlining. is this just from elixir-ls? tree-sitter?))
172
* often want a specific version (i.e. something i'm running/using),
173
sometimes just browse main/master if cbf/not relevant/more interested
174
in design than exact
175
* summary of this point: "whatever would be unnecessary if i always had
176
a clone of everything". i don't, but i'm in the position of improving
177
the situation for when you don't -- what actually helps?
178
* sometimes i do this even in the presence of a clone on disk, because
179
i'm *using* that one somehow, but i cbf creating a new worktree.
180
similar result. a browser window (and the way you can open lots of
181
them, to various paths/versions/etc) is a much smaller cognitive unit
182
to manage than a worktree.
183
* how often do i want to see the whole commit list straight up front like
184
this? (day separations would give this a lot more context, for what
185
it is.)
186
* almost always would prefer the *graph*; i almost never prefer the
187
straight log style locally. (think about jj log view.)
188
* there are three axes: commit (temporal), path (spatial), view (fn).
189
github exposes commit consistently, path inconsistently (compare blob
190
view to commit history restricted to a subpath), view inconsistently
191
("Commits" page vs 2.5 tree pages (root, non-root w/ README, non-root;
192
sidebar tree only visible in non-root) vs blob (very aligned with
193
non-root tree). root really is the odd one out, since it's a landing
194
page.)
195
* big commit *graph* that stashes in side: file listing-style tree view
196
that then collapses into expanding tree sidebar: blob.
197
* then you can shift around points in the graph while retaining
198
visibility over the directory tree, no reloads/scrolls breaking
199
"immersion".
200
* does the graph stash over to a plain log? i should make sure while i'm
201
developing that i work with the browser the sizes i want to actually
202
be using it at. (i.e. push back against default to 2/3rds code, unless
203
i'm developing a usecase where i'd have the browser at 1/3rd).
204
* sometimes you do want to view just the log of a file or subtree.
205
kinda wanna apply that filter *to* the far-left graph, as a
206
saved-in-navigation thing. then you can nav to a commit (still
207
centred on the tree or file you started the filter from), see it in
208
context, move around, and then at some point you back up or clear
209
the 'path filter' on the DAG view.
210
* note that we want the current path to remain in the tree view
211
when navigating the DAG view even when we don't have a path filter
212
active. same with current blob, if any.
213
* this kind of removes that fake third axis, exposes the other two as
214
proper orthogonal ones. github flattening the DAG with no way to
215
recover is criminal.
216
* and then there's commit view, which is a whole other thing: viewing a
217
commit message & diff.
218
- [x] let's fix our URIs in gen i guess, ?path= is ugly
219
- [x] support submodules in tree
220
- [x] be explicit in which params are UTF-8 encoded & which aren't
221
- [x] global support for non-UTF-8; no error messages
222
- [x] navigate commits on left; focus current commit as navigating
223
- [x] compile-time the storage layer choice
224
- [x] vyxos push fails!
225
- [x] "last commit modified" links are incorrect for subtrees, there's a TODO in
226
git2.rs somewhere
227
- [x] decompose git2's monster "resolve_commit" into somewhat orthogonal ops
228
- [x] syntax highlighting
229
- [x] little live demo with channels of push response
230
- [x] reaffirm backup situation for kala
231
- [x] nix syntax highlighting egumi??
232
- [x] wow! nossa in docker/k8s!
233
- [x] ES: "Clave de empujar creada exitosamente" when creating a new repo!?
234
- [x] new repo => brocken
235
- [x] remove register links if register is disabled
236
- [x] install our own git hooks in repositories, set HEAD on push if unset
237
- [x] assign default branch on first push
238
- [x] this causes clone failures, the weird nix flake stuff we've been seeing, etc.
239
- [x] floating windows don't preserve state on livereload
240
- [x] let's fix the first thing: navigating back to a subtree shouldn't close an
241
open blob. we can keep our existing assigns, or just stream.
242
- [x] open new windows in specified order
243
- [x] default orientation based on aspect ratio
244
- [x] splith(3): need to have up/down too; splitv(3) needs to have left/right.
245
it's too hard to just do that with merges and unmerges.
246
- [x] skip floating windows when finding clientInDirection; similarly,
247
moveClient/mergeClient; their behaviour is very puzzling if it's not clear
248
what's happening
249
- [x] "hooks" are breaking on current live because they're symlinks into old
250
versions of nossa, since GC'd from the nix store!
251
* [x] shynet: add javascript call on live patch
252
* [x] what's nom? https://github.com/NixOS/nixpkgs/pull/430275#pullrequestreview-3089109039
253
* [x] set inline-block for repo breadcrumbs so the underline doesn't over-extend
254
* [x] NixOS tests to ensure the module stays good even after we move to deploying on k8s
255