The repository will be merged into and will therefore be empty after the migration.Īll affected repositories will be provided as empty repositories for a transition period after the migration.
The repository will be split into and, the repository will be split into and. Notification when the migration starts, and when it is completed, will be published on the mailing list. The Arch Linux packaging team will not be able to update packages in any of the repositories during this period. POST and PUT requests must also include the current Unix Epoch and the app_id.This Friday morning () the Git packaging migration will start until Sunday (). Available HTTP verbs are GET, POST, PUT to respectively read, create or update ARKs to the databaseįor POST and PUT, an Authorization HTTP header must contain a hmac256 of the request body, signed with your secret key (see Add API account to generate your key).:/ will redirect you to the location available in the db. Any other column will be treated as meta: ark csv-import /path/to/some/file.csvĪ csv file is generated at /path/to/some/file-out.csv with added ARK names for creations. Must have columns app_id, ark_location, ark_name (empty value for creation). CSV importįor mass-creation or update of ARK names. Would generate the following output: Access granted to untitled app (Start web server first !) pytest -vv tests.py Warning ! This will wipe all data in your ARK database. env and change settings): export ARK_SERVER_PGSQL_HOST=Įxport ARK_SERVER_PGSQL_PASSWORD=Įxport ARK_SERVER_DEBUG=0 # don't set to 1 in productionĮxport ARK_SERVER_WORKERS=4 # as much as available cpu coresĪll command-line tools support -h flag for help. DependenciesĬreate a virtualenv and activate it: make venvĬreate a database and then override default env vars (or copy the. It offers a database, command-line tools and an HTTP API. The goal of this software is to offer a solution for a Name Assigning Authority to distribute Archival Resources Keys and maintain basic information about the resources.