'runserver': Does not re-index itself every interval.

[bnvinay92]

Auto-reviewers: @NiharikaRay @matthewwardrop @earthmancash @danfrankj

I have the knowledge server webapp deployed on an ec2 instance using sudo knowledge_repo --repo /home/ec2-user/krepo/ runserver --port 80

but when I push to this repo from elsewhere git remote add ec2 ssh://ec2-user@<ip-address>/home/ec2-user/krepo git push -f ec2 master

The web app does not re-index even after 10 minutes though I can confirm that the master branch does get updated on the ec2 instance. If I clone my git repo locally and deploy the web app(locally), it re-indexes every 5 minutes reflecting changes on master that I sync between the local repos.

The only difference between the ec2 instance and my machine is that knowledge_repo is installed in a virtualenv on ec2, but that shouldn't make a difference right?

[matthewwardrop]

Hi @bnvinay92 ,

Apologies for the delay. Which database server (MySQL, Postgres, ...) is backing the knowledge repo web app? If you haven't changed it from the default, then it will be an SQLite in-memory database, which cannot asynchronously update the index. Instead, the index will be (or should be) updated when a request hits the server. It is possible that the SQLite backend has failed for some reason, but in that case an exception should be raised. If that is the case, and you run the knowledge_repo web app with the --debug flag, you should be able to clearly see what the error is (maybe once every 5 minutes if the status can be updated but not the actual index).

Otherwise, no; installing it via a virtual environment should not make a difference.