A copyright violation detector running on Wikimedia Cloud Services https://tools.wmflabs.org/copyvios/
25개 이상의 토픽을 선택하실 수 없습니다. Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

README.md 1.7 KiB

11 년 전
11 년 전
13 년 전
12345678910111213141516171819202122232425262728293031323334353637383940414243444546
  1. This is a [copyright violation](https://en.wikipedia.org/wiki/WP:COPYVIO)
  2. detector web tool for Wikipedia articles running on
  3. [Wikimedia Cloud Services](https://wikitech.wikimedia.org/wiki/Help:Cloud_Services_introduction)
  4. at [copyvios.toolforge.org](https://copyvios.toolforge.org/).
  5. It can search the web for content similar to a given article, and graphically
  6. compare an article to specific URLs. Some technical details are expanded upon
  7. [in a blog post](https://benkurtovic.com/2014/08/20/copyvio-detector.html),
  8. though much of it is outdated.
  9. Installation
  10. ============
  11. - If using Toolforge, clone the repository to `~/www/python/src`, or otherwise
  12. symlink it to that directory.
  13. - Create a virtual environment and install the dependencies. On Toolforge,
  14. this should be in `~/www/python/venv`, otherwise it can be in a subdirectory
  15. of the git project named `venv`:
  16. python3 -m venv venv
  17. . venv/bin/activate
  18. pip install -e .
  19. - If you intend to modify CSS or JS, install the frontend dependencies:
  20. npm install -g uglify-js cssnano postcss postcss-cli
  21. - Create an SQL database with the tables defined by `schema.sql`.
  22. - Create an earwigbot instance in `.earwigbot` (run `earwigbot .earwigbot`).
  23. In `.earwigbot/config.yml`, fill out the connection info for the database by
  24. adding the following to the `wiki` section:
  25. copyvios:
  26. engine: mysql
  27. host: <hostname of database server>
  28. db: <name of database>
  29. Running
  30. =======
  31. - Run `make` to minify JS and CSS files after making any frontend changes.
  32. - Start your WSGI server pointing to app:app. For production, uWSGI or
  33. Gunicorn are likely good options. For development, use `flask run`.