You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 2, 2020. It is now read-only.
Sound URL needs to be set first so that sound files can be generated before anything else loads. A dev shouldn't need to know the IP address of their raspberry pi to have sounds work (if they're being served on local, apache server)
Right now when making any changes, we need to manually set VUE_APP_SOUND_LOCAL_URL to the raspberry pi IP address, port 80, etc., before we run npm run build. That's absurd!
A potential bad hack/viable fix is using regex on raspberry pi startup that find/replaces all localhost or whatever the Sound URL is set to, and changes it to the RPi's IP address.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Sound URL needs to be set first so that sound files can be generated before anything else loads. A dev shouldn't need to know the IP address of their raspberry pi to have sounds work (if they're being served on local, apache server)
Right now when making any changes, we need to manually set
VUE_APP_SOUND_LOCAL_URL
to the raspberry pi IP address, port 80, etc., before we runnpm run build
. That's absurd!A potential bad hack/viable fix is using regex on raspberry pi startup that find/replaces all
localhost
or whatever the Sound URL is set to, and changes it to the RPi's IP address.The text was updated successfully, but these errors were encountered: