PeerTube CLI
- 
@girish this morning they released 2.4.0 adding many features and solving even more bugs of which 2 of them where blocking for us  @imc67 said in PeerTube CLI: @girish this morning they released 2.4.0 adding many features and solving even more bugs of which 2 of them where blocking for us  Friendly reminder  
- 
@imc67 said in PeerTube CLI: @girish this morning they released 2.4.0 adding many features and solving even more bugs of which 2 of them where blocking for us  Friendly reminder  
- 
Also interested in the cli to be able to relaunch transcoding jobs example : 
 sudo -u peertube NODE_CONFIG_DIR=/var/www/peertube/config NODE_ENV=production npm run create-transcoding-job -- --generate-hls -v c249320b-5263-4b2b-b1e8-14d07403079c
- 
@imc67 Noted  I will get to this next week though since we are rolling out 5.6 this week. But I am very interested in getting that app to stable state asap. I will get to this next week though since we are rolling out 5.6 this week. But I am very interested in getting that app to stable state asap.
- 
I tried (in the 0.7 version) the following command: sudo -u root NODE_CONFIG_DIR=/var/www/peertube/config NODE_ENV=production npm run create-transcoding-job -- -v b8b791eb-9e38-4c4f-b797-0347662bb45fbut this error returns: sudo: npm: command not foundIs the path in the command ok? 
- 
peertube as many other apps should ideally run with the cloudronuser, so maybe try that user instead of root.
- 
Ah sudo apparently does not carry over the env bits for this. So instead use gosu cloudron:cloudron npm ...that should do.@nebulon said in PeerTube CLI: gosu cloudron:cloudron getting one step closer but still an error: gosu cloudron:cloudron NODE_CONFIG_DIR=/var/www/peertube/config NODE_ENV=production npm run create-transcoding-job -- -v db21c654-6ca3-470e-b6a0-0f31bbcb3c37 error: exec: "NODE_CONFIG_DIR=/var/www/peertube/config": stat NODE_CONFIG_DIR=/var/www/peertube/config: no such file or directory
- 
NODE_CONFIG_DIRis already properly set in the environment pointing to/app/code/server/configso remove that from your commandline.@nebulon again one step closer, but... /app/code/server# gosu cloudron:cloudron NODE_ENV=production npm run create-transcoding-job -- -v db21c654-6ca3-470e-b6a0-0f31bbcb3c37 error: exec: "NODE_ENV=production": executable file not found in $PATHwith the current size.
- 
it seems to work here : 
  and transcoding works too : 
  the "solution" is to disable HLS Requires ffmpeg >= 4.1 Generate HLS playlists and fragmented MP4 files resulting in a better playback than with the current default player: Resolution change is smoother Faster playback in particular with long videos More stable playback (less bugs/infinite loading)If you also enabled WebTorrent support, it will multiply videos storage by 2 
- 
it seems to work here : 
  and transcoding works too : 
  the "solution" is to disable HLS Requires ffmpeg >= 4.1 Generate HLS playlists and fragmented MP4 files resulting in a better playback than with the current default player: Resolution change is smoother Faster playback in particular with long videos More stable playback (less bugs/infinite loading)If you also enabled WebTorrent support, it will multiply videos storage by 2 
- 
@rmdes HLS seems to be messy. is ffmpeg not >=4.1 by default? does HLS being enabled mean the fragmented MP4 and original are in place? That already means 2x the original. What is it about WebTorrent that 2x that even more? 
- 
Fresh update with the latest version on a fresh cloudron : when I follow the doc here : https://docs.cloudron.io/apps/peertube/ to import a video from cli 
 I getpeertube import --url https://domain.com --username user --password bloodypass --target-url https://www.youtube.com/watch?v=xxxx --tmpdir /tmp the shell returns this : 
 --username field is required
 --password field is requiredAnything changed perhaps for the cli & latest peertube version ? 
- 
Fresh update with the latest version on a fresh cloudron : when I follow the doc here : https://docs.cloudron.io/apps/peertube/ to import a video from cli 
 I getpeertube import --url https://domain.com --username user --password bloodypass --target-url https://www.youtube.com/watch?v=xxxx --tmpdir /tmp the shell returns this : 
 --username field is required
 --password field is requiredAnything changed perhaps for the cli & latest peertube version ? So the peertube cli has now a neat feature to remember instances it is being used to upload from the cli : peertube auth : add [options] remember your accounts on remote instances for easier use 
 del <url> unregisters a remote instance
 list lists registered remote instances
 set-default <url> set an existing entry as default
 help [command] display help for commandExamples: $ peertube auth add -u https://peertube.cpy.re -U "PEERTUBE_USER" --password "PEERTUBE_PASSWORD" $ peertube auth add -u https://peertube.cpy.re -U root $ peertube auth list $ peertube auth del https://peertube.cpy.reWhen I try to use it, I get this : node:internal/process/promises:246 triggerUncaughtException(err, true /* fromPromise */); ^ [Error: ENOENT: no such file or directory, mkdir '/root/.config'] { errno: -2, code: 'ENOENT', syscall: 'mkdir', path: '/root/.config' } 
 





