accordsync-server 0.3.0__tar.gz

accordsync_server-0.3.0/.gitignore

@@ -0,0 +1,9 @@
+.venv/
+__pycache__/
+*.egg-info/
+dist/
+build/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+/interop/node/node_modules/

accordsync_server-0.3.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

accordsync_server-0.3.0/PKG-INFO

@@ -0,0 +1,135 @@
+Metadata-Version: 2.5
+Name: accordsync-server
+Version: 0.3.0
+Summary: The Accord sync server for Python on PostgreSQL, framework-agnostic.
+Project-URL: Homepage, https://accord.benhattab.pro
+Project-URL: Source, https://github.com/crossben/accordsync-python
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: crdt,local-first,offline-first,sync
+Requires-Python: >=3.11
+Requires-Dist: accordsync-core<0.4,>=0.3
+Requires-Dist: psycopg[binary,pool]>=3.2
+Requires-Dist: pyjwt[crypto]>=2.10
+Description-Content-Type: text/markdown
+
+# accordsync-server
+
+**The [Accord](https://accord.benhattab.pro) sync server for Python, on PostgreSQL.**
+
+Framework-agnostic: push and pull, scopes, JWT auth, limits, rate limits, CORS and compaction behind
+one `handle()` call per request, plus a WSGI application. It speaks the same protocol, merges by the
+same rules and uses the same PostgreSQL schema as
+[`@accordsync/server`](https://www.npmjs.com/package/@accordsync/server), so the TypeScript, React
+Native, Flutter and Python clients sync with it unchanged.
+
+With FastAPI or Django, use [`accordsync-fastapi`](https://pypi.org/project/accordsync-fastapi/) or
+[`accordsync-django`](https://pypi.org/project/accordsync-django/): they route to this package. This
+page is for WSGI, or for another framework.
+
+## Install
+
+```sh
+pip install accordsync-server
+```
+
+Python 3.11+ and PostgreSQL (the conformance suite and the example apps use PostgreSQL 16). It
+connects with psycopg 3 and its connection pool.
+
+## Define the server
+
+`define_server()` takes the same parts as `defineServer` in TypeScript: the schema, a scope function
+per record type, the access a user gets from their JWT claims, and how tokens are checked. It checks
+at once that every record type has a scope function.
+
+```python
+# myapp/sync.py
+from accordsync_core import conflict, counter, define_schema, lww, set_
+from accordsync_server import Access, Auth, ScopedRecord, define_server
+
+schema = define_schema(
+    {"dossier": {"agent": lww(), "visits": counter(), "docs": set_(), "status": conflict()}}
+)
+
+
+def dossier_scope(record: ScopedRecord) -> list[str]:
+    """The scope keys of a record, from its current fields."""
+    agent = record.fields.get("agent")
+    return [f"agent:{agent}"] if isinstance(agent, str) else []
+
+
+server = define_server(
+    schema=schema,
+    scopes={"dossier": dossier_scope},
+    # The scope keys a user may read and write, from their verified JWT claims.
+    access=lambda claims: Access(read=[f"agent:{claims['sub']}"], write=[f"agent:{claims['sub']}"]),
+    auth=Auth.jwks(
+        "https://auth.example.com/.well-known/jwks.json",
+        issuer="https://auth.example.com/",
+        audience="accord",
+    ),
+)
+```
+
+Optional arguments: `cors` (browser origins allowed to call the API), `rate_limit` (a `RateLimits`;
+default 600 requests a minute per device and 1 800 per user; `False` turns it off), `compaction` (a
+`Compaction`: device TTL, interval, minimum ops) and `limits` (a `Limits`: body size, concurrent
+pushes, ops per push, pull page size, scope delta size, clock skew). `Auth.hs256(secret)` is for
+development and tests.
+
+## Serve it
+
+`AccordServer(definition, pool)` serves `GET /health`, `POST /v1/push` and `GET /v1/pull`.
+`server.handle(method, path, query, headers, body)` returns a `Response(status, headers, body)` for
+any framework; `server.wsgi` is a ready WSGI application:
+
+```python
+# myapp/wsgi.py
+import os
+
+from accordsync_server import AccordServer, create_pool
+
+from myapp.sync import server as definition
+
+app = AccordServer(definition, create_pool(os.environ["ACCORD_DATABASE_URL"])).wsgi
+```
+
+`create_pool(url, size=20)` opens a psycopg pool of up to `size` connections. Serve `app` with a
+threaded WSGI server (waitress, or gunicorn with `--threads`): each request holds a thread while it
+waits on PostgreSQL. `ACCORD_DATABASE_URL` is a URL like `postgresql://user:password@host:5432/db`.
+
+## Migrations and compaction
+
+```sh
+ACCORD_DATABASE_URL=postgresql://… python -m accordsync_server migrate
+ACCORD_DATABASE_URL=postgresql://… python -m accordsync_server compact --definition myapp.sync:server
+```
+
+Run `compact` from cron at the definition's `compaction.interval_ms` (default hourly). It takes
+PostgreSQL's exclusive advisory lock, so overlapping runs, or several servers, do not conflict. In
+code: `migrate(url)` and `compact(pool, definition)`.
+
+## One database, any Accord server
+
+The migrations are the TypeScript server's, recorded in the same ledger table (`kysely_migration`):
+a database migrated by `@accordsync/server` is up to date here, and the other way round. One database
+can be served by TypeScript and Python servers at the same time, with clients sent to either. The
+repository's `server-interop/` harness does exactly that: Python and TypeScript devices send every
+request to a randomly chosen server, through a network that loses requests and responses, and must
+end with identical data. This server, and the repository's FastAPI and Django example apps, also
+pass Accord's black-box HTTP conformance suite, the same one the TypeScript server passes.
+
+## Security notes
+
+- Requests authenticate with `Authorization: Bearer <jwt>`. In production use `Auth.jwks()` with an
+  issuer and an audience.
+- Rate limits are kept in memory, per process: with several worker processes, each has its own
+  buckets.
+- Request bodies above `limits.max_body_bytes` (default 5 MiB) get 413; the WSGI app stops reading
+  past the limit.
+- CORS for the sync API is the definition's `cors` list, answered by the server.
+- What a user may read and write is decided only by your `access` function and scope functions.
+  See [docs/security.md](https://github.com/crossben/accordsync/blob/main/docs/security.md).
+
+Docs: [accord.benhattab.pro/docs/python](https://accord.benhattab.pro/docs/python/) ·
+Source: [crossben/accordsync-python](https://github.com/crossben/accordsync-python) · Licence: Apache-2.0

accordsync_server-0.3.0/README.md

@@ -0,0 +1,120 @@
+# accordsync-server
+
+**The [Accord](https://accord.benhattab.pro) sync server for Python, on PostgreSQL.**
+
+Framework-agnostic: push and pull, scopes, JWT auth, limits, rate limits, CORS and compaction behind
+one `handle()` call per request, plus a WSGI application. It speaks the same protocol, merges by the
+same rules and uses the same PostgreSQL schema as
+[`@accordsync/server`](https://www.npmjs.com/package/@accordsync/server), so the TypeScript, React
+Native, Flutter and Python clients sync with it unchanged.
+
+With FastAPI or Django, use [`accordsync-fastapi`](https://pypi.org/project/accordsync-fastapi/) or
+[`accordsync-django`](https://pypi.org/project/accordsync-django/): they route to this package. This
+page is for WSGI, or for another framework.
+
+## Install
+
+```sh
+pip install accordsync-server
+```
+
+Python 3.11+ and PostgreSQL (the conformance suite and the example apps use PostgreSQL 16). It
+connects with psycopg 3 and its connection pool.
+
+## Define the server
+
+`define_server()` takes the same parts as `defineServer` in TypeScript: the schema, a scope function
+per record type, the access a user gets from their JWT claims, and how tokens are checked. It checks
+at once that every record type has a scope function.
+
+```python
+# myapp/sync.py
+from accordsync_core import conflict, counter, define_schema, lww, set_
+from accordsync_server import Access, Auth, ScopedRecord, define_server
+
+schema = define_schema(
+    {"dossier": {"agent": lww(), "visits": counter(), "docs": set_(), "status": conflict()}}
+)
+
+
+def dossier_scope(record: ScopedRecord) -> list[str]:
+    """The scope keys of a record, from its current fields."""
+    agent = record.fields.get("agent")
+    return [f"agent:{agent}"] if isinstance(agent, str) else []
+
+
+server = define_server(
+    schema=schema,
+    scopes={"dossier": dossier_scope},
+    # The scope keys a user may read and write, from their verified JWT claims.
+    access=lambda claims: Access(read=[f"agent:{claims['sub']}"], write=[f"agent:{claims['sub']}"]),
+    auth=Auth.jwks(
+        "https://auth.example.com/.well-known/jwks.json",
+        issuer="https://auth.example.com/",
+        audience="accord",
+    ),
+)
+```
+
+Optional arguments: `cors` (browser origins allowed to call the API), `rate_limit` (a `RateLimits`;
+default 600 requests a minute per device and 1 800 per user; `False` turns it off), `compaction` (a
+`Compaction`: device TTL, interval, minimum ops) and `limits` (a `Limits`: body size, concurrent
+pushes, ops per push, pull page size, scope delta size, clock skew). `Auth.hs256(secret)` is for
+development and tests.
+
+## Serve it
+
+`AccordServer(definition, pool)` serves `GET /health`, `POST /v1/push` and `GET /v1/pull`.
+`server.handle(method, path, query, headers, body)` returns a `Response(status, headers, body)` for
+any framework; `server.wsgi` is a ready WSGI application:
+
+```python
+# myapp/wsgi.py
+import os
+
+from accordsync_server import AccordServer, create_pool
+
+from myapp.sync import server as definition
+
+app = AccordServer(definition, create_pool(os.environ["ACCORD_DATABASE_URL"])).wsgi
+```
+
+`create_pool(url, size=20)` opens a psycopg pool of up to `size` connections. Serve `app` with a
+threaded WSGI server (waitress, or gunicorn with `--threads`): each request holds a thread while it
+waits on PostgreSQL. `ACCORD_DATABASE_URL` is a URL like `postgresql://user:password@host:5432/db`.
+
+## Migrations and compaction
+
+```sh
+ACCORD_DATABASE_URL=postgresql://… python -m accordsync_server migrate
+ACCORD_DATABASE_URL=postgresql://… python -m accordsync_server compact --definition myapp.sync:server
+```
+
+Run `compact` from cron at the definition's `compaction.interval_ms` (default hourly). It takes
+PostgreSQL's exclusive advisory lock, so overlapping runs, or several servers, do not conflict. In
+code: `migrate(url)` and `compact(pool, definition)`.
+
+## One database, any Accord server
+
+The migrations are the TypeScript server's, recorded in the same ledger table (`kysely_migration`):
+a database migrated by `@accordsync/server` is up to date here, and the other way round. One database
+can be served by TypeScript and Python servers at the same time, with clients sent to either. The
+repository's `server-interop/` harness does exactly that: Python and TypeScript devices send every
+request to a randomly chosen server, through a network that loses requests and responses, and must
+end with identical data. This server, and the repository's FastAPI and Django example apps, also
+pass Accord's black-box HTTP conformance suite, the same one the TypeScript server passes.
+
+## Security notes
+
+- Requests authenticate with `Authorization: Bearer <jwt>`. In production use `Auth.jwks()` with an
+  issuer and an audience.
+- Rate limits are kept in memory, per process: with several worker processes, each has its own
+  buckets.
+- Request bodies above `limits.max_body_bytes` (default 5 MiB) get 413; the WSGI app stops reading
+  past the limit.
+- CORS for the sync API is the definition's `cors` list, answered by the server.
+- What a user may read and write is decided only by your `access` function and scope functions.
+  See [docs/security.md](https://github.com/crossben/accordsync/blob/main/docs/security.md).
+
+Docs: [accord.benhattab.pro/docs/python](https://accord.benhattab.pro/docs/python/) ·
+Source: [crossben/accordsync-python](https://github.com/crossben/accordsync-python) · Licence: Apache-2.0

accordsync_server-0.3.0/pyproject.toml

@@ -0,0 +1,25 @@
+[project]
+name = "accordsync-server"
+version = "0.3.0"
+description = "The Accord sync server for Python on PostgreSQL, framework-agnostic."
+readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+requires-python = ">=3.11"
+keywords = ["offline-first", "sync", "crdt", "local-first"]
+dependencies = [
+    "accordsync-core>=0.3,<0.4",
+    "psycopg[binary,pool]>=3.2",
+    "pyjwt[crypto]>=2.10",
+]
+
+[project.urls]
+Homepage = "https://accord.benhattab.pro"
+Source = "https://github.com/crossben/accordsync-python"
+
+[build-system]
+requires = ["hatchling>=1.26"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/accordsync_server"]

accordsync_server-0.3.0/src/accordsync_server/__init__.py

@@ -0,0 +1,54 @@
+"""The Accord sync server on PostgreSQL, framework-agnostic: push, pull, scopes, compaction."""
+
+from accordsync_core import PROTOCOL_VERSION
+
+from .app import AccordServer, Response
+from .auth import AuthError, create_verifier
+from .compact import CompactionResult, compact
+from .db import create_pool
+from .define import (
+    Access,
+    Auth,
+    Claims,
+    Compaction,
+    Limits,
+    RateLimit,
+    RateLimits,
+    ScopedRecord,
+    ServerDefinition,
+    define_server,
+)
+from .migrations import migrate
+from .ratelimit import Limiter, RateLimiter
+from .sync import FEED_LOCK, BadRequestError, Caller, ForbiddenError, op_hash, pull, push
+
+__all__ = [
+    "FEED_LOCK",
+    "PROTOCOL_VERSION",
+    "Access",
+    "AccordServer",
+    "Auth",
+    "AuthError",
+    "BadRequestError",
+    "Caller",
+    "Claims",
+    "Compaction",
+    "CompactionResult",
+    "ForbiddenError",
+    "Limiter",
+    "Limits",
+    "RateLimit",
+    "RateLimiter",
+    "RateLimits",
+    "Response",
+    "ScopedRecord",
+    "ServerDefinition",
+    "compact",
+    "create_pool",
+    "create_verifier",
+    "define_server",
+    "migrate",
+    "op_hash",
+    "pull",
+    "push",
+]

accordsync_server-0.3.0/src/accordsync_server/__main__.py

@@ -0,0 +1,50 @@
+"""`python -m accordsync_server migrate|compact`.
+
+`migrate` needs only ACCORD_DATABASE_URL. `compact` also needs the server definition:
+`--definition module:attribute` (or ACCORD_SERVER) naming a `ServerDefinition`.
+"""
+
+from __future__ import annotations
+
+import argparse
+import importlib
+import json
+import os
+import sys
+
+from .compact import compact
+from .db import create_pool
+from .define import ServerDefinition
+from .migrations import migrate
+
+
+def load_definition(spec: str) -> ServerDefinition:
+    module, _, attr = spec.partition(":")
+    value = getattr(importlib.import_module(module), attr or "server")
+    if not isinstance(value, ServerDefinition):
+        raise SystemExit(f"{spec} is not a ServerDefinition (use define_server(...))")
+    return value
+
+
+def main(argv: list[str] | None = None) -> int:
+    parser = argparse.ArgumentParser(prog="python -m accordsync_server")
+    parser.add_argument("command", choices=["migrate", "compact"])
+    parser.add_argument("--database-url", default=os.environ.get("ACCORD_DATABASE_URL"))
+    parser.add_argument("--definition", default=os.environ.get("ACCORD_SERVER"))
+    args = parser.parse_args(argv)
+    if not args.database_url:
+        parser.error("ACCORD_DATABASE_URL (or --database-url) is required")
+    if args.command == "migrate":
+        ran = migrate(args.database_url)
+        print(f"applied {len(ran)} migration(s): {', '.join(ran)}" if ran else "up to date")
+        return 0
+    if not args.definition:
+        parser.error("compact needs --definition module:attribute (or ACCORD_SERVER)")
+    definition = load_definition(args.definition)
+    with create_pool(args.database_url, size=2) as pool:
+        print(json.dumps(compact(pool, definition)))
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())