Management Commands =================== These commands can be called from a CLI. Read the `official documentation `_ for help. Call the commands with ``-h`` for more details on the usage. createadmin ----------- This creates a super user like the command ``createsuperuser`` and creates a member for that new user, which is required by juntagrico to be able to log in. If you need to create members for previously created superusers, use ``create_member_for_superusers`` instead. create_member_for_superusers ---------------------------- The command ``create_member_for_superusers`` will create such a member for all existing super users. The member is required by juntagrico to be able to log in. .. _reference-generate-depot-list: generate_depot_list ------------------- This command generates all depot lists. This can be used to generate the lists regularly, e.g., using a cronjob. .. note:: When using a :ref:`custom depot list generator `, the arguments have the effect, that you implement. .. warning:: Currently all pending depot changes are applied, when executing the command on a weekday specified in :ref:`DEPOT_LIST_GENERATION_DAYS `. This behaviour will be DEPRECATED. Use ``--future`` explicitly, to apply the depot changes. Use ``--no-future`` to prevent depot changes in that case. remind_members -------------- Sends a job reminder email to all members that are signed up to a job in the next 48 hours. Will only send the notification once, i.e., executing the command twice will not send another notification to those already notified. shift_time ---------- When changing the ``TIMEZONE`` setting on an existing installation, you will have to adapt the times of all existing jobs. This command helps you with that task. .. warning:: No notification emails will be sent, when changing the job time with this command. This command is also available to super users under the hidden url ``/command/shifttime``. .. _reference-commands-mailtexts: mailtexts --------- Prints the text of all notification emails using real data from the database, but without sending any emails. This can be used to test, if the emails meet your expectations, e.g. if your modifications work as expected. generate_testdata ----------------- .. warning:: Do not use this command in production In a testing environment, this command can be used to generate some minimum test data, e.g. subscription types, members, jobs etc. generate_testdata_advanced -------------------------- .. warning:: Do not use this command in production .. note:: This command requires ``faker``. Install it via pip. Like ``generate_testdata`` but produces a much bigger set of test data.