PeerTube CLI

[imc67]

@girish I uploaded (via YT URL) 1 video just to test. Then discovered the, for us blocking issues and since then waiting for the update.

However, I remember that importing a YT playlist by URL didn’t seem to work (nothing happened). So I really prefer a build in CLI to do this.

[imc67]

@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

[girish]

@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.

[rmdes]

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

from : https://github.com/Chocobozzz/PeerTube/issues/3121

[imc67]

@girish friendly reminder

[girish]

@imc67 I pushed a new package with youtube-dl and the CLI installed. Do you require the cron support?

[imc67]

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-0347662bb45f

but this error returns:

sudo: npm: command not found

Is the path in the command ok?

[nebulon]

peertube as many other apps should ideally run with the cloudron user, so maybe try that user instead of root.

[imc67]

@nebulon same result

sudo -u cloudron NODE_CONFIG_DIR=/var/www/peertube/config NODE_ENV=production npm run create-transcoding-job -- -v db21c654-6ca3-470e-b6a0-0f31bbcb3c37
sudo: npm: command not found

[nebulon]

Ah sudo apparently does not carry over the env bits for this. So instead use gosu cloudron:cloudron npm ... that should do.

[imc67]

@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

[nebulon]

NODE_CONFIG_DIR is already properly set in the environment pointing to /app/code/server/config so remove that from your commandline.

[imc67]

@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.

[girish]

All my docs go unread it's just peertube

[nebulon]

Oh haha, great https://docs.cloudron.io/apps/peertube/

[imc67]

@girish stupid me!

[rmdes]

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

[robi]

@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?

[rmdes]

@robi I have no idea about all 3 questions

[rmdes]

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 get

peertube 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 required

Anything changed perhaps for the cli & latest peertube version ?