Commit Graph

25 Commits

Author SHA1 Message Date
Matthew Foster Walsh
10c85ce3d6
Rename docker compose files to include 'docker-compose' (#4995)
* Renamed local.yml to docker-compose.local.yml

* Renamed production.yml to docker-compose.production.yml

* Rename docs.yml to docker-compose.docs.yml

* [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: Bruno Alla <alla.brunoo@gmail.com>
2024-05-13 18:18:56 +01:00
Jelmer
3b3cf416f3
Merge pull request #4930 from foarsitter/py312
Upgrade Python to version 3.12
2024-03-19 10:41:04 +01:00
Shayan Karimi
a1d34a08af
Split the docs from local.yml and build the service in CI (#4909)
* Split the docs from local.yml and build the service in CI

* Change docs build in our CI docker tests
2024-03-18 19:26:18 +00:00
Jelmer Draaijer
b488056b63 Upgrade Python to version 3.12 2024-03-18 20:07:24 +01:00
Jelmer Draaijer
6ba6104f09 Ruff as formatter & linter 2024-02-13 11:59:54 +01:00
Imran Rahman
f567b5f685
update docs docker-compose -> docker compose (#4463)
Co-authored-by: Imran Rahman <imranrahman.ix@gmail.com>
2023-07-24 10:42:51 +01:00
Jelmer
42c30dafcb
Upgrade Python to version 3.11 (Faster CPython) (#4256)
* Upgrade Python to version 3.11 (Faster CPython)

* Update pyupgrade config for Python 3.11

* Update tox env to Python 3.11

* Update to latest Python 3.11.3

* Add a note about lack of support in PythonAnywhere

* Rephrase note

* Fix casing

---------

Co-authored-by: Bruno Alla <alla.brunoo@gmail.com>
Co-authored-by: Bruno Alla <browniebroke@users.noreply.github.com>
2023-04-15 11:42:33 +01:00
Jelmer
4ea0e98f3f
Upgrade Python version from 3.9 to 3.10 (#3913) 2022-10-24 21:41:00 +01:00
areski
a1d551d067 Update from Python3.8 to Python3.9 2021-01-26 16:13:27 +01:00
Andrew Chen Wang
e83933ae7a
Upgrade Travis to Focal 2021-01-07 22:34:39 -05:00
Andrew-Chen-Wang
d249158444 Fix .travis.yml indent alignment 2020-04-16 14:15:35 -04:00
Andrew-Chen-Wang
d2285d9e2d pytest.parametrized test for generating CI
* Removed celerybeat start's postgres_ready() for new PR for closer inspection and further review. Travis and GitLab CI reflect changes
2020-04-16 13:34:12 -04:00
Andrew Chen Wang
9e007699c9
Merge branch 'master' into ci 2020-04-14 11:55:01 -04:00
Andrew-Chen-Wang
3c63b3e46e Add Docker support to Travis and GitLab CI
* Celerybeat start files wait for table migration so that errors don't occur if a migration does not happen post-build
2020-04-14 11:52:14 -04:00
Ernesto Cedeno
0cdf60ceac Change Python version to 3.8 2020-03-29 19:55:27 +02:00
Nicolas Stefani
1f68e370ee Updated python version to 3.7 2019-09-29 21:07:59 -03:00
Bruno Alla
6f9e57618d
Add Postgres service to Travis config 2019-06-06 17:23:37 +01:00
Xaver Y.R. Chen
611373cac2 Update Travis config, remove the deprecated sudo keyword 2019-06-06 14:48:48 +08:00
Xaver Y.R. Chen
ef59ffad94 Update Travis config, using new xenial distribution to support the newer version of SQLite to satisfy the requirement of Django 2.2 2019-06-05 20:21:37 +08:00
btknu
6e72169ffe Add missing script key to Travis CI config (#1950)
* Add failing test for travis.yml

I see three options to test travis.yml :

1. Testing that the YAML contains relevant value. Least useful and least
reliable, but simplest to implement.

2. Testing that the YAML is valid TravisCI YAML. Unfortunately this is
difficult / impossible. Doing 'travis lint' would succeed, this command
does not check for 'script' key presence and wouldn't be useful for us.

We could use 'travis-build' to verify that the YAML can be converted to
a worker config, but as of now 'travis-build' doesn't work out of the
box.

There is a new tool for validating travis YAML files 'travis-yml', but
as of now it's a ruby-only library and it's still a work in progress.

3. Running Travis CI task based on the generated YAML. This seems the
best approach, however since cookiecutter-django itself uses Travis CI,
that would require running Travis CI from within Travis CI.

Scheduling Travis CI job without a github push still requires a public
github repo, which is something that we can't generate on demand.

Given that I'm opting to use approach 1.

* Adds missing config to generated .travis.yml

The keys added are as follows:

1. 'script'

Required by Travis, cookiecutter-django used to provide it until it has
been removed together with hitch.

I'm assuming hitch has been replaced with pytest, I'm setting pytest as
the new value for the 'script' key.

2. 'install'

Not required by Travis, but necessary in our case; installs test
libraries, mostly pytest.

As of now this points to 'local.txt' requirements file. There used to be
a separate 'test.txt' requirements file but it has been decided to merge
it with 'local.txt', see discussion in
https://github.com/pydanny/cookiecutter-django/pull/1557 .

* Update CONTRIBUTORS.rst
2019-03-05 22:10:45 -03:00
Reggie Riser
f7bd7a5814 Fixing leftovers from migration to Django 1.11 and Python 3.6. 2018-01-03 08:44:54 -05:00
Daniel Roy Greenfeld
6aced9ba73 Remove Python 2.7 support per #1129 (#1130)
* Remove Python 2.7 support per

* Remove Python 2.7 references

* Remove Python 2.7 references

* remove python 2 entirely
2017-04-21 12:31:45 -07:00
Andreas Meistad
41059ff4df Change use_python2 [N] to use_python3 [Y]
Fixes #747
2016-08-21 22:11:01 +02:00
Daniel Roy Greenfeld
7dad5ac667 Removed Hitch per #529 2016-04-25 23:11:17 -07:00
Audrey Roy Greenfeld
15f350f05e Change repo_name to project_slug for clarity. 2016-04-20 10:00:35 -07:00