automatic reindexing on doctree.org + automatic migrations

[emidoots]

Automatic migrations

Before this change, if say the Python indexer improved and you launched a new version of doctree you would need to reindex your projects to see the improvement.

Similarly, if the doctree schema format changes, you might see errors until you reindex your projects.

Now when we improve indexers, add new indexers, change the schema format, etc. we just bump indexer.projectDirVersion and then on startup you'll see:

2022/05/30 17:58:00 migration: doctree schema has changed, removing: github.com/Sobeston/ziglearn
2022/05/30 17:58:00 migration: doctree schema has changed, removing: github.com/django/django
2022/05/30 17:58:00 migration: doctree schema has changed, removing: github.com/golang/go
2022/05/30 17:58:00 migration: doctree schema has changed, removing: github.com/gorilla/mux
2022/05/30 17:58:00 migration: doctree schema has changed, removing: github.com/hexops/mach
2022/05/30 17:58:00 migration: doctree schema has changed, removing: github.com/sourcegraph/sourcegraph

If you used auto indexing to add the projects, they should be auto-indexed again. If not, you'll need to rerun doctree index . on them - it's now clear you need to do so.

In cloud mode, it will automatically reclone the repository and index it (since we know the source.)

Automatic reindexing on doctree.org

Right now the repositories on doctree.org can become quite out of date, since they only index once (and when I redeploy the site.) Now there is a silly for loop here that will reindex them when new commits are pushed to the Git repos - so they should pretty much always be up to date now.

• By selecting this checkbox, I agree to license my contributions to this project under the license(s) described in the LICENSE file, and I have the right to do so or have received
  permission to do so by an employer or client I am producing work for whom has this right.