Fix #24, refactor URL detection
This commit is contained in:
11
README.md
11
README.md
@ -11,8 +11,8 @@ Having a quick overview over what is being posted can be a great way to discover
|
||||
|
||||
This is fairly simple from a technical point of view! metalhead.club's local timeline is being watched using the
|
||||
Mastodon Streaming API over a Websocket. Every time a new post arrives, it is checked if it contains any music by
|
||||
checking included hashtags and URLs. A list of tags and URLs can be found in [the configuration](.env.EXAMPLE).
|
||||
Additionally, lins to YouTube are queried, if they are music or other videos using the YouTube API.
|
||||
checking included hashtags and URLs. A list of tags can be found in [the configuration](.env.EXAMPLE).
|
||||
Additionally, links are vetted if they are music by checking if https://song.link finds info on them.
|
||||
|
||||
If a post passes this check it is saved to a SQLite database.
|
||||
|
||||
@ -93,11 +93,12 @@ and set your `User`, `Group`, `ExecStart` and `WorkingDirectory` accordingly.
|
||||
|
||||
#### On your development machine
|
||||
|
||||
Copy `.env.EXAMPLE` to `.env` and add your `YOUTUBE_API_KEY`.
|
||||
Copy `.env.EXAMPLE` to `.env` and add your `YOUTUBE_API_KEY` and `ODESLI_API_KEY`.
|
||||
To obtain one follow [YouTube's guide](https://developers.google.com/youtube/registering_an_application) to create an
|
||||
_API key_.
|
||||
If `YOUTUBE_API_KEY` is unset, all YouTube videos will be assumed to contain music links.
|
||||
If this is unwanted, set `YOUTUBE_DISABLE` to `true`).
|
||||
If `YOUTUBE_API_KEY` is unset, no playlist will be updated.
|
||||
|
||||
If `ODESLI_API_KEY` is unset, your rate limit to the song.link API will be lower.
|
||||
|
||||
Run `npm run build` and copy the output folder, usually `build` to `$APP_DIR` on your server.
|
||||
|
||||
|
Reference in New Issue
Block a user