mrlemur / bottle-radio

Radio in a bottle. All in one solution for your own radio station.

Hey friend! 👋

I'm Kassim and I make apps that I have found a need for in my day to day life.

You might have come here through some of my promoted projects:

• Bottle Radio - All in one solution for your own web radio station with auto playback and live streaming
• Park My Bike - Find bike parking infrastructure in London while on the go

Here are some stats about the languages I use:

bottle-radio's Issues

Auto update Playlists

Hello,

Thank you for this. I installed it yesterday.

I've also created an algorithm that creates Spotify playlists vis Spotify API. I ask Bottle to play this playlist.

Everything's fine except that when I update the playlist I have to log in to Iris to manually go and ask it to update it. Is there a possibility that when the spotify playlist changes, the radio adapts automatically?

Have a nice day
Alex

Is there a missing section between the end of installation and getting started?

Describe the bug
Docs go from installation to "visit spotify.your.doman/" however this fails with a 404.
The docs dont mention set up of SSL anywhere and even when going insecure it's still a 404

To Reproduce
Steps to reproduce the behavior:

1. Install
2. Try to visit https://spotify.your.domain
3. SSL warning page
4. Click through "unsafe" and you get a 404

Expected behavior
I expected the set up page to load

Screenshots

Desktop (please complete the following information):

• OS: Win 10
• Browser Chrome
• Version latest

Docker-Compose up fails with: Error: error:0308010C:digital envelope routines::unsupported

Hello!

Bottle Radio is exactly what I have been looking for after going down the same road with Azuracast than you did - I really appreciate your description :) Unfortunately it took me over a year to find this repo, and it seems there are some issues I am unable to solve. They are all related to the installation of the components used failing. I am not a developer but I am running my fair share of docker-deployed services, so I assume this compose script requires a little more knowledge than described in your installation guide. Or it is simply outdated.

This has been verified on three of my VPS (2x 20.04, 1x 18. 04). By just following your install instructions, docker-compose up fails with:

Building frontend
Step 1/16 : FROM node:alpine as builder
alpine: Pulling from library/node
97518928ae5f: Already exists
4796d9078153: Pull complete
c3cb450ea517: Pull complete
dc9de54e9683: Pull complete
Digest: sha256:e64dc950217610c86f29aef803b123e1b6a4a372d6fa4bcf71f9ddcbd39eba5c
Status: Downloaded newer image for node:alpine
 ---> bb1fcdaff936
Step 2/16 : WORKDIR /app
 ---> Running in adc96fe3d4b2
Removing intermediate container adc96fe3d4b2
 ---> 8a31341c92ff
Step 3/16 : COPY package.json .
 ---> 314398f99893
Step 4/16 : COPY yarn.lock .
 ---> 563f211c8248
Step 5/16 : RUN yarn
 ---> Running in cdeb18573813
yarn install v1.22.15
[1/4] Resolving packages...
[2/4] Fetching packages...
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning "@emotion/styled > @emotion/[email protected]" has unmet peer dependency "@babel/core@^7.0.0".
warning "@emotion/styled > @emotion/babel-plugin > @babel/[email protected]" has unmet peer dependency "@babel/core@^7.0.0-0".
warning " > @testing-library/[email protected]" has unmet peer dependency "@testing-library/dom@>=7.21.4".
warning "react-scripts > @typescript-eslint/eslint-plugin > [email protected]" has unmet peer dependency "typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta".
[4/4] Building fresh packages...
Done in 70.39s.
Removing intermediate container cdeb18573813
 ---> 86cd90de1149
Step 6/16 : COPY . .
 ---> d7f65d513081
Step 7/16 : RUN yarn build
 ---> Running in 3ad84968c56f
yarn run v1.22.15
$ react-scripts build
Creating an optimized production build...
Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:67:19)
    at Object.createHash (node:crypto:130:10)
    at module.exports (/app/node_modules/webpack/lib/util/createHash.js:135:53)
    at NormalModule._initBuildHash (/app/node_modules/webpack/lib/NormalModule.js:417:16)
    at handleParseError (/app/node_modules/webpack/lib/NormalModule.js:471:10)
    at /app/node_modules/webpack/lib/NormalModule.js:503:5
    at /app/node_modules/webpack/lib/NormalModule.js:358:12
    at /app/node_modules/loader-runner/lib/LoaderRunner.js:373:3
    at iterateNormalLoaders (/app/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
    at iterateNormalLoaders (/app/node_modules/loader-runner/lib/LoaderRunner.js:221:10)
    at /app/node_modules/loader-runner/lib/LoaderRunner.js:236:3
    at runSyncOrAsync (/app/node_modules/loader-runner/lib/LoaderRunner.js:130:11)
    at iterateNormalLoaders (/app/node_modules/loader-runner/lib/LoaderRunner.js:232:2)
    at Array.<anonymous> (/app/node_modules/loader-runner/lib/LoaderRunner.js:205:4)
    at Storage.finished (/app/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:55:16)
    at /app/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:91:9
/app/node_modules/react-scripts/scripts/build.js:19
  throw err;
  ^

Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:67:19)
    at Object.createHash (node:crypto:130:10)
    at module.exports (/app/node_modules/webpack/lib/util/createHash.js:135:53)
    at NormalModule._initBuildHash (/app/node_modules/webpack/lib/NormalModule.js:417:16)
    at /app/node_modules/webpack/lib/NormalModule.js:452:10
    at /app/node_modules/webpack/lib/NormalModule.js:323:13
    at /app/node_modules/loader-runner/lib/LoaderRunner.js:367:11
    at /app/node_modules/loader-runner/lib/LoaderRunner.js:233:18
    at context.callback (/app/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
    at /app/node_modules/react-scripts/node_modules/babel-loader/lib/index.js:59:103 {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v17.2.0
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: Service 'frontend' failed to build: The command '/bin/sh -c yarn build' returned a non-zero code: 1

I have researched this error and it seems to be quite common when compiling nodejs projects (webpack/webpack#14532). So I tried putting the "--openssl-legacy-provider" into the package.json react script build reference, and it actually worked - only to be stopped when installing Mopidy:

`Step 4/18 : RUN apt-get update     && apt-get install -y     dumb-init     graphviz-dev     gstreamer1.0-plugins-bad     gstreamer1.0-plugins-good     gstreamer1.0-plugins-ugly     gstreamer1.0-pulseaudio     libasound2-dev     python-dev     python-gst-1.0     python3-gst-1.0     && rm -rf /var/lib/apt/lists/*
 ---> Running in 3d184dc0d078
Get:1 http://deb.debian.org/debian buster InRelease [122 kB]
Get:2 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Get:3 http://deb.debian.org/debian buster-updates InRelease [51.9 kB]
Reading package lists...
E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
E: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
E: Repository 'http://deb.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'
ERROR: Service 'mopidy' failed to build: The command '/bin/sh -c apt-get update     && apt-get install -y     dumb-init     graphviz-dev     gstreamer1.0-plugins-bad     gstreamer1.0-plugins-good     gstreamer1.0-plugins-ugly     gstreamer1.0-pulseaudio     libasound2-dev     python-dev     python-gst-1.0     python3-gst-1.0     && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100
`

So yeah, it seems to be pretty broken atm. Or I am missing something. Please help me out!

Mopify-Spotify not running

Running Ubuntu 21.10

Mopify logs in but I am unable to browse spotify through the web interface

It also appears to not want to connect to a server

Ive redo authentication with the plugin but and restarted the docker container but no luck. Just running locally with no SSL cert

[Mopidy: Failed to add some tracks]

I have installed the mopidy Container alone
and i inserted all Variables from Spotify.
Added my own Icecast Server for Playout.

When i click on a song or Playlist, i get the Error:
Mopidy: Failed to add some tracks

Any Help for this Issue?

[SPOTIFY] - Spotify has stopped supporting libspotifyd - can no longer login

Ref: https://discourse.mopidy.com/t/spotify-login-error-errortype-user-needs-premium-15/5459/22

At the moment, Bottle Radio will probably stop working as this is needed for the connection to Spotify :(

I'll be looking to expand the services we ca use.

Use Typescript

Use typescript. <3

Local Files

Hi there,

Just wondering if bottle radio would be able to play local files? Basically the same thing as it does now just with local files instead of using Spotify.

Thanks!

Is there available a backend management demo?

i.e. AzuraCast has web-based panel, from where people manages everything (station, account, settings..), and its demo is available.
Is anything similar available for bottleratio, so we could see how backend management panel looks like?