forge/Vervis
1
0
Fork 0
Code Pull requests Activity
Vervis/vervis.cabal

551 lines
21 KiB
Text
Raw Normal View History

Clearly specify license as AGPL-3-or-later in cabal file
2023-06-16 16:14:40 +02:00
cabal-version: 2.2
Initial record with empty package that builds
2016-01-28 15:15:54 +01:00
name: vervis
No trailing zero components in version number
2016-04-12 17:19:02 +02:00
version: 0.1
Update package description in vervis.cabal, we're already federating! Mostly :P
2020-05-24 11:17:57 +02:00
synopsis: Federated project hosting platform
Initial record with empty package that builds
2016-01-28 15:15:54 +01:00
description:
Update package description in vervis.cabal, we're already federating! Mostly :P
2020-05-24 11:17:57 +02:00
Vervis a decentralized software project hosting web application, which
federates using ActivityPub and ForgeFed.
Releases are under AGPL 3
2018-03-17 19:21:51 +01:00
.
Most of the source code is in the public domain using the CC0 public domain
dedication, but the application as a whole has GPL dependencies, and is
released under the AGPL 3 license.
Update docs for darcs->git switch, and switch from darcs-rev to gitrev
2023-05-25 12:54:03 +02:00
homepage: https://vervis.peers.community/repos/rjQ3E
bug-reports: pere@towards.vision
Clearly specify license as AGPL-3-or-later in cabal file
2023-06-16 16:14:40 +02:00
license: AGPL-3.0-or-later
vervis.cabal: Specify license as AGPL-3 because that's the release license
2022-09-06 17:38:34 +02:00
license-file: COPYING.AGPL3
Update docs for darcs->git switch, and switch from darcs-rev to gitrev
2023-05-25 12:54:03 +02:00
author: Pere Lev
maintainer: pere@towards.vision
Initial record with empty package that builds
2016-01-28 15:15:54 +01:00
copyright: ♡ Copying is an act of love. Please copy, reuse and share.
category: Development, Distribution, Git, Web
build-type: Simple
Update format of AUTHORS file, link to Fedi accounts instead of email
2022-09-01 11:28:38 +02:00
extra-source-files: AUTHORS.md
Rename NEWS.md to CHANGELOG.md
2018-05-14 17:25:16 +02:00
CHANGELOG.md
Initial record with empty package that builds
2016-01-28 15:15:54 +01:00
COPYING
Explain current federation status in FEDERATION.md new file
2019-05-05 13:15:51 +02:00
FEDERATION.md
Initial record with empty package that builds
2016-01-28 15:15:54 +01:00
INSTALL.md
README.md
source-repository head
Update docs for darcs->git switch, and switch from darcs-rev to gitrev
2023-05-25 12:54:03 +02:00
type: git
location: https://vervis.peers.community/repos/rjQ3E
Initial record with empty package that builds
2016-01-28 15:15:54 +01:00
Bring Yesod scaffolding
2016-02-13 04:35:30 +01:00
flag dev
description: Turn on development settings, like auto-reload templates.
default: False
flag library-only
description: Build for use with "yesod devel"
default: False
Initial record with empty package that builds
2016-01-28 15:15:54 +01:00
library
Expose only required modules of vervis:library in vervis.cabal Only Vervis.Hook (for the hook programs) and Vervis.Application (for the web app program itself) are exposed now. I suppose more will be needed for tests. But now there's a clear distinction what's used by other components and what isn't.
2022-09-01 11:34:25 +02:00
exposed-modules:
Vervis.Application
Vervis.Hook
other-modules:
Control.Applicative.Local
Implement actor-model system and start moving Person actor to it This patch makes Vervis temporarily unusable, because all actors' inbox POST handlers use the new system, but the actual federation handler code hasn't been ported. The next patches will port all the S2S activities supported so far, as well as C2S.
2023-04-29 12:40:44 +02:00
Control.Concurrent.Actor
Launch service thread with a function that re-throws if they fail In Haskell by default if a thread has an exception, the main thread isn't notified at all. This patch changes service thread launching to re-throw their exceptions in the main thread, so that their failure is noticed.
2019-01-14 23:03:49 +01:00
Control.Concurrent.Local
Unfinished updated outbox handler
2019-04-11 15:44:44 +02:00
Control.Concurrent.ResultShare
Implement actor-model system and start moving Person actor to it This patch makes Vervis temporarily unusable, because all actors' inbox POST handlers use the new system, but the actual federation handler code hasn't been ported. The next patches will port all the S2S activities supported so far, as well as C2S.
2023-04-29 12:40:44 +02:00
Control.Concurrent.Return
New module structure for ActivityPub C2S and S2S code
2019-06-15 06:39:13 +02:00
Control.Monad.Trans.Except.Local
Improve the AP async HTTP delivery API and per-actor key support New iteration of the ActivityPub delivery implementation and interface. Advantages over previous interface: * When sending a ByteString body, the sender is explicitly passed as a parameter instead of JSON-parsing it out of the ByteString * Clear 3 operations provided: Send, Resend and Forward * Support for per-actor keys * Actor-type-specific functions (e.g. deliverRemoteDB_D) removed * Only the most high-level API is exposed to Activity handler code, making handler code more concise and clear Also added in this patch: * Foundation for per-actor key support * 1 key per actor allowed in DB * Disabled C2S and S2S handlers now un-exported for clarity * Audience and capability parsing automatically done for all C2S handlers * Audience and activity composition automatically done for Vervis.Client builder functions Caveats: * Actor documents still don't link to their per-actor keys; that should be the last piece to complete per-actor key support * No moderation and anti-spam tools yet * Delivery API doesn't yet have good integration of persistence layer, e.g. activity is separately encoded into bytestring for DB and for HTTP; this will be improved in the next iteration * Periodic delivery now done in 3 separate steps, running sequentially; it simplifies the code, but may be changed for efficiency/robustness in the next iterations * Periodic delivery collects per-actor keys in a 1-DB-transaction-for-each-delivery fashion, rather than grabbing them in the big Esqueleto query (or keeping the signed output in the DB; this isn't done currently to allow for smooth actor key renewal) * No support yet in the API for delivery where the actor key has already been fetched, rather than doing a DB transaction to grab it; such support would be just an optimization, so it's low-priority, but will be added in later iterations
2022-10-12 18:50:11 +02:00
Crypto.ActorKey
HTTP Signature verification: RSA-SHA256 and PEM/ASN1 support Before, things worked like this: * Only signatures of Ed25519 keys could be verified * Key encoding placed the plain binary Ed25519 key in the PEM, instead of the key's ASN1 encoding With this patch it now works like this: * Ed25519 signatures are supported as before * RSA keys are now supported too, assuming RSA-SHA256 signatures * Both Ed25519 and RSA keys are encoded and decoded using actual PEM with ASN1
2019-03-11 00:15:42 +01:00
Crypto.PubKey.Encoding
Crypto.PublicVerifKey
Darcs change log view
2016-05-08 16:28:03 +02:00
Darcs.Local.Repository
Implement theater-based remote delivery and port personGrant
2023-05-25 00:17:14 +02:00
Data.Slab
Data.Slab.Backend
Data.Slab.Simple
Federation test outbox page with form for entering JSON
2019-01-21 16:54:57 +01:00
Data.Aeson.Encode.Pretty.ToEncoding
Move some JSON/AP codec utils to new Data.Aeson.Local module
2019-02-03 12:01:36 +01:00
Data.Aeson.Local
Darcs change log view
2016-05-08 16:28:03 +02:00
Data.Attoparsec.ByteString.Local
Enable Darcs repo creation using the executable Darcs does export most of its module tree, but there's a problem: Darcs relies on the current directory. It changes the current directory of the process to the repo, and then proceeds using paths relative to the repo dir. This is bad for my case here. If some other thread uses a relative path (e.g. currently any repo path is relative by default) in parallel, it will fail. For now, the quick path around this problem is to use the `darcs` program.
2016-05-04 13:44:06 +02:00
Data.Binary.Local
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
-- Data.Bitraversable.Local
Incremental binary stream decoder, generalized from hit-network
2016-04-24 20:25:30 +02:00
Data.ByteString.Char8.Local
Work on git pack protocol, not done yet This is a lot of code, better save now than sorry later when something gets deleted by mistake. Either way, the code will move later - once tested and organized properly - into its own package.
2016-04-01 07:00:02 +02:00
Data.ByteString.Local
Finish route change, it builds now I used this chance to make some name changes, add some utils, tweak some imports, remove more `setTitle`s and so on. I also made person, repo, key and project creation forms verify CI-uniqueness.
2016-05-23 22:46:54 +02:00
Data.CaseInsensitive.Local
Implement git history log in repo page
2016-03-03 09:15:54 +01:00
Data.Char.Local
Mechanism for reporting git pushes to Vervis via post-receive hooks Here's how it works: - When Vervis starts, it writes a config file and it writes post-receive hooks into all the repos it manages - When a git push is accepted, git runs the post-receive hook, which is a trivial shell script that executes the actual Haskell program implementing the hook logic - The Haskell hook program generates a Push JSON object and HTTP POSTs it to Vervis running on localhost - Vervis currently responds with an error, the next step is to implement the actual publishing of ForgeFed Push activities
2019-09-05 14:02:42 +02:00
Data.DList.Local
Minimal pagination for git and darcs change log
2016-05-13 10:49:19 +02:00
Data.Either.Local
Dedicated module for "time ago"
2016-05-03 03:20:23 +02:00
Data.EventTime.Local
Basic pagination for Vervis
2016-05-11 16:42:41 +02:00
Data.Functor.Local
Implement an 'initRepo' that actually works
2016-05-03 01:11:32 +02:00
Data.Git.Local
DAG tree view model builder, based on (V, E) and user choices
2016-08-04 01:09:42 +02:00
Data.Graph.DirectedAcyclic.View.Tree
DB graph cycle existence checking using recursive SQL query
2016-07-05 10:46:58 +02:00
Data.Graph.Inductive.Query.Cycle
Layering of intransitive DAGs
2016-06-21 00:50:16 +02:00
Data.Graph.Inductive.Query.Layer
Path existence checking between graph nodes
2016-07-05 14:37:31 +02:00
Data.Graph.Inductive.Query.Path
Transitive reduction of DAGs for FGL
2016-07-14 02:39:00 +02:00
Data.Graph.Inductive.Query.TransRed
Layering of intransitive DAGs
2016-06-21 00:50:16 +02:00
Data.HashMap.Lazy.Local
Basic TimeEvent support for 'hourglass', will need this for 'hit'
2016-05-06 01:05:56 +02:00
Data.Hourglass.Local
Generate and keep permanent salt for generating hashids for URIs
2019-02-08 22:54:22 +01:00
Data.Int.Local
Data.KeyFile
Add repo pages and repo creation form
2016-02-27 06:41:36 +01:00
Data.List.Local
Unfinished updated outbox handler
2019-04-11 15:44:44 +02:00
Data.List.NonEmpty.Local
Ticket content edit form lets you edit custom ticket params
2016-08-10 20:52:26 +02:00
Data.Maybe.Local
Syntax-highlight the pretty JSON display of AP objects
2019-06-09 16:32:57 +02:00
Data.MediaType
Initial incomplete pagination model
2016-05-10 13:05:56 +02:00
Data.Paginate.Local
Add GET routes and handlers for sharer-hosted patches
2020-05-24 11:17:49 +02:00
Data.Patch.Local
Refactor Git log view into separate modules and Widgets
2016-05-06 12:29:02 +02:00
Data.Text.UTF8.Local
Data.Text.Lazy.UTF8.Local
Darcs change log view
2016-05-08 16:28:03 +02:00
Data.Time.Clock.Local
Implement building discussion message tree from DB
2016-05-19 14:06:27 +02:00
Data.Tree.Local
New module structure for ActivityPub C2S and S2S code
2019-06-15 06:39:13 +02:00
Data.Tuple.Local
Start big route change, doesn't build yet I decided to add some safety to routes: - Use dedicated newtypes - Use CI for the CI-unique DB fields Since such a change requires so many changes in many source files, this is also a chance to do other such breaking changes. I'm recording the change gradually. It won't build until I finish, so for now don't waste time trying to build the app.
2016-05-23 14:24:14 +02:00
Database.Esqueleto.Local
Implement theater-based remote delivery and port personGrant
2023-05-25 00:17:14 +02:00
Database.Persist.Box
Database.Persist.Box.Internal
Database.Persist.Box.Via
PersistField instance for CI, i.e. case-insensitive DB fields
2016-05-22 23:43:59 +02:00
Database.Persist.Class.Local
Switch jsonb support from persistent-postgresql to a custom module The custom module provides a parametric wrapper, allowing any specific FromJSON/ToJSON instance to be used. It's a standalone module though, and not a wrapper of persistent-postgresql, because persistent-postgresql uses aeson Value and it prevents using toEncoding to get from the value directly to a string.
2019-03-23 16:29:50 +01:00
Database.Persist.JSON
Start big route change, doesn't build yet I decided to add some safety to routes: - Use dedicated newtypes - Use CI for the CI-unique DB fields Since such a change requires so many changes in many source files, this is also a chance to do other such breaking changes. I'm recording the change gradually. It won't build until I finish, so for now don't waste time trying to build the app.
2016-05-23 14:24:14 +02:00
Database.Persist.Sql.Local
Implement theater-based remote delivery and port personGrant
2023-05-25 00:17:14 +02:00
Database.Persist.Sqlite.Local
When POSTing an activity, protect remote actor DB insertion with withHostLock
2019-03-09 18:12:43 +01:00
Database.Persist.Local
PersistEntityGraph is for any graph, PersistEntityHierarchy for DAGs
2016-07-05 18:13:48 +02:00
Database.Persist.Local.Class.PersistEntityHierarchy
Forgot to record a file, darcs amend decided not to work
2016-06-13 15:48:31 +02:00
Database.Persist.Local.RecursionDoc
DB: Add media type field to 'Patch' entity This patch (haha) also adds a VCS field to the AP representation of repos
2020-08-14 23:16:33 +02:00
Development.PatchMediaType
Development.PatchMediaType.JSON
Development.PatchMediaType.Persist
Initial code for intransitive DAG drawing
2016-06-28 21:46:54 +02:00
Diagrams.IntransitiveDAG
Finish route change, it builds now I used this chance to make some name changes, add some utils, tweak some imports, remove more `setTitle`s and so on. I also made person, repo, key and project creation forms verify CI-uniqueness.
2016-05-23 22:46:54 +02:00
Formatting.CaseInsensitive
Complete DB migration list, allowing to upgrade 2016-08-04 running instance Until now the list of DB migration actions was incomplete, containing only changes made since I added the migration system itself. It now contains the 2016-08-04 model, and then every change made since then. IMPORTANT: The 2016-08-04 instance doesn't have a schema version entity at all, so it is assigned version 0, while the actual version of its schema is 1. I'm going to patch persistent-migration to allow it to be 1, making the migration path smooth.
2018-03-27 16:28:56 +02:00
Language.Haskell.TH.Quote.Local
New datatype `FedURI` for @id URIs Using a dedicated type allows to record in the type the guarantees that we provide, such as scheme being HTTPS and authority being present. Allows to replace ugly `fromJust` and such with direct field access.
2019-02-08 00:08:28 +01:00
Network.FedURI
Federation test outbox page with form for entering JSON
2019-01-21 16:54:57 +01:00
Network.HTTP.Client.Conduit.ActivityPub
When POSTing activities, set a Digest header using SHA-256
2019-04-25 17:49:15 +02:00
Network.HTTP.Digest
Implement DB-based SSH authentication
2016-03-06 12:58:48 +01:00
Network.SSH.Local
C2S: Implement applyC (apply a patch/MR to a repo/branch) Both Git and Darcs are supported - Darcs implementation applies right on the bare repo, I haven't tested to make sure it works right (federated MR demo is going to be only for Git) - Git implementation clones to temporary repo, runs `git am` on it to apply, then pushes to the real bare repo (because `git am` doesn't work on bare repos; I haven't tested yet to see how it handles conflicts; cloning and pushing should be efficient since the refs are just hardlinked rather than copied)
2022-09-24 11:04:10 +02:00
System.Process.Typed.Local
Finish route change, it builds now I used this chance to make some name changes, add some utils, tweak some imports, remove more `setTitle`s and so on. I also made person, repo, key and project creation forms verify CI-uniqueness.
2016-05-23 22:46:54 +02:00
Text.Blaze.Local
Add simple Display class for showing-as-strict-Text
2016-06-03 11:12:33 +02:00
Text.Display
Treat email address as `EmailAddress` instead of `Text` including in the mailer
2018-03-06 03:26:27 +01:00
Text.Email.Local
Use Pandoc for document rendering, for now just Markdown
2016-04-17 19:55:23 +02:00
Text.FilePath.Local
Refactor Git log view into separate modules and Widgets
2016-05-06 12:29:02 +02:00
Text.Jasmine.Local
Define HMAC based access token and switch CapSignKey from Ed25519 to HMAC
2019-03-09 22:21:36 +01:00
Web.ActivityAccess
Federation test outbox page with form for entering JSON
2019-01-21 16:54:57 +01:00
Web.ActivityPub
Implement actor-model system and start moving Person actor to it This patch makes Vervis temporarily unusable, because all actors' inbox POST handlers use the new system, but the actual federation handler code hasn't been ported. The next patches will port all the S2S activities supported so far, as well as C2S.
2023-04-29 12:40:44 +02:00
Web.Actor
Implement theater-based remote delivery and port personGrant
2023-05-25 00:17:14 +02:00
Web.Actor.Deliver
Implement actor-model system and start moving Person actor to it This patch makes Vervis temporarily unusable, because all actors' inbox POST handlers use the new system, but the actual federation handler code hasn't been ported. The next patches will port all the S2S activities supported so far, as well as C2S.
2023-04-29 12:40:44 +02:00
Web.Actor.Persist
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
-- Web.Capability
C2S: offerTicketC re-enabled and supporting looms and remote origin repo What's missing: - Match patch VCS, origin repo VCS and target repo VCS - Hook into postPersonInboxR - If only origin is provided, generate patches / otherwise somehow remember the commits proposed
2022-09-21 14:50:26 +02:00
Web.Text
Generate and keep permanent salt for generating hashids for URIs
2019-02-08 22:54:22 +01:00
Web.Hashids.Local
Start big route change, doesn't build yet I decided to add some safety to routes: - Use dedicated newtypes - Use CI for the CI-unique DB fields Since such a change requires so many changes in many source files, this is also a chance to do other such breaking changes. I'm recording the change gradually. It won't build until I finish, so for now don't waste time trying to build the app.
2016-05-23 14:24:14 +02:00
Web.PathPieces.Local
New module Yesod.ActivityPub, use it in Vervis.Federation for delivery POSTing
2019-04-26 05:23:49 +02:00
Yesod.ActivityPub
Implement actor-model system and start moving Person actor to it This patch makes Vervis temporarily unusable, because all actors' inbox POST handlers use the new system, but the actual federation handler code hasn't been ported. The next patches will port all the S2S activities supported so far, as well as C2S.
2023-04-29 12:40:44 +02:00
Yesod.Actor
Write unverified login user functions
2018-03-17 18:30:46 +01:00
Yesod.Auth.Unverified
Unverified variants of setCreds and clearCreds
2018-03-17 23:16:02 +01:00
Yesod.Auth.Unverified.Creds
Yesod.Auth.Unverified.Internal
New module Yesod.FedURI: Render routes into FedURI and LocalURI
2019-03-20 11:08:36 +01:00
Yesod.FedURI
C2S & UI: Allow creation of a new Repo
2022-09-16 12:34:44 +02:00
Yesod.Form.Local
More type-safe handling of DB key Hashids
2019-03-29 04:25:32 +01:00
Yesod.Hashids
Run the delivery worker priodically, settings control how often to run
2019-04-18 12:38:01 +02:00
Yesod.MonadSite
Use HTTPS for avatar URL if approot in settings is https://
2018-03-06 01:55:52 +01:00
Yesod.Paginate.Local
Add route getMessageR, returns an Activity Note for any locally created Message
2019-03-22 21:46:42 +01:00
Yesod.Persist.Local
Syntax-highlight the pretty JSON display of AP objects
2019-06-09 16:32:57 +02:00
Yesod.RenderSource
Write unverified login user functions
2018-03-17 18:30:46 +01:00
Yesod.SessionEntity
Initial incomplete pagination model
2016-05-10 13:05:56 +02:00
Determine operation access in Vervis.Access, reuse it everywhere it's needed
2019-01-26 23:22:49 +01:00
Vervis.Access
New module structure for ActivityPub C2S and S2S code
2019-06-15 06:39:13 +02:00
Vervis.ActivityPub
Implement actor-model system and start moving Person actor to it This patch makes Vervis temporarily unusable, because all actors' inbox POST handlers use the new system, but the actual federation handler code hasn't been ported. The next patches will port all the S2S activities supported so far, as well as C2S.
2023-04-29 12:40:44 +02:00
Vervis.Actor
Implement theater-based remote delivery and port personGrant
2023-05-25 00:17:14 +02:00
Vervis.Actor2
Deck: Port/write Accept, Reject, Follow, Undo
2023-06-07 09:15:30 +02:00
Vervis.Actor.Common
Implement actor-model system and start moving Person actor to it This patch makes Vervis temporarily unusable, because all actors' inbox POST handlers use the new system, but the actual federation handler code hasn't been ported. The next patches will port all the S2S activities supported so far, as well as C2S.
2023-04-29 12:40:44 +02:00
Vervis.Actor.Deck
Vervis.Actor.Group
Vervis.Actor.Loom
Vervis.Actor.Person
Actor system: Add support for C2S actor methods
2023-06-15 19:23:50 +02:00
Vervis.Actor.Person.Client
Project routes, handlers and creation UI
2023-06-26 21:02:54 +02:00
Vervis.Actor.Project
Implement actor-model system and start moving Person actor to it This patch makes Vervis temporarily unusable, because all actors' inbox POST handlers use the new system, but the actual federation handler code hasn't been ported. The next patches will port all the S2S activities supported so far, as well as C2S.
2023-04-29 12:40:44 +02:00
Vervis.Actor.Repo
New module structure for ActivityPub C2S and S2S code
2019-06-15 06:39:13 +02:00
Vervis.API
Libravatar support \o/
2016-05-25 23:10:41 +02:00
Vervis.Avatar
Binary request body decoder
2016-04-24 20:48:07 +02:00
Vervis.BinaryBody
Explore friendly rendering of event time
2016-05-06 00:20:11 +02:00
Vervis.Changes
Atom and RSS feeds for repo history
2018-04-01 00:04:33 +02:00
Vervis.ChangeFeed
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
--Vervis.Class.Actor
Client, UI: Form for creating a new Deck
2022-08-16 15:17:26 +02:00
Vervis.Client
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
Vervis.Cloth
Define colors for use with 'diagrams'
2016-06-26 10:03:18 +02:00
Vervis.Colour
Smart HTTP ref discovery
2016-04-22 21:46:46 +02:00
Vervis.Content
Refactor git source view code and implement the same for Darcs
2016-05-05 09:29:19 +02:00
Vervis.Darcs
S2S: Switch from Grant->Accept->Enable to Invite->Accept->Grant Giving access now starts with an Invite activity, followed by Accept from the Invite's recipient. Finally, the resource sends a Grant, which is the actual OCap.
2022-09-05 18:19:52 +02:00
S2S: Implement preparation and generic steps in person inbox post handler The steps are: - Parse activity ID and match with the authenticated sender - For local activity (we got via forwarding), find in DB - For remote activity, cache in DB - Insert activity to recipient's inbox What's not there yet is the actual logic of handling specific activities.
2022-08-31 15:01:04 +02:00
Vervis.Data.Actor
Vervis.Data.Collab
C2S, S2S: Re-enable createNoteC and personCreateNoteF
2022-10-16 13:26:24 +02:00
Vervis.Data.Discussion
C2S: Re-implement and enable resolveC, followC, undoC
2022-10-25 06:54:56 +02:00
Vervis.Data.Follow
C2S: offerTicketC re-enabled and supporting looms and remote origin repo What's missing: - Match patch VCS, origin repo VCS and target repo VCS - Hook into postPersonInboxR - If only origin is provided, generate patches / otherwise somehow remember the commits proposed
2022-09-21 14:50:26 +02:00
Vervis.Data.Ticket
S2S: Switch from Grant->Accept->Enable to Invite->Accept->Grant Giving access now starts with an Invite activity, followed by Accept from the Invite's recipient. Finally, the resource sends a Grant, which is the actual OCap.
2022-09-05 18:19:52 +02:00
S2S: Prepare inbox handlers for Repo, Deck and Loom
2022-09-06 12:52:14 +02:00
--Vervis.Federation
Refactor the types used in activity authentication and handle project recipient - The data returned from activity authentication has nicer types now, and no mess of big tuples. - Activity authentication code has its own module now, Vervis.Federation.Auth. - The sharer inbox handler can now handle and store activities by a local project actor, forwarded from a remote actor. This isn't in use right now, but once projects start publishing Accept activities, or other things, it may be needed.
2019-06-16 23:39:50 +02:00
Vervis.Federation.Auth
S2S: Invite->Accept->Grant (for Repo, Deck, Loom and Person, not for Group) Person inbox handler: - Invite: Parse and insert to inbox - Grant: Parse and insert to inbox Repo/Deck/Loom inbox handler: - Invite: Parse and remember as Collab record in DB for later - Accept: Send a Grant (and remember it in DB) Along with inviteC and acceptC, the Invite->Accept->Grant flow is now fully federated, yay! What's missing is UI for actually using it. Coming soon.
2022-09-08 14:00:14 +02:00
Vervis.Federation.Collab
C2S, S2S: Re-enable createNoteC and personCreateNoteF
2022-10-16 13:26:24 +02:00
Vervis.Federation.Discussion
S2S: Re-implement and re-enable personFollowF
2022-10-25 20:02:06 +02:00
Vervis.Federation.Offer
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
--Vervis.Federation.Push
S2S: deckOfferTicketF (i.e. local deck receives ticket from remote author)
2022-09-23 17:58:54 +02:00
Vervis.Federation.Ticket
Prepare for ticket dependency federation To be honest, this is a huge patch that changes tons of stuff and probably should have been broken up into small changes. But I already had the codebase not building, so... just did all of this at once :P Basically this patch does the following: - DB migrations for ticket dependency related tables, e.g. allowing a remote author and a remote child - Allowing S2S handlers to provide an async continued processing function, which is executed and the result then added to the debug page - Most UI and functionality related to ticket deps is disabled, new implementation being added gradually via ActivityPub - Improvements to AP tools, e.g. allow to specify multiple hosts for approved forwarding when sending out an activity, and allow to specify audience of software-authored activities using a convenient human-friendly structure - Implementation of S2S sharerOfferDepF which creates a dependency under a sharer-hosted ticket/patch and sends back an Accept
2020-06-18 12:38:04 +02:00
Vervis.Federation.Util
New Network.FedURI with separate URI modes for dev and for fediverse FedURIs, until now, have been requiring HTTPS, and no port number, and DNS internet domain names. This works just fine on the forge fediverse, but it makes local dev builds much less useful. This patch introduces URI types that have a type tag specifying one of 2 modes: - `Dev`: Works with URIs like `http://localhost:3000/s/fr33` - `Fed`: Works with URIs like `https://dev.community/s/fr33` This should allow even to run multiple federating instances for development, without needing TLS or reverse proxies or editing the hosts files or anything like that.
2019-07-23 15:59:48 +02:00
Vervis.FedURI
S2S: loomOfferTicketF, open MR sent by remote author
2022-09-23 17:59:21 +02:00
Vervis.Fetch
UI: Tweak and re-enable UI for uploading personal SSH keys
2022-09-26 14:51:06 +02:00
Vervis.Field.Key
Write initial overview content and add project creation form
2016-02-25 04:10:30 +01:00
Vervis.Field.Person
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
--Vervis.Field.Project
--Vervis.Field.Repo
--Vervis.Field.Role
--Vervis.Field.Sharer
--Vervis.Field.Ticket
-- Vervis.Field.Workflow
Implement reply-to-existing-comment
2016-05-20 00:07:25 +02:00
Vervis.Form.Discussion
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
--Vervis.Form.Group
UI: Tweak and re-enable UI for uploading personal SSH keys
2022-09-26 14:51:06 +02:00
Vervis.Form.Key
C2S & UI: Allow creation of a new Repo
2022-09-16 12:34:44 +02:00
Vervis.Form.Repo
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
--Vervis.Form.Role
UI: Fix and re-enable deck ticket list view
2022-09-17 12:14:27 +02:00
Vervis.Form.Ticket
UI: New ticket/MR creation form + deck/loom navigation links
2022-10-17 17:08:00 +02:00
Vervis.Form.Tracker
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
-- Vervis.Form.Workflow
Finish route change, it builds now I used this chance to make some name changes, add some utils, tweak some imports, remove more `setTitle`s and so on. I also made person, repo, key and project creation forms verify CI-uniqueness.
2016-05-23 22:46:54 +02:00
Vervis.Formatting
Put all modules under a new Vervis module
2016-02-23 09:45:03 +01:00
Vervis.Foundation
Vervis.Git
Ticket dependency add/remove and some fixes to recursive SQL
2016-07-28 18:40:10 +02:00
Vervis.GraphProxy
Implement remote following, disable automatic following This patch contains migrations that require that there are no follow records. If you have any, the migration will (hopefully) fail and you'll need to manually delete any follow records you have. In the next patch I'll try to add automatic following on the pseudo-client side by running both e.g. createNoteC and followC in the same POST request handler.
2019-09-25 12:43:05 +02:00
Vervis.Handler.Client
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
Vervis.Handler.Cloth
Put all modules under a new Vervis module
2016-02-23 09:45:03 +01:00
Vervis.Handler.Common
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
Vervis.Handler.Deck
-- Vervis.Handler.Git
Add group routes
2016-05-24 23:48:21 +02:00
Vervis.Handler.Group
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
--Vervis.Handler.Inbox
UI: Tweak and re-enable UI for uploading personal SSH keys
2022-09-26 14:51:06 +02:00
Vervis.Handler.Key
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
Vervis.Handler.Loom
Put all modules under a new Vervis module
2016-02-23 09:45:03 +01:00
Vervis.Handler.Person
Add repo pages and repo creation form
2016-02-27 06:41:36 +01:00
Vervis.Handler.Repo
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
--Vervis.Handler.Role
Project routes, handlers and creation UI
2023-06-26 21:02:54 +02:00
Vervis.Handler.Project
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
--Vervis.Handler.Sharer
New ticket post form
2016-05-01 00:32:22 +02:00
Vervis.Handler.Ticket
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
-- Vervis.Handler.Wiki
-- Vervis.Handler.Workflow
Add utility for loading permanent key files, and use it for ocap signing key
2019-02-08 04:13:56 +01:00
Vervis.KeyFile
Use the new migration system in place of persistent's one
2016-08-31 18:51:02 +02:00
Vervis.Migration
DB: Move new entity declarations to a new module Vervis.Migration.Entities
2022-10-19 11:06:38 +02:00
Vervis.Migration.Entities
Complete DB migration list, allowing to upgrade 2016-08-04 running instance Until now the list of DB migration actions was incomplete, containing only changes made since I added the migration system itself. It now contains the 2016-08-04 model, and then every change made since then. IMPORTANT: The 2016-08-04 instance doesn't have a schema version entity at all, so it is assigned version 0, while the actual version of its schema is 1. I'm going to patch persistent-migration to allow it to be 1, making the migration path smooth.
2018-03-27 16:28:56 +02:00
Vervis.Migration.Model
Vervis.Migration.TH
Refactor git source view code and implement the same for Darcs
2016-05-05 09:29:19 +02:00
Vervis.Model
Experimental typeclass for ident+name model entities
2016-08-08 21:17:25 +02:00
Vervis.Model.Entity
Add group roles and make a group's creator its admin
2016-05-25 17:52:15 +02:00
Vervis.Model.Group
Start big route change, doesn't build yet I decided to add some safety to routes: - Use dedicated newtypes - Use CI for the CI-unique DB fields Since such a change requires so many changes in many source files, this is also a chance to do other such breaking changes. I'm recording the change gradually. It won't build until I finish, so for now don't waste time trying to build the app.
2016-05-23 14:24:14 +02:00
Vervis.Model.Ident
Initial minimal limited per-repo RBAC system
2016-05-29 15:17:55 +02:00
Vervis.Model.Role
Turn boolean ticketDone into TicketStatus enum
2016-08-11 02:44:11 +02:00
Vervis.Model.Ticket
Complete DB migration list, allowing to upgrade 2016-08-04 running instance Until now the list of DB migration actions was incomplete, containing only changes made since I added the migration system itself. It now contains the 2016-08-04 model, and then every change made since then. IMPORTANT: The 2016-08-04 instance doesn't have a schema version entity at all, so it is assigned version 0, while the actual version of its schema is 1. I'm going to patch persistent-migration to allow it to be 1, making the migration path smooth.
2018-03-27 16:28:56 +02:00
Vervis.Model.TH
Per-workflow custom ticket fields
2016-08-08 16:01:06 +02:00
Vervis.Model.Workflow
Basic pagination for Vervis
2016-05-11 16:42:41 +02:00
Vervis.Paginate
Define colors in dedicated Vervis.Palette module
2016-06-22 22:58:42 +02:00
Vervis.Palette
Add GET routes and handlers for sharer-hosted patches
2020-05-24 11:17:49 +02:00
Vervis.Path
S2S: Switch from Grant->Accept->Enable to Invite->Accept->Grant Giving access now starts with an Invite activity, followed by Accept from the Invite's recipient. Finally, the resource sends a Grant, which is the actual OCap.
2022-09-05 18:19:52 +02:00
Vervis.Persist.Actor
S2S: Invite->Accept->Grant (for Repo, Deck, Loom and Person, not for Group) Person inbox handler: - Invite: Parse and insert to inbox - Grant: Parse and insert to inbox Repo/Deck/Loom inbox handler: - Invite: Parse and remember as Collab record in DB for later - Accept: Send a Grant (and remember it in DB) Along with inviteC and acceptC, the Invite->Accept->Grant flow is now fully federated, yay! What's missing is UI for actually using it. Coming soon.
2022-09-08 14:00:14 +02:00
Vervis.Persist.Collab
C2S, S2S: Re-enable createNoteC and personCreateNoteF
2022-10-16 13:26:24 +02:00
Vervis.Persist.Discussion
C2S: Re-implement and enable resolveC, followC, undoC
2022-10-25 06:54:56 +02:00
Vervis.Persist.Follow
S2S: Implement loomApplyF (remote person asking to apply bundle on local loom)
2022-09-24 17:46:02 +02:00
Vervis.Persist.Ticket
S2S: Switch from Grant->Accept->Enable to Invite->Accept->Grant Giving access now starts with an Invite activity, followed by Accept from the Invite's recipient. Finally, the resource sends a Grant, which is the actual OCap.
2022-09-05 18:19:52 +02:00
Refactor git source view code and implement the same for Darcs
2016-05-05 09:29:19 +02:00
Vervis.Readme
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
Vervis.Recipient
Move remote actor DB code from Foundation to separate module
2019-03-09 16:40:02 +01:00
Vervis.RemoteActorStore
Deck: Port Invite handler
2023-06-08 14:38:09 +02:00
Vervis.RemoteActorStore.Types
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
--Vervis.Repo
Use HTTPS for avatar URL if approot in settings is https://
2018-03-06 01:55:52 +01:00
Vervis.Secure
Refactor git source view code and implement the same for Darcs
2016-05-05 09:29:19 +02:00
Vervis.Settings
Vervis.Settings.StaticFiles
Mechanism for reporting git pushes to Vervis via post-receive hooks Here's how it works: - When Vervis starts, it writes a config file and it writes post-receive hooks into all the repos it manages - When a git push is accepted, git runs the post-receive hook, which is a trivial shell script that executes the actual Haskell program implementing the hook logic - The Haskell hook program generates a Push JSON object and HTTP POSTs it to Vervis running on localhost - Vervis currently responds with an error, the next step is to implement the actual publishing of ForgeFed Push activities
2019-09-05 14:02:42 +02:00
Vervis.Settings.TH
Refactor git source view code and implement the same for Darcs
2016-05-05 09:29:19 +02:00
Vervis.SourceTree
Implement DB-based SSH authentication
2016-03-06 12:58:48 +01:00
Vervis.Ssh
Put all modules under a new Vervis module
2016-02-23 09:45:03 +01:00
Vervis.Style
Ticket tree view page
2016-08-04 09:36:24 +02:00
Vervis.Ticket
Ticket filtering
2016-05-22 16:31:56 +02:00
Vervis.TicketFilter
Show creation date in group page
2016-05-25 09:50:10 +02:00
Vervis.Time
S2S: Prepare inbox handlers for Repo, Deck and Loom
2022-09-06 12:52:14 +02:00
Vervis.Web.Actor
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 09:51:42 +01:00
Vervis.Web.Collab
UI: Fix and re-enable getRepoCommitR
2022-09-16 13:41:58 +02:00
Vervis.Web.Darcs
Improve the AP async HTTP delivery API and per-actor key support New iteration of the ActivityPub delivery implementation and interface. Advantages over previous interface: * When sending a ByteString body, the sender is explicitly passed as a parameter instead of JSON-parsing it out of the ByteString * Clear 3 operations provided: Send, Resend and Forward * Support for per-actor keys * Actor-type-specific functions (e.g. deliverRemoteDB_D) removed * Only the most high-level API is exposed to Activity handler code, making handler code more concise and clear Also added in this patch: * Foundation for per-actor key support * 1 key per actor allowed in DB * Disabled C2S and S2S handlers now un-exported for clarity * Audience and capability parsing automatically done for all C2S handlers * Audience and activity composition automatically done for Vervis.Client builder functions Caveats: * Actor documents still don't link to their per-actor keys; that should be the last piece to complete per-actor key support * No moderation and anti-spam tools yet * Delivery API doesn't yet have good integration of persistence layer, e.g. activity is separately encoded into bytestring for DB and for HTTP; this will be improved in the next iteration * Periodic delivery now done in 3 separate steps, running sequentially; it simplifies the code, but may be changed for efficiency/robustness in the next iterations * Periodic delivery collects per-actor keys in a 1-DB-transaction-for-each-delivery fashion, rather than grabbing them in the big Esqueleto query (or keeping the signed output in the DB; this isn't done currently to allow for smooth actor key renewal) * No support yet in the API for delivery where the actor key has already been fetched, rather than doing a DB transaction to grab it; such support would be just an optimization, so it's low-priority, but will be added in later iterations
2022-10-12 18:50:11 +02:00
Vervis.Web.Delivery
UI: Re-enable ticket page, some pieces still missing, mostly buttons
2022-09-17 19:42:04 +02:00
Vervis.Web.Discussion
UI: Fix and re-enable getRepoCommitR
2022-09-16 13:41:58 +02:00
Vervis.Web.Git
Vervis.Web.Repo
S2S: Prepare inbox handlers for Repo, Deck and Loom
2022-09-06 12:52:14 +02:00
Breadcrumbs widget in default layout
2016-05-02 16:16:51 +02:00
Vervis.Widget
Dummy discussion widget
2016-05-18 12:10:07 +02:00
Vervis.Widget.Discussion
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
Vervis.Widget.Person
Refactor Git log view into separate modules and Widgets
2016-05-06 12:29:02 +02:00
Vervis.Widget.Repo
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
--Vervis.Widget.Role
UI: Fix and re-enable deck ticket list view
2022-09-17 12:14:27 +02:00
Vervis.Widget.Ticket
UI: New ticket/MR creation form + deck/loom navigation links
2022-10-17 17:08:00 +02:00
Vervis.Widget.Tracker
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
-- Vervis.Widget.Workflow
-- Vervis.Wiki
C2S: Re-implement and enable resolveC, followC, undoC
2022-10-25 06:54:56 +02:00
--Vervis.WorkItem
Expose only required modules of vervis:library in vervis.cabal Only Vervis.Hook (for the hook programs) and Vervis.Application (for the web app program itself) are exposed now. I suppose more will be needed for tests. But now there's a clear distinction what's used by other components and what isn't.
2022-09-01 11:34:25 +02:00
Bring Yesod scaffolding
2016-02-13 04:35:30 +01:00
default-extensions: TemplateHaskell
QuasiQuotes
OverloadedStrings
MultiParamTypeClasses
TypeFamilies
GADTs
GeneralizedNewtypeDeriving
FlexibleContexts
FlexibleInstances
EmptyDataDecls
NoMonomorphismRestriction
DeriveDataTypeable
ViewPatterns
TupleSections
RecordWildCards
C2S: offerTicketC re-enabled and supporting looms and remote origin repo What's missing: - Match patch VCS, origin repo VCS and target repo VCS - Hook into postPersonInboxR - If only origin is provided, generate patches / otherwise somehow remember the commits proposed
2022-09-21 14:50:26 +02:00
LambdaCase
Expose only required modules of vervis:library in vervis.cabal Only Vervis.Hook (for the hook programs) and Vervis.Application (for the web app program itself) are exposed now. I suppose more will be needed for tests. But now there's a clear distinction what's used by other components and what isn't.
2022-09-01 11:34:25 +02:00
Rely on stack for dep versions and upgrade to LTS 5.5
2016-03-07 02:12:55 +01:00
build-depends: aeson
ActivityPub inbox test page This patch includes some ugliness and commented out code. Sorry for that. I'll clean it up soon. Basically there's a TVar holding a Vector of at most 10 AP activities. You can freely POST stuff to /inbox, and then GET /inbox and see what you posted, or an error description saying why your activity was rejected.
2019-01-19 02:44:21 +01:00
-- For activity JSOn display in /inbox test page
, aeson-pretty
Implement actor-model system and start moving Person actor to it This patch makes Vervis temporarily unusable, because all actors' inbox POST handlers use the new system, but the actual federation handler code hasn't been ported. The next patches will port all the S2S activities supported so far, as well as C2S.
2023-04-29 12:40:44 +02:00
-- For rethrowing in Control.Concurrent.Actor
, annotated-exception
HTTP Signature verification: RSA-SHA256 and PEM/ASN1 support Before, things worked like this: * Only signatures of Ed25519 keys could be verified * Key encoding placed the plain binary Ed25519 key in the PEM, instead of the key's ASN1 encoding With this patch it now works like this: * Ed25519 signatures are supported as before * RSA keys are now supported too, assuming RSA-SHA256 signatures * Both Ed25519 and RSA keys are encoded and decoded using actual PEM with ASN1
2019-03-11 00:15:42 +01:00
-- for encoding and decoding of crypto public keys
, asn1-encoding
, asn1-types
Darcs change log view
2016-05-08 16:28:03 +02:00
-- for parsing commands sent over SSH and Darcs patch
-- metadata
Parse the git-uploac-pack SSH command properly
2016-04-19 11:42:02 +02:00
, attoparsec
Switch to new actor layout This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
2022-08-15 15:57:42 +02:00
-- For LocalActorBy and LocalStageBy
, barbies
Rely on stack for dep versions and upgrade to LTS 5.5
2016-03-07 02:12:55 +01:00
, base
Darcs change log view
2016-05-08 16:28:03 +02:00
-- for hex display of Darcs patch hashes
, base16-bytestring
Generate FEP-8b32 authenticity proofs when delivering activities Limitations: - Verification of proofs not implemeneted yet, just generation. Verification probably coming in the next commit. - Only jcs-eddsa-2022 is supported. Can add more cryptosuites once they're updated for the requirements of the VC Data Integrity spec. - Bug: The proofs aren't stored in the DB versions of outgoing activities, i.e. HTTP GETing an activity won't include the proof. Probably not urgent to fix. Ideally, change the whole PersistJSONObject/Envelope/etc. thing to allow to serialize the activity exactly once.
2023-05-30 08:48:21 +02:00
, base58-bytestring
Refactor git source view code and implement the same for Darcs
2016-05-05 09:29:19 +02:00
, base64-bytestring
Incremental binary stream decoder, generalized from hit-network
2016-04-24 20:25:30 +02:00
-- for Data.Binary.Local
, binary
Add UI for display of SSH keys
2016-03-07 01:42:06 +01:00
, blaze-html
Refactor Git log view into separate modules and Widgets
2016-05-06 12:29:02 +02:00
-- for Data.EventTime.Local
, blaze-markup
Display repo files in repo page instead of history log
2016-04-12 00:13:32 +02:00
, byteable
Rely on stack for dep versions and upgrade to LTS 5.5
2016-03-07 02:12:55 +01:00
, bytestring
Darcs inventory parser: Add hash types and parse previous inventory
2016-05-16 16:02:43 +02:00
-- for Darcs.Local.PatchInfo.Parser
, bytestring-lexing
Make initial homepage with table and simple login
2016-02-16 12:41:13 +01:00
, case-insensitive
Implement theater-based remote delivery and port personGrant
2023-05-25 00:17:14 +02:00
-- For slab/box/citron serialization
, cereal
Define colors for use with 'diagrams'
2016-06-26 10:03:18 +02:00
-- for defining colors for use with diagrams
, colour
Rely on stack for dep versions and upgrade to LTS 5.5
2016-03-07 02:12:55 +01:00
, conduit
Federation test outbox page with form for entering JSON
2019-01-21 16:54:57 +01:00
-- For httpAPEither
, conduit-extra
Make initial homepage with table and simple login
2016-02-16 12:41:13 +01:00
, containers
Darcs change log view
2016-05-08 16:28:03 +02:00
, cryptonite
Refactor git source view code and implement the same for Darcs
2016-05-05 09:29:19 +02:00
-- for Storage.Hashed because hashed-storage seems
-- unmaintained and darcs has its own copy
, darcs
Adapt to darcs-lights and changes in darcs-rev
2018-05-24 23:45:01 +02:00
, darcs-lights
Make initial homepage with table and simple login
2016-02-16 12:41:13 +01:00
, data-default
Initial incomplete pagination model
2016-05-10 13:05:56 +02:00
, data-default-class
Fix DB migrations and use the validating addEntities
2018-04-05 02:04:39 +02:00
, data-default-instances-bytestring
Unfinished updated outbox handler
2019-04-11 15:44:44 +02:00
, data-ordlist
Initial code for intransitive DAG drawing
2016-06-28 21:46:54 +02:00
-- for drawing DAGs: RBAC role inheritance, etc.
Upgrade LTS from 5.13 to 6.5
2016-07-02 10:51:29 +02:00
, diagrams-core
, diagrams-lib
, diagrams-svg
Rely on stack for dep versions and upgrade to LTS 5.5
2016-03-07 02:12:55 +01:00
, directory
Implement an 'initRepo' that actually works
2016-05-03 01:11:32 +02:00
-- for Data.Git.Local
, directory-tree
Implement topsort for commits and apply to graph
2016-03-01 23:16:01 +01:00
, dlist
Add OAuth2 tables to database, and run their migrations
2020-03-28 15:18:00 +01:00
, dvara
Treat email address as `EmailAddress` instead of `Text` including in the mailer
2018-03-06 03:26:27 +01:00
, email-validate
Mechanism for reporting git pushes to Vervis via post-receive hooks Here's how it works: - When Vervis starts, it writes a config file and it writes post-receive hooks into all the repos it manages - When a git push is accepted, git runs the post-receive hook, which is a trivial shell script that executes the actual Haskell program implementing the hook logic - The Haskell hook program generates a Push JSON object and HTTP POSTs it to Vervis running on localhost - Vervis currently responds with an error, the next step is to implement the actual publishing of ForgeFed Push activities
2019-09-05 14:02:42 +02:00
, email-validate-json
Make initial homepage with table and simple login
2016-02-16 12:41:13 +01:00
, esqueleto
Upgrade to GHC 8 and LTS 10.10
2018-05-16 02:02:54 +02:00
, exceptions
Rely on stack for dep versions and upgrade to LTS 5.5
2016-03-07 02:12:55 +01:00
, fast-logger
Implement building discussion message tree from DB
2016-05-19 14:06:27 +02:00
-- for building a message tree using DFS in
-- Vervis.Discussion, possibly also used by some git
-- graph related code?
Implement flexible Kahn topsort for use on git commit graphs
2016-02-29 02:59:33 +01:00
, fgl
Bring Yesod scaffolding
2016-02-13 04:35:30 +01:00
, file-embed
Add repo pages and repo creation form
2016-02-27 06:41:36 +01:00
, filepath
Render README below repo tree view when present
2016-04-13 18:17:34 +02:00
, formatting
Implement loading a commit graph
2016-02-29 22:42:37 +01:00
, hashable
Generate and keep permanent salt for generating hashids for URIs
2019-02-08 22:54:22 +01:00
, hashids
Implement an 'initRepo' that actually works
2016-05-03 01:11:32 +02:00
-- for source file highlighting
Syntax highlighting suppport, but no colors in CSS yet
2016-04-12 13:21:14 +02:00
, highlighter2
Federation test outbox page with form for entering JSON
2019-01-21 16:54:57 +01:00
, http-client-signature
C2S: offerTicketC re-enabled and supporting looms and remote origin repo What's missing: - Match patch VCS, origin repo VCS and target repo VCS - Hook into postPersonInboxR - If only origin is provided, generate patches / otherwise somehow remember the commits proposed
2022-09-21 14:50:26 +02:00
, html-entities
ActivityPub inbox test page This patch includes some ugliness and commented out code. Sorry for that. I'll clean it up soon. Basically there's a TVar holding a Vector of at most 10 AP activities. You can freely POST stuff to /inbox, and then GET /inbox and see what you posted, or an error description saying why your activity was rejected.
2019-01-19 02:44:21 +01:00
, http-signature
Upgrade to GHC 8.4 and LTS 12
2018-12-05 04:41:19 +01:00
, git
Update docs for darcs->git switch, and switch from darcs-rev to gitrev
2023-05-25 12:54:03 +02:00
, gitrev
Upgrade to GHC 8.4 and LTS 12
2018-12-05 04:41:19 +01:00
, hit-graph
, hit-harder
, hit-network
Refactor Git log view into separate modules and Widgets
2016-05-06 12:29:02 +02:00
-- currently discarding all JS so no need for minifier
--, hjsmin
Upgrade to GHC 8.4 and LTS 12
2018-12-05 04:41:19 +01:00
-- 'git' uses it for 'GitTime'
Make initial homepage with table and simple login
2016-02-16 12:41:13 +01:00
, hourglass
Periodically rotated AP actor key for signing ActivityPub requests The actor key will be used for all actors on the server. It's held in a `TVar` so that it can always be safely updated and safely retrieved (technically there is a single writer so IORef and MVar could work, but they require extra care while TVar is by design suited for this sort of thing).
2019-01-14 23:08:44 +01:00
, yesod-http-signature
ActivityPub inbox test page This patch includes some ugliness and commented out code. Sorry for that. I'll clean it up soon. Basically there's a TVar holding a Vector of at most 10 AP activities. You can freely POST stuff to /inbox, and then GET /inbox and see what you posted, or an error description saying why your activity was rejected.
2019-01-19 02:44:21 +01:00
, http-client
, http-client-tls
, http-conduit
Stop using classy-prelude-yesod
2016-02-29 15:04:23 +01:00
, http-types
Libravatar support \o/
2016-05-25 23:10:41 +02:00
, libravatar
Darcs change log view
2016-05-08 16:28:03 +02:00
, memory
Add email sending capability to Vervis
2018-02-25 10:28:55 +01:00
, mime-mail
Rely on stack for dep versions and upgrade to LTS 5.5
2016-03-07 02:12:55 +01:00
, monad-control
, monad-logger
Recursive SQL queries, still need to test before use
2016-06-13 00:37:52 +02:00
-- for Database.Persist.Local
, mtl
Add email sending capability to Vervis
2018-02-25 10:28:55 +01:00
, network
ActivityPub inbox test page This patch includes some ugliness and commented out code. Sorry for that. I'll clean it up soon. Basically there's a TVar holding a Vector of at most 10 AP activities. You can freely POST stuff to /inbox, and then GET /inbox and see what you posted, or an error description saying why your activity was rejected.
2019-01-19 02:44:21 +01:00
, network-uri
Deck: Port/write Accept, Reject, Follow, Undo
2023-06-07 09:15:30 +02:00
, optics-core
Use Pandoc for document rendering, for now just Markdown
2016-04-17 19:55:23 +02:00
, pandoc
, pandoc-types
Start big route change, doesn't build yet I decided to add some safety to routes: - Use dedicated newtypes - Use CI for the CI-unique DB fields Since such a change requires so many changes in many source files, this is also a chance to do other such breaking changes. I'm recording the change gradually. It won't build until I finish, so for now don't waste time trying to build the app.
2016-05-23 14:24:14 +02:00
-- for PathPiece instance for CI, Web.PathPieces.Local
, path-pieces
Generate commit diff data for git repos
2018-05-19 18:10:03 +02:00
, patience
Periodically rotated AP actor key for signing ActivityPub requests The actor key will be used for all actors on the server. It's held in a `TVar` so that it can always be safely updated and safely retrieved (technically there is a single writer so IORef and MVar could work, but they require extra care while TVar is by design suited for this sort of thing).
2019-01-14 23:08:44 +01:00
, pem
Rely on stack for dep versions and upgrade to LTS 5.5
2016-03-07 02:12:55 +01:00
, persistent
Treat email address as `EmailAddress` instead of `Text` including in the mailer
2018-03-06 03:26:27 +01:00
, persistent-email-address
Move most of the DB graph modules to a separate persistent-graph library
2019-01-26 23:20:19 +01:00
, persistent-graph
Use my new persistent-migration library, to which I moved the related modules
2018-02-26 15:23:02 +01:00
, persistent-migration
Rely on stack for dep versions and upgrade to LTS 5.5
2016-03-07 02:12:55 +01:00
, persistent-postgresql
Implement theater-based remote delivery and port personGrant
2023-05-25 00:17:14 +02:00
, persistent-sqlite
Rely on stack for dep versions and upgrade to LTS 5.5
2016-03-07 02:12:55 +01:00
, persistent-template
Enable git-fetch using the git executable
2016-04-19 16:56:02 +02:00
, process
Generate and keep permanent salt for generating hashids for URIs
2019-02-08 22:54:22 +01:00
-- for generating hashids salt
, random
Recursive SQL queries, still need to test before use
2016-06-13 00:37:52 +02:00
-- for Database.Persist.Local
, resourcet
Implement theater-based remote delivery and port personGrant
2023-05-25 00:17:14 +02:00
, retry
Bring Yesod scaffolding
2016-02-13 04:35:30 +01:00
, safe
Rely on stack for dep versions and upgrade to LTS 5.5
2016-03-07 02:12:55 +01:00
, shakespeare
Add option to render pretty AP JSON using Skylighting highligher2 doesn't have a JSON syntax and the JS lexer seems to be failing, not sure exactly why yet. To have an alternative, I'm adding a Skylighting option.
2019-06-29 22:31:01 +02:00
-- for json debug highlighting in Yesod.RenderSource
, skylighting
Add email sending capability to Vervis
2018-02-25 10:28:55 +01:00
, smtp-mail
Upgrade LTS from 5.13 to 6.5
2016-07-02 10:51:29 +02:00
, ssh
Periodically rotated AP actor key for signing ActivityPub requests The actor key will be used for all actors on the server. It's held in a `TVar` so that it can always be safely updated and safely retrieved (technically there is a single writer so IORef and MVar could work, but they require extra care while TVar is by design suited for this sort of thing).
2019-01-14 23:08:44 +01:00
-- for holding actor key in a TVar
, stm
Upgrade LTS from 5.13 to 6.5
2016-07-02 10:51:29 +02:00
-- for rendering diagrams
, svg-builder
Initial code for intransitive DAG drawing
2016-06-28 21:46:54 +02:00
-- for text drawing in 'diagrams'
, SVGFonts
Make initial homepage with table and simple login
2016-02-16 12:41:13 +01:00
, template-haskell
C2S: offerTicketC: If origin provided but not bundle, generate patches from git For now it's implemented only for Git: If tracker is a local loom, and a (local or remote) origin repo is specified, but no patches are provided, then generate them ourselves! * Clone the (local) target repo * Add the (local or remote) origin repo as a git remote * Make sure target branch is an ancestor of the origin branch * Generate patches for the commits that origin adds on top of target * Insert them into our DB
2022-09-22 19:12:37 +02:00
, temporary
Rely on stack for dep versions and upgrade to LTS 5.5
2016-03-07 02:12:55 +01:00
, text
Write recipient filtering utility function
2020-02-19 11:59:38 +01:00
, these
Make initial homepage with table and simple login
2016-02-16 12:41:13 +01:00
, time
Email tokens expire within 1 day
2018-04-01 05:02:35 +02:00
, time-interval
Make the cookie encryption key and timeout configurable in settings file
2018-07-01 10:15:23 +02:00
, time-interval-aeson
Email tokens expire within 1 day
2018-04-01 05:02:35 +02:00
, time-units
Implement outbox remote delivery, in handler and periodic, not used yet
2019-04-16 16:27:50 +02:00
, tls
Stop using classy-prelude-yesod
2016-02-29 15:04:23 +01:00
, transformers
Initial code for intransitive DAG drawing
2016-06-28 21:46:54 +02:00
-- probably should be replaced with lenses once I learn
, tuple
S2S: repoApplyF, for now only on remotely hosted patches
2022-06-23 11:09:02 +02:00
, typed-process
Mechanism for reporting git pushes to Vervis via post-receive hooks Here's how it works: - When Vervis starts, it writes a config file and it writes post-receive hooks into all the repos it manages - When a git push is accepted, git runs the post-receive hook, which is a trivial shell script that executes the actual Haskell program implementing the hook logic - The Haskell hook program generates a Push JSON object and HTTP POSTs it to Vervis running on localhost - Vervis currently responds with an error, the next step is to implement the actual publishing of ForgeFed Push activities
2019-09-05 14:02:42 +02:00
-- For making git hooks executable, i.e. set file mode
, unix
Federation test outbox page with form for entering JSON
2019-01-21 16:54:57 +01:00
-- For httpAPEither
, unliftio-core
ActivityPub inbox test page This patch includes some ugliness and commented out code. Sorry for that. I'll clean it up soon. Basically there's a TVar holding a Vector of at most 10 AP activities. You can freely POST stuff to /inbox, and then GET /inbox and see what you posted, or an error description saying why your activity was rejected.
2019-01-19 02:44:21 +01:00
, unliftio
Bring Yesod scaffolding
2016-02-13 04:35:30 +01:00
, unordered-containers
Display commit diff for Git repos
2018-05-21 22:32:34 +02:00
, vector
Bring Yesod scaffolding
2016-02-13 04:35:30 +01:00
, wai
Rely on stack for dep versions and upgrade to LTS 5.5
2016-03-07 02:12:55 +01:00
, wai-extra
, wai-logger
, warp
HTTP Signature verification: RSA-SHA256 and PEM/ASN1 support Before, things worked like this: * Only signatures of Ed25519 keys could be verified * Key encoding placed the plain binary Ed25519 key in the PEM, instead of the key's ASN1 encoding With this patch it now works like this: * Ed25519 signatures are supported as before * RSA keys are now supported too, assuming RSA-SHA256 signatures * Both Ed25519 and RSA keys are encoded and decoded using actual PEM with ASN1
2019-03-11 00:15:42 +01:00
-- for encoding and decoding of crypto public keys
, x509
In darcs post-apply hook, send a Push object to Vervis
2019-10-10 18:41:34 +02:00
-- for parsing darcs apply's changes XML from env var in
-- the vervis post-apply hook program
, xml
Use Pandoc for document rendering, for now just Markdown
2016-04-17 19:55:23 +02:00
, xss-sanitize
Rely on stack for dep versions and upgrade to LTS 5.5
2016-03-07 02:12:55 +01:00
, yaml
, yesod
, yesod-auth
Switch to yesod-auth-account and make the mail code independent of Vervis
2018-03-03 22:33:59 +01:00
, yesod-auth-account
Rely on stack for dep versions and upgrade to LTS 5.5
2016-03-07 02:12:55 +01:00
, yesod-core
, yesod-form
Move Yesod.Mail.Send to a new dedicated separate library
2018-03-20 17:01:33 +01:00
, yesod-mail-send
Atom and RSS feeds for repo history
2018-04-01 00:04:33 +02:00
, yesod-newsfeed
Rely on stack for dep versions and upgrade to LTS 5.5
2016-03-07 02:12:55 +01:00
, yesod-static
Add UI for display of SSH keys
2016-03-07 01:42:06 +01:00
, yesod-persistent
Compressed inventory parser and DarcsRev TH utils
2016-05-17 22:34:22 +02:00
-- for reading gzipped darcs inventory via utils in
-- Data.Attoparsec.ByteString.Local
, zlib
Expose only required modules of vervis:library in vervis.cabal Only Vervis.Hook (for the hook programs) and Vervis.Application (for the web app program itself) are exposed now. I suppose more will be needed for tests. But now there's a clear distinction what's used by other components and what isn't.
2022-09-01 11:34:25 +02:00
Move some files around, tweak the generated code a bit
2016-02-14 10:10:21 +01:00
hs-source-dirs: src
Bring Yesod scaffolding
2016-02-13 04:35:30 +01:00
default-language: Haskell2010
if flag(dev) || flag(library-only)
cpp-options: -DDEVELOPMENT
UI: getPatchR: Display diff-syntax-highlighted patch content file
2022-09-19 13:00:47 +02:00
ghc-options: -Wall -fwarn-tabs -O0
-Werror=incomplete-patterns
-Werror=missing-fields
-Werror=overlapping-patterns
Bring Yesod scaffolding
2016-02-13 04:35:30 +01:00
else
ghc-options: -Wall -fwarn-tabs -O2
executable vervis
main-is: main.hs
build-depends: base, vervis
hs-source-dirs: app
default-language: Haskell2010
Write unverified login user functions
2018-03-17 18:30:46 +01:00
ghc-options: -Wall -threaded -rtsopts -with-rtsopts=-N
Bring Yesod scaffolding
2016-02-13 04:35:30 +01:00
if flag(library-only)
buildable: False
Mechanism for reporting git pushes to Vervis via post-receive hooks Here's how it works: - When Vervis starts, it writes a config file and it writes post-receive hooks into all the repos it manages - When a git push is accepted, git runs the post-receive hook, which is a trivial shell script that executes the actual Haskell program implementing the hook logic - The Haskell hook program generates a Push JSON object and HTTP POSTs it to Vervis running on localhost - Vervis currently responds with an error, the next step is to implement the actual publishing of ForgeFed Push activities
2019-09-05 14:02:42 +02:00
executable vervis-post-receive
main-is: main.hs
build-depends: base, vervis
Install darcs post-apply hooks in darcs repos, no-op hook for now In Darcs, any command can have a post hook (and a pre hook), and the hook command can be set using a command-line option to the darcs command that you run. So, in the Vervis SSH server, if we add a --posthook option when running `darcs apply` to apply remotely received patches, we get a chance to process the patch data much like in the git post-receive hook. The setup this patch creates is similar to the git one: It writes a _darcs/prefs/defaults file to all Darcs repos, and that defaults file sets the posthook line for `darcs apply`. The posthook line simply executes the actual hook program written in Haskell. The current hook program is a one-liner that prints a line to stdout, so every time you `darcs push` you can tell the hook got executed. The next step is to implement the actual hook logic, by reading patch data from the environment variable in which Darcs puts it.
2019-10-07 16:05:52 +02:00
hs-source-dirs: hook-git
default-language: Haskell2010
ghc-options: -Wall
executable vervis-post-apply
main-is: main.hs
build-depends: base, vervis
hs-source-dirs: hook-darcs
Mechanism for reporting git pushes to Vervis via post-receive hooks Here's how it works: - When Vervis starts, it writes a config file and it writes post-receive hooks into all the repos it manages - When a git push is accepted, git runs the post-receive hook, which is a trivial shell script that executes the actual Haskell program implementing the hook logic - The Haskell hook program generates a Push JSON object and HTTP POSTs it to Vervis running on localhost - Vervis currently responds with an error, the next step is to implement the actual publishing of ForgeFed Push activities
2019-09-05 14:02:42 +02:00
default-language: Haskell2010
ghc-options: -Wall
Bring Yesod scaffolding
2016-02-13 04:35:30 +01:00
test-suite test
main-is: Spec.hs
Expose only required modules of vervis:library in vervis.cabal Only Vervis.Hook (for the hook programs) and Vervis.Application (for the web app program itself) are exposed now. I suppose more will be needed for tests. But now there's a clear distinction what's used by other components and what isn't.
2022-09-01 11:34:25 +02:00
Bring Yesod scaffolding
2016-02-13 04:35:30 +01:00
default-extensions: TemplateHaskell
QuasiQuotes
OverloadedStrings
CPP
MultiParamTypeClasses
TypeFamilies
GADTs
GeneralizedNewtypeDeriving
FlexibleContexts
FlexibleInstances
EmptyDataDecls
NoMonomorphismRestriction
DeriveDataTypeable
ViewPatterns
TupleSections
Expose only required modules of vervis:library in vervis.cabal Only Vervis.Hook (for the hook programs) and Vervis.Application (for the web app program itself) are exposed now. I suppose more will be needed for tests. But now there's a clear distinction what's used by other components and what isn't.
2022-09-01 11:34:25 +02:00
Bring Yesod scaffolding
2016-02-13 04:35:30 +01:00
build-depends: base
, vervis
DB: Switch to more flexible collaborator model
2022-06-22 08:19:37 +02:00
, yesod-test
Bring Yesod scaffolding
2016-02-13 04:35:30 +01:00
, yesod-core
, yesod
Make it build with persistent
2016-02-06 14:36:35 +01:00
, persistent
Bring Yesod scaffolding
2016-02-13 04:35:30 +01:00
, persistent-postgresql
Make minimal Yesod app that returns main view as an HTML table
2016-02-12 02:53:19 +01:00
, resourcet
Bring Yesod scaffolding
2016-02-13 04:35:30 +01:00
, monad-logger
, shakespeare
Remove obsolete code and start using stack
2016-02-12 12:01:53 +01:00
, transformers
Bring Yesod scaffolding
2016-02-13 04:35:30 +01:00
, hspec >= 2.0.0
, aeson
Expose only required modules of vervis:library in vervis.cabal Only Vervis.Hook (for the hook programs) and Vervis.Application (for the web app program itself) are exposed now. I suppose more will be needed for tests. But now there's a clear distinction what's used by other components and what isn't.
2022-09-01 11:34:25 +02:00
DB graph cycle existence checking using recursive SQL query
2016-07-05 10:46:58 +02:00
hs-source-dirs: test
Initial record with empty package that builds
2016-01-28 15:15:54 +01:00
default-language: Haskell2010
Not-yet-added empty test suite
2016-07-05 14:36:40 +02:00
ghc-options: -Wall
type: exitcode-stdio-1.0
-- test-suite test-graph
-- main-is: Test.hs
-- build-depends: base
-- , fgl
-- , fgl-arbitrary
-- , hspec
-- , vervis
-- hs-source-dirs: test
-- default-language: Haskell2010
-- ghc-options: -Wall
-- type: exitcode-stdio-1.0
Copy permalink