Forums

As of right now, my webapp is serving files from old versions. No matter what I do, what changes I make, whether or not I completely delete everything and re-clone it after deleting the webapp, I am still somehow serving files that not only no longer exist, but are even overwritten on my end. From what I can tell, I would have to rename almost everything in order to make an effective change. It's kind of crazy that this issue has effectively bricked any app updates. Just wipe all my files and whatever cache you have of old versions you have. Starting over from absolutely nothing would be appreciated because the more I dig the more I realize how many files I just cant refresh or update.

I assume you are reloading the web app on the Web page after you make changes to the source code, right? Did you try on different browsers / incognito window? Maybe it's a caching issue in your browser? Otherwise we'd need more specific description of the issue (e.g. a url to check against and source file path) to be able to debug.

Refreshing the page is kind of a given. Tried with different browsers and incognito. I resolved the issue and got to update with my bugfix, but it was definitely weird. Your end not only managed to serve old versions of a file called graph.js, but I went as far as completely deleting the file and refreshing the webapp in config just to see what would happen and it served the deleted file. My guess is it was just a server-side cache that refused to update and the files were pulled from that cache.

My solution was deleting the old file, using touch in the bash console to create a file under the same name, then I went in to the file editor, saved, and reloaded the file, that finally forced the cache to update. I then copied the contents of the updated graph.js to the file and it finally served the updated version

There is no caching on our side, to it sounds like caching in your browser. Did you do hard reload there?

Nope, cache remained in tact on my end. The new version is now being served after deleting the original, then using touch to create a file under the same name, and saving it while empty. I checked the site and it immediately caused it to deliver the empty file instead of the deprecated version. Once I saw that worked, I just copied the contents of the new version to that file and it updated immediately with that new version. Do you use docker on your end?

No, we don't use docker for our web apps. It is still not clear to me whether you tried accessing the page in a different browser or clearing your browser cache?