Confirmed users
26
edits
AMO/SigningService: Difference between revisions
Jump to navigation
Jump to search
Add a "usage" section
(Add a "usage" section) |
|||
| Line 130: | Line 130: | ||
} | } | ||
</bugzilla> | </bugzilla> | ||
== Usage == | |||
There's two management commands to manually sign add-ons: | |||
===sign_addons=== | |||
This can be used to sign a list of add-ons, by providing their IDs: | |||
'''python manage.py sign_addons 123 124 125''' | |||
===process_addons=== | |||
This is a more general management command that can run tasks on every add-on: | |||
'''python manage.py process_addons --task sign_addons''' | |||
Running this will sign each add-on. Celery tasks will be used. | |||