Closed Bug 1589137 Opened 5 years ago Closed 5 years ago

Changes to static files outside the frontend folder requiring make build

Categories

(Webtools Graveyard :: Pontoon, enhancement, P1)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: henikilana, Assigned: adrian)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.120 Safari/537.36

Steps to reproduce:

  1. Edit pontoon/base/static/css/style.css
  2. Open in browser http://localhost:8000/static/css/style.css

Actual results:

No changes in the browser.
It updates only after running "make build"

Expected results:

The file should be updated.

Thanks for the report!

:adrian, I'm having this problem as well. Do you mind having a look at this?

Flags: needinfo?(adrian)
Assignee: nobody → adrian
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Flags: needinfo?(adrian)

This is a side-effect of enabling the feature for Translate.Next. I had to use --nostatic on the runserver django command, so that I could load static files from the webpack server. But then when I do that, we do lose automatic reloading of django static files.

I'm investigating, but I guess I'll have to find a way to have the effect of the static django utility for resources that are not frontend related. Not sure if or how that's doable.

Bumping priority, because this makes development on static files outside frontend extremely slow.

Priority: -- → P1
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: