Project

General

Profile

Feature #7458

Automatically update changed JavaScripts

Added by Evgeny Novikov over 3 years ago. Updated 8 days ago.

Status:
Resolved
Priority:
Urgent
Category:
Bridge
Target version:
Start date:
08/09/2016
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

Now if Bridge comes with some new JavaScripts they aren't automatically updated and browser caches keep the old ones until they will be cleaned up somehow. I am not sure whether the development Django web server or/and Apache are responsible for this.


Related issues

Related to Klever - Feature #7388: Always show line numbers for error traces and source filesClosed07/11/201608/02/2016

Actions
Blocks Klever - Feature #9897: Develop tutorialNew10/30/2019

Actions

History

#1

Updated by Vladimir Gratinskiy almost 3 years ago

  • Status changed from New to Feedback

In most browsers you can update the page with its cache by "Ctrl+F5" (you should do it for all pages with saved cache).

The server can influence on static files caching, but I don't recommend it - I'm not going to change javascripts too often, and caching decreases page loading time.

http://staticfiles.productiondjango.com/blog/setting-up-static-file-caching/

#2

Updated by Evgeny Novikov almost 3 years ago

  • Status changed from Feedback to Open

I still suppose that the really production server, which Bridge is, has to update caches like this is done by other well known servers. Actually everybody are bothered with this issue very much. For instance, I completely switched of caches, Ilja restarts the whole web-browser when he meets unexpected things in Bridge. This does take much time after all. The only place where this issue doesn't hit is automatically deployed instances or containers, but they aren't intended to be updated at all in the most cases.

#3

Updated by Evgeny Novikov 18 days ago

  • Target version set to 3.0
  • Priority changed from High to Urgent

It turned out that there is a nice solution for this issue. Let's implement it, since scripts are updated often that can cause unpleasant consequences.

#4

Updated by Evgeny Novikov 15 days ago

#5

Updated by Evgeny Novikov 8 days ago

  • Status changed from Open to Resolved

Implemented in branch klever-3.0.

Also available in: Atom PDF