CORS problem about generative.fm HOT 7 CLOSED

Hi @LawlietZe, this was done intentionally to help with costs, traffic recently increased quite a bit:

I had always intended to setup a method of fetching the files locally during development but just hadn't gotten around to it yet. Hopefully I can get that added this week; I'll use this issue to track the work. Thanks!

from generative.fm.

@metalex9 Yes, I deployed the code to another computer on the LAN.

My workaround is to copy the whole public folder from samples.generative.fm into generative.fm.
And change the DEFAULT_ENDPOINT in node_modules/@generative-music/samples.generative.fm/browser-client.js to public . Now it works.😋

from generative.fm.

@metalex9 thank you !

from generative.fm.

See the readme for updated instructions!

from generative.fm.

Also see #48, not sure why I didn't just do it this way from the beginning.

from generative.fm.

@metalex9
Hi, thanks for your awesome works.
I still can't figure out how to run the generative.fm locally. I have pull the samples.generative.fm and built the samples but still got the CROS error when I tried to play the music.

from generative.fm.

@imyhxy Any chance you're not hosting the site at localhost? For now, you must access the site at localhost:<some port> for this to work, though I have a change sitting in the develop branch which will fetch local samples for any host other than my production and staging hosts.

Otherwise, ensure your directory for samples.generative.fm is directly adjacent to the directory for generative.fm. If the build process can't find the local sample files, a message is output before webpack's output when you run npm start or npm run build which will show you where it's looking for sample files.

from generative.fm.