-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Development] Issue with developing locally #229
Comments
I'll try to look into a fix for this... Essentially, builds were taking far too long on Cloudflare and I was also worried about hitting storage and file count limitations on Cloudflare Pages, hence moving the audio to separate storage. You might be able to use something like Python's simple web server by running it in the
Then update the following lines: rail-announcements/src/announcement-data/AnnouncementSystem.ts Lines 153 to 155 in d9a3ac7
to: generateAudioFileUrl(fileId: string, customPrefix?: string): string {
return `http:https://localhost:9000/${customPrefix || this.FILE_PREFIX}/${this.processAudioFileId(fileId).replace(/\./g, '/')}.mp3`
} |
@davwheat And this error in the Python terminal:
|
Sorry this took so long... This should be better now from changes in 9313af4 and 58ee9b5. I've added some new info to the README for local development. In a nutshell, run these three in different terminals one after the other: yarn develop
yarn develop:workers
yarn serve-audio You can access the site on Let me know if you still have issues. |
Oh, I just broke something with my latest change. Not your fault... |
Oh, that's alright. I thought I was doing something wrong! 😂 |
That should also be fixed with the latest commit |
When I have tried to add new audio files to the site, I noticed that I get an error when I attempt to test an announcement with the audio snippet that I added.
From what I can gather, it's because the site is programmed to get the files from a CDN, which obviously doesn't contain the files that I'm adding.
Could anyone advise me on a way around this for local development and testing?
The text was updated successfully, but these errors were encountered: