by Luc Saffre · in Developers · assigned to Luc Saffre

Résumé

Concepts sous-jacents

Commentaires

• 1 année, 6 mois ago by Luc Saffre about #5043 (Each modification to settings.py requires pm buildcache) : I released to pypi and upgraded fijal. Everything seems okay. I close this ticket.
• 1 année, 6 mois ago by Luc Saffre about #5043 (Each modification to settings.py requires pm buildcache) : The test suite passed. I'll commit my changes without documentation because I'd like to see whether it passes on GL as well. And then I'll test it on fijal, too. I'm surprised that the solution is so simple...
• 1 année, 6 mois ago by Luc Saffre about #5043 (Each modification to settings.py requires pm buildcache) : Okay I'm not a good leader: rather than delegating it to @8lurry I did it myself (or at least I think so... the test suite is still running).
• 1 année, 6 mois ago by Luc Saffre about #5043 (Each modification to settings.py requires pm buildcache) (1 reply) : Right now I often have the silly situation that I need to run buildcache just because i changed some Peppol setting in the settings.py. AFAICS a simple solution would be to use the timestamp of the lino_cache.txt file and not of the settings.py file.
• 3 ans, 3 mois ago by Luc Saffre about #5043 (Each modification to settings.py requires pm buildcache) : Sharif and Luc have been digging a bit into this. It is not trivial...
• 3 ans, 3 mois ago by Luc Saffre about #5043 (Each modification to settings.py requires pm buildcache) : Changes in the settings.py *may* require buildcache, but e.g. when I just change ALLOWED_HOSTS or ADMINS, there is no need to rebuild everything.
• 3 ans, 3 mois ago by Sharif Mehedi about #5043 (Each modification to settings.py requires pm buildcache) : changes in the settings.py may change site_data(+).
• 3 ans, 3 mois ago by Sharif Mehedi about #5043 (Each modification to settings.py requires pm buildcache) : on the other hand, running buildcache is necessary after a change in the settings.py file.
• 3 ans, 3 mois ago by Sharif Mehedi about #5043 (Each modification to settings.py requires pm buildcache) : timestamp of the main.js is independent to the timestamp of the settings.py. This feature were NOT really working until now, there was a name mismatch: see [url gitlab.com/lino-framework/react/-/commit/27cf64376bd86f963768791537b7e8dda700178d commit].
• 3 ans, 3 mois ago by Luc Saffre about #5043 (Each modification to settings.py requires pm buildcache) : This is disturbing because right now we are doning frequent minor changes to the settings.py for optimizing certain settings that are completely unrelated to the main.js file. And forgetting to run pm buildcache breaks Lino for the end users because their Lino will "blink".
• 3 ans, 3 mois ago by Luc Saffre about #5043 (Each modification to settings.py requires pm buildcache) : In order to test whether the client has an old version, Lino currently compares the timestamp stored in the main.js file with the timestamp of the settings.py file. That's nonsense. Lino should compare it to that of the main,js file on the server.
• 3 ans, 3 mois ago by Luc Saffre about #5043 (Each modification to settings.py requires pm buildcache) : Created new Ticket #5043 (Each modification to settings.py requires pm buildcache).