0bdc9fef5c
(Most of this work was done by acrefoot in an earlier branch.
I took over the branch to fix casper tests that were broken during
the upgrade (which were fixed in a different commit). I also
made most of the changes to run-casper.)
This also upgrades phantomjs to 2.1.7.
The huge structural change here is that we no longer vendor casperjs
or download phantomjs with our own script. Instead, we just use
casperjs and phantomjs from npm, via package.json.
Another thing that we do now is run casperjs tests individually, so
that we don't get strange test flakes from test interactions. (Tests
can still influence each other in terms of changing data, since we
don't yet have code to clear the test database in between tests.)
A lot of this diff is just removing files and obsolete configurations.
The main new piece is in package.json, which causes npm to install the
new version.
Also, run-casper now runs files individually, as mentioned above.
We had vendored casperjs in the past. I didn't bring over any of our
changes. Some of the changes were performance-related (primarily
|
||
|---|---|---|
| .. | ||
| _static | ||
| images | ||
| .gitignore | ||
| Makefile | ||
| README.md | ||
| THIRDPARTY | ||
| architecture-overview.md | ||
| brief-install-vagrant-dev.md | ||
| changelog.md | ||
| code-style.md | ||
| conf.py | ||
| conversion.md | ||
| custom-apps.md | ||
| dev-env-first-time-contributors.md | ||
| dev-overview.md | ||
| directory-structure.md | ||
| front-end-build-process.md | ||
| full-text-search.md | ||
| html_css.md | ||
| html_unescape.py | ||
| index.rst | ||
| install-docker-dev.md | ||
| install-generic-unix-dev.md | ||
| install-ubuntu-without-vagrant-dev.md | ||
| integration-guide.md | ||
| life-of-a-request.md | ||
| linters.md | ||
| logging.md | ||
| markdown.md | ||
| migration-renumbering.md | ||
| mypy.md | ||
| new-feature-tutorial.md | ||
| pointer.md | ||
| prod-authentication-methods.md | ||
| prod-customize.md | ||
| prod-install.md | ||
| prod-maintain-secure-upgrade.md | ||
| prod-postgres.md | ||
| prod-requirements.md | ||
| prod-troubleshooting.md | ||
| queuing.md | ||
| readme-symlink.md | ||
| requirements.readthedocs.txt | ||
| roadmap.md | ||
| schema-migrations.md | ||
| settings.md | ||
| ssl-certificates.md | ||
| testing-with-casper.md | ||
| testing-with-django.md | ||
| testing-with-node.md | ||
| testing.md | ||
| translating.md | ||
| using-dev-environment.md | ||
| version-control.md | ||
| writing-views.md | ||
README.md
Documentation
These docs are written in Commonmark Markdown with a small bit of rST. We've chosen Markdown because it is easy to write. The docs are served in production at zulip.readthedocs.io.
If you want to build the documentation locally (e.g. to test your changes), the dependencies are automatically installed as part of Zulip development environment provisioning, and you can build the documentation using:
cd docs/
make html
and then opening file:///path/to/zulip/docs/_build/html/index.html in
your browser (you can also use e.g. firefox docs/_build/html/index.html from the root of your Zulip checkout).
If you are introducing a new section into the table of contents,
you will want to modify docs/index.rst and run make clean before
make html, so that other docs besides your new one also get the
new entry in the table of contents.
You can also usually test your changes by pushing a branch to GitHub and looking at the content on the GitHub web UI, since GitHub renders Markdown.
When editing dependencies for the Zulip documentation, you should edit
requirements/docs.txt (which is used by ReadTheDocs to build the
documentation quickly, without installing all of Zulip's dependencies).