Files

T

Daniel Gak Anagrov 3ca4a11ca3 feat(notifications): basic listener structure, notification record, delayed mechanism (#5432 )

* feat: basic notification listener sturcuture

* feat: clean up generated gql

* chore: edited structure

* feat: added basic repo

* feat: ported comment email to job queue

* feat: ported stream access request accepted

* feat: added notification insertion

* fix: minor typings

* feat: delayed notifications

* updated types

* feat: fixed gql

* notifications are listed

* index on notifications

* feat: while loop skiping for update locked

* delayed notification for access request

* take into account user prefrences

* on comment view, notification is marked as read

* feat: added gql notifications

* feat: avoid raising errors

* fix: error added scopes

* fix: mr comments

* fix: cursor and service method

* feat: added stronger types to notifications and versioning logic

* minor: rows updated

2025-10-06 12:19:12 +01:00

commands

feat(notifications): basic listener structure, notification record, delayed mechanism (#5432 )

2025-10-06 12:19:12 +01:00

index.ts

chore(server): migrating fully to ESM (#5042 )

2025-07-14 10:26:19 +03:00

readme.md

feat(server): cli and cross-server-sync multiregion support (#3527 )

2024-11-22 19:52:58 +01:00

readme.md

Using CLI

You can run it like so from the server package's root directory: ./bin/cli (or yarn cli)

Use the --help argument to get more info about each command.

Example for running migrations: yarn cli db migrate latest

Using CLI in test mode (& DB)

Use yarn cli:test to run the CLI in the TEST environment. This will use the test DB and will likely run some code a bit differently than in prod/dev.

Creating new commands

CLI is defined using yargs.We use it to define hierarchical trees of commands which allows for better organization both for command definition and for using the CLI.

All commands are created in the commands directory. Commands should be defined using command modules.

Any top-level modules under commands will be assumed to be command modules. If you want to define a child command for a top-level command, then configure the top-level command to look for further child commands using .commandDir().

Then put those child command modules in a subdirectory that is named after the top level command. So if the top level command is "db", then all of its child commands should be put inside a "db" subfolder.

Example commands dir:

- commands
    - db
        - migrate.js
    - db.js

In this case, db.js is the command module for the top-level db command. And then inside the db folder there's a command module migrate.js for the migrate child command of db.

This results in 2 commands - db and db migrate.