p0psicles
commented
3 years ago Few releases ago we started using the browsers localStorage cache to cache the shows. As you have everything set up under the same domain its overwriting the same cache.
Closed mysterfr closed 3 years ago
p0psicles
commented
3 years ago Few releases ago we started using the browsers localStorage cache to cache the shows. As you have everything set up under the same domain its overwriting the same cache.
p0psicles
commented
3 years ago You could work around it by using virtual servers. Like https://medusa.host/ and https://medusafr.host/
mysterfr
commented
3 years ago Thanks for your feedback.
Unfortunately, at the moment, that's not an option in my setup, but I'll keep that in mind.
Just out of curiosity, would the new Firefox "Fission" mode be any help in this situation, or doesn't change anything with regards to the localStorage cache.
Answering myself : NO Firefox Fission mode only segregate tabs in differents processes with dedicate memory pages, that doesn't change the browser local storage usage.
BenjV
commented
3 years ago As a workaround you could use a different browsers for every medusa instance. For example Chrome, Firefox and Brave.
Or use a browser that can start different instances and not using the tabbed function.
p0psicles
commented
3 years ago Just curious. Why isn't virtual servers an option? Your already using nginx. And setting up virtual servers in nginx is not that different from the setup you have now
mysterfr
commented
3 years ago @p0psicles it's definitely a valid technical option. I'll definitely end up reworking my setup to have dedicated virtual servers per Medusa instance as you recommended.
My setup is behind a pfSense with HAProxy which also handles the SSL offloading. It then dispatches traffic to the appropriate hosts inside my network, so there's also a bit of work at the HAProxy level + extra ACME certs to be handled/generated/renewed. So instead of having HAProxy and ACME handle the "my.host" SSL cert, it will have to handle 3 additional certs, dedicated to the Medusa instances (to ease my OCDs, I'll have all 3 instances under their dedicated virtual hosts :) ).
It's just that for the coming weeks I don't have time to fiddle with this :D. OR you can put that on my lazyness if you prefer ;).
It's also because of my habits, I have all my seedbox related stuff under https://my.host/WHATEVER And you know how habits are the most difficult thing to change...
That being said, thanks to you I have a good understanding on the reason why my browsers behave this way, and the solution is clear to me. And this is definitely not a bug but rather related to my setup (and I guess I might not be the only one in this situation ?).
p0psicles
commented
3 years ago Given it some thinking. I might be able to namespace the cache if the webroot is set
Describe the bug I'm running 3 Medusa instances, all served by nginx through reverse proxies :
This setup is now almost a year old, and all 3 instances get regularly updated to the latest version (at the time of opening this bug, all 3 instances run v0.5.12.) All instances have dedicated configuration folders (I especially doubled checked my docker container mounted volumes to make sure). Regular instance config : /opt/medusa/ VOSTFR container : /homedir/.medusa-vostr/ mounted as /config in the medusa-vostfr container FRENCH container : /homedir/.medisa-fr/ mounted as /config in the medusa-fr container
The main.db files in each folder show different sizes, expected as well:
What's wrong/how to reproduce I have three tabs opened on my browser, each of them displaying one of the 3 instances. Whichever tab I pick, the shows list contains ALL shows, from all 3 instances, listed.
Then, I switch to the tab of another instance, and I have to repeat the above steps to get the actual shows list for that instance. That is :
Phase 2 : I clear my browser's cache, and browse the "regular" instance (it's the one containing the highest number of shows). Show list is correct. I open a new tab with one of the other two instances : that instance's shows get displayed, mixed up with shows from the other instance. I go through my workaround described above, and finally get the proper shows list for that instance.
Expected behavior I would expect every instance tab to only show that instance's shows list.
Medusa (please complete the following information): REGULAR :
DOCKER:
I have provided the debug logs, but they do not contain anything relevant to my issue. It seems to be a browser/browser cache issue to me.
Debug logs (at least 50 lines): General > Advanced Settings > Enable debug
Additional context It seems to me this odd behavior appeared from version 0.5.9 or 0.5.10 (can't tell for sure). I also have the feeling that this more related to some browser caching issue than the actual medusa code. I have reproduced the issue after clearing cache, and also when using private browsing mode.
=> Are the Medusa cached objects properly segregated when using multiple instances ? for instance, are objects only linked to the host URL (https://my.host) or the full path (https://my.host/medusa, https://my.host/medusafr, and so on ?)