-
-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to test front-end changes? #8
Comments
Here's what I've been doing:
I run that script inside the |
update: make sure you restart uWSGI after this (or just restart the whole kpi container). also, purge
|
here's a script that takes advantage of the up-to-date files in the most recently built Docker image instead of calling (moved to gist) |
@jnm what about calling your script in the |
Sounds good! |
I would like to test front-end changes to KPI code, e.g. while reviewing PRs. I do not want to use
npm run watch
, because no production build uses this. I would prefer not to have to rebuild and recreate all containers each time I change something in KPI, because this is slow (in excess of 3.5 minutes on my machine).Here's what I tried, to no avail:
kobo-install
;run.py
, instructing it to use developer mode and giving it the paths to the KPI and KoBoCAT source directories I'd just cloned;run.py --build-kpi
;run.py
again, which recreated all containers;❓ Am I doing something wrong, or am I trying to do something we haven't made possible yet?
Here is the (very long) transcript of my shell session:
Starting fresh and cloning the source repositories:
Cloning and running
kobo-install
:Looking for the string
creating your first project
, which I will later change:I make the following change to KPI, outside this shell:
Rebuilding KPI and seeing if the change made it through:
Since no results were found after rebuilding KPI, I'm now using
run.py
with no arguments to recreate all containers:Now looking again for my modification in the compiled static files:
Since there are still no results, here's a sanity check in the source directory:
In case it's helpful: run.conf (formatted).zip
The text was updated successfully, but these errors were encountered: