Implement runner in client side

[github/Chocobozzz/PeerTube.git] / client / src / app / +admin / config / edit-custom-config / edit-live-configuration.component.html

diff --git a/client/src/app/+admin/config/edit-custom-config/edit-live-configuration.component.html b/client/src/app/+admin/config/edit-custom-config/edit-live-configuration.component.html
index c90c34c80f169b34ba157f4038f3128397d3d362..34ce8efa6cab3da192235ce4c7f9c120d9644766 100644 (file)
--- a/client/src/app/+admin/config/edit-custom-config/edit-live-configuration.component.html
+++ b/client/src/app/+admin/config/edit-custom-config/edit-live-configuration.component.html
@@ -110,6 +110,20 @@
             </my-peertube-checkbox>
           </div>
 
+          <div class="form-group" formGroupName="remoteRunners" [ngClass]="getDisabledLiveTranscodingClass()">
+            <my-peertube-checkbox
+              inputName="transcodingRemoteRunnersEnabled" formControlName="enabled"
+              i18n-labelText labelText="Enable remote runners"
+            >
+              <ng-container ngProjectAs="description">
+                <span i18n>
+                  Use <a routerLink="/admin/system/runners/runners-list">remote runners</a> to process live transcoding.
+                  Remote runners has to register on your instance first.
+                </span>
+              </ng-container>
+            </my-peertube-checkbox>
+          </div>
+
           <div class="form-group" [ngClass]="getDisabledLiveTranscodingClass()">
             <label i18n for="liveTranscodingThreads">Live resolutions to generate</label>