0
0
mirror of https://github.com/wagtail/wagtail.git synced 2024-12-01 11:41:20 +01:00
wagtail/tox.ini

50 lines
1.6 KiB
INI
Raw Normal View History

2015-04-03 15:38:08 +02:00
[tox]
skipsdist = True
usedevelop = True
2016-11-08 12:17:26 +01:00
envlist = py{27,33,34,35}-dj{18,19}-{sqlite,postgres,mysql}-{elasticsearch5,elasticsearch2,elasticsearch,noelasticsearch},
py{27,34,35}-dj{110,110head}-{sqlite,postgres,mysql}-{elasticsearch5,elasticsearch2,elasticsearch,noelasticsearch},
flake8
2015-04-03 15:38:08 +02:00
[testenv]
install_command = pip install -e ".[testing]" -U {opts} {packages}
commands =
elasticsearch: coverage run runtests.py wagtail.wagtailsearch wagtail.wagtaildocs wagtail.wagtailimages --elasticsearch
Elasticsearch 2 support (#2573) * Created Elasticsearch 2 backend * Added tests for Elasticsearch 2 backend * Split models up into different indices pages, images and documents are now in separate indices * Prefix fields of child models to prevent mapping clashes * Replaced index_analyzer with analyzer/search_analyzer index_analyzer has been removed in Elasticsearch 2.0 https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking_20_mapping_changes.html#_analyzer_mappings There's no indication in Elasticsearch's docs that this wouldn't work on Elasticsearch 1.x. However, we found that the new configuration isn't reliable on Elasticsearch 1.6 and below (causes the test_query_analyzer test to fail randomly). * Implemented new way of representing content types in search index Instead of using a long string of model names that is queried using a "prefix" query, we instead use a multi-value string field and query it using a simple "match" query. The only reason why this isn't implemented in the Elasticsearch 1.x backend yet is backwards compatibility * Added another child model of SearchTest with clashing field mapping This checks that the namespacing of fields on child models is working properly (if it doesn't the update_index tests will fail) * Added tests for get_model_root function * fixup! Added tests for get_model_root function * Docs updates for Elasticsearch 2 support Also tweak examples to use elasticsearch2 backend by default * Test against Elasticsearch 2 on travis
2016-05-06 12:23:31 +02:00
elasticsearch2: coverage run runtests.py wagtail.wagtailsearch wagtail.wagtaildocs wagtail.wagtailimages --elasticsearch2
2016-11-08 12:17:26 +01:00
elasticsearch5: coverage run runtests.py wagtail.wagtailsearch wagtail.wagtaildocs wagtail.wagtailimages --elasticsearch5
noelasticsearch: coverage run runtests.py
2015-04-03 15:38:08 +02:00
basepython =
py27: python2.7
py33: python3.3
py34: python3.4
2015-09-16 05:50:12 +02:00
py35: python3.5
2015-04-03 15:38:08 +02:00
deps =
2015-04-10 05:44:41 +02:00
django-sendfile==0.3.6
Embedly
dj18: Django>=1.8.1,<1.9
dj19: Django>=1.9,<1.10
dj110: Django>=1.10a1,<1.11
dj110head: git+https://github.com/django/django.git@stable/1.10.x#egg=Django
2015-04-03 15:38:08 +02:00
postgres: psycopg2>=2.6
mysql: mysqlclient==1.3.6
elasticsearch: elasticsearch>=1,<2
Elasticsearch 2 support (#2573) * Created Elasticsearch 2 backend * Added tests for Elasticsearch 2 backend * Split models up into different indices pages, images and documents are now in separate indices * Prefix fields of child models to prevent mapping clashes * Replaced index_analyzer with analyzer/search_analyzer index_analyzer has been removed in Elasticsearch 2.0 https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking_20_mapping_changes.html#_analyzer_mappings There's no indication in Elasticsearch's docs that this wouldn't work on Elasticsearch 1.x. However, we found that the new configuration isn't reliable on Elasticsearch 1.6 and below (causes the test_query_analyzer test to fail randomly). * Implemented new way of representing content types in search index Instead of using a long string of model names that is queried using a "prefix" query, we instead use a multi-value string field and query it using a simple "match" query. The only reason why this isn't implemented in the Elasticsearch 1.x backend yet is backwards compatibility * Added another child model of SearchTest with clashing field mapping This checks that the namespacing of fields on child models is working properly (if it doesn't the update_index tests will fail) * Added tests for get_model_root function * fixup! Added tests for get_model_root function * Docs updates for Elasticsearch 2 support Also tweak examples to use elasticsearch2 backend by default * Test against Elasticsearch 2 on travis
2016-05-06 12:23:31 +02:00
elasticsearch2: elasticsearch>=2,<3
2016-11-08 12:17:26 +01:00
elasticsearch5: elasticsearch>=5,<6
elasticsearch5: certifi
setenv =
2015-04-03 15:38:08 +02:00
postgres: DATABASE_ENGINE=django.db.backends.postgresql_psycopg2
2015-04-03 15:38:08 +02:00
mysql: DATABASE_ENGINE=django.db.backends.mysql
mysql: DATABASE_USER=wagtail
mysql: DATABASE_HOST=localhost
mysql: DATABASE_USER=root
[testenv:flake8]
basepython=python3.4
deps=flake8>=2.2.0
commands=flake8 wagtail