YouTube-operational-API
YouTube-operational-API copied to clipboard
Use relative path, organize folders for `ytPrivate` as they are for real or use a `.htaccess` to deny the direct access/use from end-users?
Line raising a problem as it is only Apache 2 compliant AFAIK.
Solving this issue should solve the following nonsense on index.php while the keys.txt file isn't existing/accessible where the API looks for it, as current state:
Currently this service is powered by 1 keys.
Linked to #24.
Making metrics/ part of the git would make sense to kill two birds with one stone. By the way advertising the metrics on the homepage may makes sense.
Maybe moving keys.txt from ytPrivate/ to noKey/ would make sense.
Renaming to private/ and possibly getting rid of ytPrivate/ would be nice.