Hey guys, a little cry of a desperation and call for help for you all :)
So, after many weeks of developing my first webapp with Sapper I'm ready to host it and to go live. It took me a few hours to deploy it on my first ever DO droplet (generally speaking everything is my first time/experience in this case). So, I have this audio player for listening music and I thought that for now I could keep all my audio files in "static" folder and later as the number of files grows I would just move them to my backend and serve them from there. What I didn't anticipate that Service Worker is loading all the static files at once, for caching and offline usage. I didn't notice this when developing from localhost (serving local files ofc is super fast) but once I went online, omg, every new user would have to wait until 80+ audio files are loaded in the browser and cached.
1. What are my options here? As I want to launch asap, can I disable this somehow or the only way is actually to move all those files to backend and serve them from there?
Another question, a bit offtopic and silly (first time going live, remember) is it okay to have a such structer for the API and frontend app -
https://domain.com/api/blablaor there is actually a way to set up Nginx so my Sapper app connects to API on localhost without publicly opening it?
In first case how this works for crawling engines and SEO, do I have to simply close the API url in my robots.txt?
Thanks everyone! :)