.. _dput-ng-profiles: ======================= dput-ng profile options ======================= A minimal `dput-ng `__ profile for uploading to a Debusine server is as follows: .. code-block:: json { "allow_unsigned_uploads": true, "debusine": { "scope": "debian", "workflow_data": { "source_artifact": "@UPLOAD@" }, "workspace": "developers" }, "fqdn": "debusine.debian.net", "incoming": "/", "meta": "debusine", "method": "debusine" } ``incoming`` must be set, but its value is ignored. In addition, either ``debusine.workflow`` or ``debusine.workflows_by_distribution`` must be set. Supported options: * ``fqdn``: the host name of the Debusine server * ``debusine.scope``: the :ref:`scope ` to upload to * ``debusine.workspace``: the :ref:`workspace ` to upload to * ``debusine.workflow``: the name of the :ref:`workflow ` template to start (configured by the workspace owners, and normally an instance of :ref:`debian_pipeline `); optional if ``debusine.workflows_by_distribution`` is set) * ``debusine.workflows_by_distribution``: a mapping from target distribution names in the ``.changes`` file to workflow template names, as in ``debusine.workflow``; optional if ``debusine.workflow`` is set * ``debusine.workflow_data``: run-time parameters to provide to the workflow; the string ``"@UPLOAD@"`` will be replaced with the artifact ID of your upload If you are uploading to ``debusine.debian.net``, then these options are set to reasonable values by default. In some cases you may need to override ``debusine.workspace`` and/or ``debusine.workflow``. Once `#983160 `__ is fixed, you will be able to set these options on the ``dput`` command line. Until then, you will need to create a configuration file such as ``~/.dput.d/profiles/debusine.debian.net.json`` instead; see the `dput-ng configuration file documentation `__ for details.