URLs when creating multiple components from a single VCS repository. Note Most of the component creation happens in the background. Check the task_url attribute of created component and follow the progress html] Customizing backup The database backup can be configured via DATABASE_BACKUP. The backup creation can be customized using BORG_EXTRA_ARGS. Weblate provisioned backup storage The easiest way of created users to a team based on their e-mail addresses. This assignment only happens upon account creation. The most common use-case for the feature is to assign all new users to some default team. In order

URLs when creating multiple components from a single VCS repository. Note Most of the component creation happens in the background. Check the task_url attribute of created component and follow the progress html] Customizing backup The database backup can be configured via DATABASE_BACKUP. The backup creation can be customized using BORG_EXTRA_ARGS. Weblate provisioned backup storage The easiest way of created users to a team based on their e-mail addresses. This assignment only happens upon account creation. The most common use-case for the feature is to assign all new users to some default team. In order

URLs when creating multiple components from a single VCS repository. Note Most of the component creation happens in the background. Check the task_url attribute of created component and follow the progress html] Customizing backup The database backup can be configured via DATABASE_BACKUP. The backup creation can be customized using BORG_EXTRA_ARGS. Weblate provisioned backup storage The easiest way of created users to a team based on their e-mail addresses. This assignment only happens upon account creation. The most common use-case for the feature is to assign all new users to some default team. In order

URLs when creating multiple components from a single VCS repository. Note Most of the component creation happens in the background. Check the task_url attribute of created component and follow the progress html] Customizing backup The database backup can be configured via DATABASE_BACKUP. The backup creation can be customized using BORG_EXTRA_ARGS. Weblate provisioned backup storage The easiest way of created users to a team based on their e-mail addresses. This assignment only happens upon account creation. The most common use-case for the feature is to assign all new users to some default team. In order

URLs when creating multiple components from a single VCS repository. Note Most of the component creation happens in the background. Check the task_url attribute of created component and follow the progress html] Customizing backup The database backup can be configured via DATABASE_BACKUP. The backup creation can be customized using BORG_EXTRA_ARGS. Weblate provisioned backup storage The easiest way of created users to a team based on their e-mail addresses. This assignment only happens upon account creation. The most common use-case for the feature is to assign all new users to some default team. In order

URLs when creating multiple components from a single VCS repository. Note Most of the component creation happens in the background. Check the task_url attribute of created component and follow the progress html] Customizing backup The database backup can be configured via DATABASE_BACKUP. The backup creation can be customized using BORG_EXTRA_ARGS. Weblate provisioned backup storage The easiest way of created users to a team based on their e-mail addresses. This assignment only happens upon account creation. The most common use-case for the feature is to assign all new users to some default team. In order

URLs when creating multiple components from a single VCS repository. Note Most of the component creation happens in the background. Check the task_url attribute of created component and follow the progress html] Customizing backup The database backup can be configured via DATABASE_BACKUP. The backup creation can be customized using BORG_EXTRA_ARGS. Weblate provisioned backup storage The easiest way of created users to a team based on their e-mail addresses. This assignment only happens upon account creation. The most common use-case for the feature is to assign all new users to some default team. In order

URLs when creating multiple components from a single VCS repository. Note Most of the component creation happens in the background. Check the task_url attribute of created component and follow the progress html] Customizing backup The database backup can be configured via DATABASE_BACKUP. The backup creation can be customized using BORG_EXTRA_ARGS. Weblate provisioned backup storage The easiest way of created users to a team based on their e-mail addresses. This assignment only happens upon account creation. The most common use-case for the feature is to assign all new users to some default team. In order

URLs when creating multiple components from a single VCS repository. Note Most of the component creation happens in the background. Check the task_url attribute of created component and follow the progress html] Customizing backup The database backup can be configured via DATABASE_BACKUP. The backup creation can be customized using BORG_EXTRA_ARGS. Weblate provisioned backup storage The easiest way of created users to a group based on their e-mail addresses. This assignment only happens upon account creation. The most common use-case for the feature is to assign all new users to some default group. In

URLs when creating multiple components from a single VCS repository. Note Most of the component creation happens in the background. Check the task_url attribute of created component and follow the progress html] Customizing backup The database backup can be configured via DATABASE_BACKUP. The backup creation can be customized using BORG_EXTRA_ARGS. Weblate provisioned backup storage The easiest way of created users to a group based on their e-mail addresses. This assignment only happens upon account creation. The most common use-case for the feature is to assign all new users to some default group. In