sup39/vervis
1
0
Fork 0
mirror of https://code.sup39.dev/repos/Wqawg synced 2024-12-26 03:04:50 +09:00
Code Issues Activity
1277 commits 3 branches 0 tags 17 MiB
Commit graph

1277 commits

This branch
This branch
All branches
Author SHA1 Message Date
sup39
284b4a8d81
fix: prevent panic on parse error in repo page 2024-01-11 00:14:38 +09:00
sup39
8c7ed627b6
feat: add raw file link in source file browser 2024-01-10 07:09:59 +09:00
sup39
cc676504bc
feat: implement raw file browsing 2024-01-10 06:50:11 +09:00
naskya
756d40793a
Merge remote-tracking branch 'upstream/main' 2023-12-14 14:15:46 +09:00
Pere Lev
ab786eb67c
UI, Vocab: Link from project/team to children & parents pages 2023-12-13 00:09:28 +02:00
Pere Lev
802df6b15b
UI, AP: Display project and team children and parents 2023-12-12 23:21:06 +02:00
Pere Lev
1f06d689f5
Tables for project/team parent/child tracking 2023-12-11 18:49:42 +02:00
Pere Lev
ee91a6403e
UI: Add 'Accept' button to invites you haven't yet accepted 2023-12-09 10:24:20 +02:00
Pere Lev
ce1e542401
UI: HomeR: Display personal invites 2023-12-09 08:55:39 +02:00
Pere Lev
e65563cd19
UI: For each Permit, display delegator-Grant and extensions 2023-12-09 07:58:16 +02:00
Pere Lev
119779b9b3
UI: Display personal resources using Permit records 2023-12-09 07:13:34 +02:00
Pere Lev
5af2fdd58b
UI: Group: Buttons for adding and removing members 2023-12-09 03:03:06 +02:00
Pere Lev
702ad39b96
S2S: Group: Adapt collab-mode code from Project 2023-12-09 02:46:11 +02:00
Pere Lev
b2b4d8778d
DB: For each CollabRecipLocal record, produce a matching Permit record 2023-12-09 01:04:21 +02:00
Pere Lev
12e2284389
C2S: When creating a resource, insert a Permit record 2023-12-07 18:50:44 +02:00
Pere Lev
e2462627a5
Remove old empty Vervis.Federation.Collab module 2023-12-07 18:22:51 +02:00
Pere Lev
cfc8add212
S2S: Common: Remove: When deleting Collab record, delete CollabDeleg*s too 2023-12-07 18:21:35 +02:00
Pere Lev
6dceaa1cff
S2S: Person: Revoke: Delete Permit records 2023-12-07 17:03:26 +02:00
naskya
3eb1c7d17e
Merge remote-tracking branch 'upstream/main' 2023-12-03 13:20:53 +09:00
Pere Lev
11a79b00fb
S2S: Person: Implement response to direct-Grant and extension-Grant 2023-12-02 21:09:13 +02:00
naskya
deb19783b3
chore: use compact time units (e.g., seconds -> s) 2023-12-01 05:27:32 +09:00
Pere Lev
39dc2089b2
S2S: Person: Accept: If topic is approving an Invite, update Permit record 2023-11-23 18:21:41 +02:00
Pere Lev
442e36dcc1
C2S: Accept: If accepting an Invite-for-me, update the Permit record 2023-11-23 01:03:50 +02:00
Pere Lev
0c0007c892
C2S: Person: Implement Join handler, inserting a Permit record to DB 2023-11-22 23:12:32 +02:00
Pere Lev
3c0a3d1317
S2S: Person: Update Invite handler to create a Permit record 2023-11-22 19:30:33 +02:00
Pere Lev
05d3a1eaef
DB: Tables for the person side of Collabs (i.e. direct-Grants they got) 
Until now I've managed to avoid having to implement this piece quite
easily. The only temptation to implement it has been pseudo-client
features, which are basically just a workaround until Vervis gets a
separate client app.

But now, Person actors need to be able to automatically send
delegator-Grants when they receive a direct-Grant from a resource they
either asked to Join or got an Invite to. So, this creates a need to
track these joins and invites on the server side.

I'm not checking the exact minimal pieces necessary for
delegator-Grants. Instead, I'm starting a full implementation of the
person-side of Collab records (AKA direct-Grants), called Permit
records. This will also allow very convenient display of these Grants
and the extensions received through them, as well as UI buttons such as
accepting/rejecting a received Join or Invite.
 2023-11-22 18:11:07 +02:00
Pere Lev
88e6818edc
S2S: Project: Send ext-Grants to new collab upon getting their delegator-Grant 
Until now, adding a direct collaborator to a Project worked exactly like
with components: Invite or Join, then Accept, finally the direct-Grant.
I missed the fact that much like with project-component relationships,
projects (and teams) need to be able to send extension-Grants to their
direct collaborators.

So in Project's Grant handler it now:

- Recognizes the delegator-Grant coming from a new collaborator
- Sends extension-Grants, using the delegator-Grant as the capability
- When getting a new component and sending extension-Grants for it to
  direct collaborators, Project uses their delegator-Grants as
  capability

And in Project's Accept handler, it no longer sends extension-Grants
(because it doesn't yet have the collaborator's delegator-Grant at this
point).

NOTE, THIS TEMPORARILY BREAKS grant chains: If you create a Project and
add a Deck to it, you won't get an extension-Grant-for-the-Deck from the
Project, because the Project doesn't yet have your delegator-Grant.

The next commits will implement the Person-side of Collab records, and
will cause Person actors to automatically send the delegator-Grant,
fixing the break.
 2023-11-22 14:16:08 +02:00
Pere Lev
5d0f707c55
DB: Allow to record the delegator-Grant sent by people to projects/teams 2023-11-21 20:44:09 +02:00
Pere Lev
7517db9619
Client, UI: Team: Creation, invite/join display, list in personal overview 2023-11-21 18:28:05 +02:00
Pere Lev
8584c6387c
S2S: Group: Implement Follow & Undo handlers, adapted from Project 2023-11-21 17:02:58 +02:00
Pere Lev
8d543c0016
S2S: Group: Implement Create handler, sending back an admin-Grant 2023-11-21 16:52:16 +02:00
Pere Lev
ea7476db9d
C2S: Implement team creation 2023-11-21 15:48:14 +02:00
Pere Lev
2797e5f3be
UI: Team & team members HTML page + AP JSON object 2023-11-21 15:01:51 +02:00
Pere Lev
80a08dea0a
UI: Browse: Update intro text & list projects' components 2023-11-21 10:56:09 +02:00
Pere Lev
840b13eff1
UI: Tweak the footer repo/commit display 2023-11-21 10:55:38 +02:00
naskya
7b61749198
Merge remote-tracking branch 'upstream/main' 2023-11-15 14:06:07 +09:00
Pere Lev
22c7b88a79
Remove federation check from PublishResolveR 2023-11-13 14:15:13 +02:00
Pere Lev
34386bcf52
S2S: Deck: Resolve: Use the full OCAP-authorization algorithm 
deckResolve now supports Resolve requests that use extension-Grants. It
iterates the verifies the Grant-chain using the process described in the
ForgeFed specification.
 2023-11-12 17:43:11 +02:00
naskya
28ff20e754
fix: vervis.peers.community can now be accessed with https 2023-11-12 04:12:41 +09:00
naskya
48ab96aae8
Merge remote-tracking branch 'upstream/main' 2023-11-11 21:37:13 +09:00
naskya
afc12de256
style: hide ticket number link 2023-11-11 20:09:53 +09:00
naskya
a484cc3025
style: hide the left most link in the navbar 2023-11-10 06:07:10 +09:00
naskya
9e9f5538aa
style: hide clone URI 2023-11-09 15:37:18 +09:00
naskya
ac729446a7
dev: gitignore backups 2023-11-09 11:01:55 +09:00
naskya
1bf1fb22c5
fix: preserve whitespaces in added/removed file 2023-11-08 15:26:19 +09:00
naskya
2e2e6bc630
style: make diff tab size 4 2023-11-08 15:24:18 +09:00
Pere Lev
1a3a46b6b2
Implement OCAP "Verifying an invocation" process from ForgeFed spec 
Vervis currently supports only direct grants. The new process supports
delegation chains as well. This commit just implements the new process
as a new function, without yet using it anywhere. The next commits will
plug it into Deck actor handlers.
 2023-11-07 10:51:42 +02:00
naskya
c150b11e19
style: remove text-align: jusify 2023-11-07 04:56:33 +09:00
naskya
b98825312a
chore: disallow crawlers in robots.txt 2023-11-06 21:35:43 +09:00
naskya
d4c7842b15
style: use softer colors for diff display 2023-11-06 21:35:13 +09:00