dojo/tootube
1
0
Fork 0
mirror of https://framagit.org/veretcle/tootube.git synced 2025-07-20 20:41:17 +02:00
Code Issues Packages Projects Releases Wiki Activity

Revert "Merge branch 'register_function' into 'master'"

Browse Source 
This reverts merge request !7
This commit is contained in:
VC
2023-10-14 17:15:34 +00:00
parent 9ca27a262f
commit 3d9ebcc2a5
6 changed files with 44 additions and 125 deletions
Download Patch File Download Diff File Expand all files Collapse all files

41
README.md
View File

@@ -8,45 +8,48 @@ This is an early prototype not really suited for production purposes for now:
* it still relies way too much on pre-determined value to upload the video to YouTube
* it cannot determine the playlists it needs to put them in
* it cannot determine the recording date (believe me, I tried!)
* there are still a lot of static values that I would rather not have static (like the cache directory…)
* it is 100% sync, meaning it’s clearly not optimal for now and probably won’t be for the next releases
So consider this a work in progress that will slowly get better with time.
So consider this a work in progress that will slowly get better with time
# What does it do exactly?
* it retrieves the latest PeerTube video download URL from an instance
* it creates a resumable upload into the target YouTube account
* it downloads/uploads the latest PeerTube video to YouTube without using a cache (stream-to-stream)
* it downloads the latest PeerTube video from an instance
* stores it in cache directory
* uploads it to YouTube
# What doesn’t it do exactly?
* it cannot register the original key (see below)
* it relies on a local cache despite the fact that it might well be possible to just download from PT/upload to YT at the same time (I don’t see why not in fact)
* it doesn’t retrieve ALL the original PeerTube video properties like licences, languages, categories, etc… again: early prototype
# Obtain Authorization Token from Google
The complicated part:
* create an OAuth2.0 application with authorization for Youtube DATA Api v3 Upload and Youtube DATA Api v3 (generally referenced as `../auth/youtube.upload` and `../auth/youtube`)
That the complicated part:
* create an OAuth2.0 application with authorization for Youtube DATA Api v3 Upload
* create a OAuth2.0 client with Desktop client
You’ll need:
* the `client_id` from your OAuth2.0 client
* the `client_secret` from you OAuth2.0 client
Create your `tootube.toml` config file:
Then enter in:
```toml
[peertube]
base_url="https://p.nintendojo.fr"
[youtube]
refresh_token="" # leave empty for now
client_id="<YOUR CLIENT_ID>"
client_secret="<YOUR CLIENT_SECRET>"
```
https://accounts.google.com/o/oauth2/v2/auth?client_id=XXX.apps.googleusercontent.com&redirect_uri=urn:ietf:wg:oauth:2.0:oob&scope=https://www.googleapis.com/auth/youtube.upload&response_type=code
```
Then run:
And accept that your YouTube account might be modified. You’ll get a code then; enter this `curl` post:
```bash
tootube register --config <PATH TO YOUR TOOTUBE.TOML FILE>
```
curl -s \
--request POST \
--data "code=[THE_CODE]&client_id=XXX.apps.googleusercontent.com&client_secret=[THE_CLIENT_SECRET]&redirect_uri=urn:ietf:wg:oauth:2.0:oob&grant_type=authorization_code" \
https://accounts.google.com/o/oauth2/token
```
You’ll be then prompted with all the necessary information to register `tootube`. You’ll end with a `refresh_token` that you can now paste inside your tootube configuration.
You’ll get a Token. The only important part is the `refresh_token`
In your `tootube.toml` config file, put the `refresh_token`.