- 04 Mar, 2021 1 commit
-
-
Neil Hanlon authored
-
- 30 Jan, 2021 1 commit
-
-
Neil Hanlon authored
-
- 16 Jan, 2021 8 commits
-
-
Florian Haas authored
-
Florian Haas authored
-
Florian Haas authored
-
Florian Haas authored
-
Florian Haas authored
In these cases, we actually want to conditionally reload the daemon at that stage in the play, not in a handler at the end.
-
Florian Haas authored
In this case, we are not using any of the special features of shell, so command will do just fine.
-
Florian Haas authored
In these instances, there is no good way to shorten the line, so leave them as-is.
-
Florian Haas authored
Skip the following rules: - 106, "Role name does not match ^[a-z][a-z0-9_]+$ pattern" (ansible-lint complains about role names containing underscores, to be fixed in a later patch) - 701, "meta/main.yml should contain relevant info" (ansible-lint complains about missing galaxy_info)
-
- 03 Jan, 2021 8 commits
-
-
Florian Haas authored
Upstream changed its recommendation from using Circus for service management to systemd a while ago. Retain the taiga_service_manager default of "circus" for backward compatibility (we don't want users running on Circus to be switched over involuntarily), but update the defaults file and variables.md to contain a strong recommendation to override this.
-
Florian Haas authored
The "archive" module will fail the playbook on an empty source list, even in check mode. Thus, explicitly disable it in check mode.
-
Florian Haas authored
As of Ansible 2.8, group names containing "-" (hyphen) characters are considered invalid, and will generate a warning about TRANSFORM_INVALID_GROUP_CHARS. Thus, give users the ability to gradually change over their group names by supporting both the "taiga-*" and "taiga_*" group name patterns. Also, update the README accordingly.
-
Florian Haas authored
Mention that the playbooks work fine on Focal, and also add a recommendation for base system upgrades.
-
Florian Haas authored
When connecting to a host as an unprivileged user, using "become" to become *another* unprivileged user can be problematic. Since we were using the unprivileged taiga_user in two instances only so we could drop a file as that user, become root instead and let it drop the file as owned by taiga_user instead. Reference: https://docs.ansible.com/ansible/latest/user_guide/become.html#becoming-an-unprivileged-user
-
Florian Haas authored
As of Ansible 2.8, using bare variables is deprecated even if they are known to be boolean, so use them with a "| bool" filter instead. Reference: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.8.html#bare-variables-in-conditionals
-
Florian Haas authored
Rather than looping over items individually, it is now recommended to use a list with the "name" parameter for the apt module. Remove all invocations of apt with with_items, and use a list for name instead.
-
Florian Haas authored
We want to set the _timestamp fact, even when we're running "ansible-playbook --check". Ansible skips any tasks using the shell and command modules in check mode by default, so we have to force running the "date" command by setting the (confusingly named) "check_mode: no" option on that task.
-
- 10 Nov, 2020 2 commits
-
-
Florian Haas authored
The "check for required variables" used a with_items loop when in was introduced in commit 30c85d17, but that loop became dead code in 8dce2ecb. Remove it.
-
Florian Haas authored
Support for the systemd module was added in Ansible 2.2; the "check for required variables" task thus verified that taiga_service_manager was set to "circus* if the playbook was run by Ansible 2.1 or earlier. The README, however, has stated for a while that Ansible 2.5 is the minimal supported version, so this test is really rather useless.
-
- 22 Jul, 2019 11 commits
-
-
Florian Haas authored
Also, since Ansible 2.5 is the first release to fully support Python 3-only targets, make that the minimum requirement. Reference: https://docs.ansible.com/ansible/latest/reference_appendices/python_3_support.html
-
Florian Haas authored
The setup guide insists on Xenial, but in practice Bionic appears to work just fine. Add a note to that effect.
-
Florian Haas authored
-
Florian Haas authored
If the taiga-front server uses a "-dist" frontend, then there is no need for it to use gulp, and hence no need to install node.js on that server. Thus, make the taiga-front to taiga-node role dependency conditional on the frontend installation type. Note that the taiga-front server will of course still install node.js if it is also a taiga-events server.
-
Florian Haas authored
If PostgreSQL were manually stopped at any time post-install, a re-run of the playbook would have failed because the postgresql_user module would have had no database to connect to. Thus, make sure that the service runs before we try to interact with the database.
-
Florian Haas authored
The Taiga production setup guide explicitly states a 1GB minimum memory requirement, "needed for compilation of lxml". Enforce this requirement on taiga-back through the taiga_back_required_memory variable, which is given in MB and defaults to 1024. On low-memory platforms such as the Raspberry Pi 3 (1 GB nominal total memory, 912 MB usable), it is still possible to compile and install lxml, under the following conditions (at least for the duration of the compilation): 1. Swap space must be available; 2. PostgreSQL must be stopped (this must be done manually, the role does not have a task for this); 3. RabbitMQ must not run (can be accomplished by setting taiga_enable_events and taiga_enable_async_tasks to false; both those features are probably not of much use on a Raspberry Pi anyway). With all these hacks in place, the memory requirement can then be relaxed by setting taiga_back_required_memory to a value like 900. Reference: https://taigaio.github.io/taiga-doc/dist/setup-production.html#_overview
-
Florian Haas authored
Based on whether the Ansible Python interpreter is Python 2 (the default on Ubuntu Xenial), or Python 3 (the default on Ubuntu Bionic), Ansible modules that rely on extra Python modules require either "python-" or "python3-" Ubuntu packages to function. Make sure we install the right one. Note that on any Ubuntu Bionic system that has events or async tasks enabled, and thus installs RabbitMQ, the Bionic rabbitmq-server package's dependency on python (that is, the Python 2 interpreter) will effectively pull Python 2 into that system, and many Ansible versions will use that interpreter by default, once it is installed. References: https://docs.ansible.com/ansible/2.8/reference_appendices/interpreter_discovery.html https://packages.ubuntu.com/bionic/rabbitmq-server
-
Florian Haas authored
Upstream no longer recommends Circus for use as the Taiga service manager, and instead suggests systemd. Include minor modifications to the systemd unit files, based on: https://taigaio.github.io/taiga-doc/dist/setup-production.html#systemd-and-gunicorn
-
Florian Haas authored
The production setup guide now recommends Node 8.x, not 6.x: https://taigaio.github.io/taiga-doc/dist/setup-production.html#taiga-events
-
Florian Haas authored
Python 3.5 is the default Python 3 version on Ubuntu Xenial; on Bionic it is Python 3.6. To ensure that things work on both platforms, just use the alias /usr/bin/python3, which exists on both.
-
Florian Haas authored
Try to ensure that people don't accidentally commit their inventories or variable files (which may contain secrets, like passwords).
-
- 27 Apr, 2018 2 commits
-
-
Florian Haas authored
Using the playbook and roles as-is can lead to unpleasant surprises if people attempt to manage multiple Taiga instances that way. Thus, add some information on how to avoid those surprises.
-
Florian Haas authored
-
- 25 Apr, 2018 2 commits
-
-
Florian Haas authored
-
Florian Haas authored
It installs by default on Ubuntu, but not on Debian, and it doesn't hurt to ensure that it's there before we attempt to add the HTTPS NodeSource repository.
-
- 24 Apr, 2018 1 commit
-
-
Marco Antonio Blanco Navarrete authored
-
- 23 Apr, 2018 4 commits
-
-
Florian Haas authored
-
Florian Haas authored
Merge branch 'fix/extra-quote-ldap-setup' of git://github.com/mablanco/taiga-ansible into mablanco-fix/extra-quote-ldap-setup Fixes #10.
-
Florian Haas authored
-
Florian Haas authored
With Ubuntu Bionic around the corner, it's probably a good idea to state that while Xenial is the reference platform, the roles should be made to run on other releases as well.
-