OpenWISP issueshttps://gitlab.ninux.org/groups/openwisp/-/issues2019-01-23T18:37:21Zhttps://gitlab.ninux.org/openwisp/ansible-openwisp2/-/issues/86Deprecation Warning in openwisp.openwisp2 set_fact task2019-01-23T18:37:21ZHispanicomarco@ingmg.comDeprecation Warning in openwisp.openwisp2 set_fact taskTASK [openwisp.openwisp2 : set_fact] *******************************************
[DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using
result|failed use result is failed. This feature will be removed in version
...TASK [openwisp.openwisp2 : set_fact] *******************************************
[DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using
result|failed use result is failed. This feature will be removed in version
2.9. Deprecation warnings can be disabled by setting
deprecation_warnings=False in ansible.cfg.https://gitlab.ninux.org/openwisp/ansible-openwisp2/-/issues/85[django] Internal server error2019-01-23T18:37:21ZHispanicomarco@ingmg.com[django] Internal server error*Created by: nemesisdesign*
I've noticed a periodic internal server error on some instances.
At first sight it seems that some processes crash and exit because they can't write to logs for permission reasons. It seems the permission ...*Created by: nemesisdesign*
I've noticed a periodic internal server error on some instances.
At first sight it seems that some processes crash and exit because they can't write to logs for permission reasons. It seems the permission of some logs change from `www-data` to `root` at some point. Further investigation is needed.https://gitlab.ninux.org/openwisp/ansible-openwisp2/-/issues/84[ci] Avoid duplication of basic running test2019-01-23T18:37:21ZHispanicomarco@ingmg.com[ci] Avoid duplication of basic running test*Created by: nemesisdesign*
These lines seem duplicated:
- https://github.com/openwisp/ansible-openwisp2/blob/master/.travis.yml#L31
- https://github.com/openwisp/ansible-openwisp2/blob/master/.gitlab-ci.yml#L16-L19
Maybe we can ...*Created by: nemesisdesign*
These lines seem duplicated:
- https://github.com/openwisp/ansible-openwisp2/blob/master/.travis.yml#L31
- https://github.com/openwisp/ansible-openwisp2/blob/master/.gitlab-ci.yml#L16-L19
Maybe we can extract those lines in a script that gets called by both CI systemshttps://gitlab.ninux.org/openwisp/ansible-openwisp2/-/issues/83Ansible install fails in migrate on Ubuntu 14.042019-01-23T18:37:21ZHispanicomarco@ingmg.comAnsible install fails in migrate on Ubuntu 14.04Ansible fails in Ubuntu 14.04 on the migrate task.
See https://travis-ci.org/hispanico/ansible-openwisp2/jobs/368290716Ansible fails in Ubuntu 14.04 on the migrate task.
See https://travis-ci.org/hispanico/ansible-openwisp2/jobs/368290716https://gitlab.ninux.org/openwisp/ansible-openwisp2/-/issues/81Missing headers when instaling on arbian based on debian strech2019-01-23T18:37:21ZHispanicomarco@ingmg.comMissing headers when instaling on arbian based on debian strech*Created by: Yasen6275*
Tried to install controller on SBC with armbian based on Debian Strech and got veeery long error.
The major clue in it was:
" The headers or library files could not be found for jpeg,
a required depende...*Created by: Yasen6275*
Tried to install controller on SBC with armbian based on Debian Strech and got veeery long error.
The major clue in it was:
" The headers or library files could not be found for jpeg,
a required dependency when compiling Pillow from source."
After installing libjpeg-dev, instalation went smoothlyhttps://gitlab.ninux.org/openwisp/ansible-openwisp2/-/issues/78[django] Load templates with django.template.loaders.cached.Loader2019-01-23T18:37:21ZHispanicomarco@ingmg.com[django] Load templates with django.template.loaders.cached.Loader*Created by: nemesisdesign*
A small optimization that's easy to add: https://docs.djangoproject.com/en/1.10/ref/templates/api/#django.template.loaders.cached.Loader
But we need to activate the django cache with django redis with thes...*Created by: nemesisdesign*
A small optimization that's easy to add: https://docs.djangoproject.com/en/1.10/ref/templates/api/#django.template.loaders.cached.Loader
But we need to activate the django cache with django redis with these two:
- http://niwinz.github.io/django-redis/latest/#_configure_as_cache_backend
- http://niwinz.github.io/django-redis/latest/#_configure_as_session_backendhttps://gitlab.ninux.org/openwisp/ansible-openwisp2/-/issues/77Ansible install fails in migrate on Debian Buster and Ubuntu 182019-01-23T18:37:21ZHispanicomarco@ingmg.comAnsible install fails in migrate on Debian Buster and Ubuntu 18*Created by: jdeluyck*
Installation in Debian Buster (aka testing) fails on the migrate step. Not entirely sure why.
Running in x86_64.
```
TASK [openwisp.openwisp2 : migrate] *******************************************************...*Created by: jdeluyck*
Installation in Debian Buster (aka testing) fails on the migrate step. Not entirely sure why.
Running in x86_64.
```
TASK [openwisp.openwisp2 : migrate] **********************************************************************************************************************
fatal: [openwisp.home.lan]: FAILED! => {"changed": false, "cmd": "./manage.py migrate --noinput", "msg": "\n:stderr: Traceback (most recent call last):\n File \"/opt/openwisp2/env/lib/python3.6/site-packages/django/contrib/gis/db/backends/spatialite/base.py\", line 51, in get_new_connection\n conn.load_extension(self.spatialite_lib)\nsqlite3.OperationalError: mod_spatialite: cannot open shared object file: No such file or directory\n\nThe above exception was the direct cause of the following exception:\n\nTraceback (most recent call last):\n File \"./manage.py\", line 10, in <module>\n execute_from_command_line(sys.argv)\n File \"/opt/openwisp2/env/lib/python3.6/site-packages/django/core/management/__init__.py\", line 371, in execute_from_command_line\n utility.execute()\n File \"/opt/openwisp2/env/lib/python3.6/site-packages/django/core/management/__init__.py\", line 365, in execute\n self.fetch_command(subcommand).run_from_argv(self.argv)\n File \"/opt/openwisp2/env/lib/python3.6/site-packages/django/core/management/base.py\", line 288, in run_from_argv\n self.execute(*args, **cmd_options)\n File \"/opt/openwisp2/env/lib/python3.6/site-packages/django/core/management/base.py\", line 335, in execute\n output = self.handle(*args, **options)\n File \"/opt/openwisp2/env/lib/python3.6/site-packages/django/core/management/commands/migrate.py\", line 77, in handle\n connection.prepare_database()\n File \"/opt/openwisp2/env/lib/python3.6/site-packages/django/contrib/gis/db/backends/spatialite/base.py\", line 61, in prepare_database\n with self.cursor() as cursor:\n File \"/opt/openwisp2/env/lib/python3.6/site-packages/django/db/backends/base/base.py\", line 255, in cursor\n return self._cursor()\n File \"/opt/openwisp2/env/lib/python3.6/site-packages/django/db/backends/base/base.py\", line 232, in _cursor\n self.ensure_connection()\n File \"/opt/openwisp2/env/lib/python3.6/site-packages/django/db/backends/base/base.py\", line 216, in ensure_connection\n self.connect()\n File \"/opt/openwisp2/env/lib/python3.6/site-packages/django/db/backends/base/base.py\", line 194, in connect\n self.connection = self.get_new_connection(conn_params)\n File \"/opt/openwisp2/env/lib/python3.6/site-packages/django/contrib/gis/db/backends/spatialite/base.py\", line 55, in get_new_connection\n ) from exc\ndjango.core.exceptions.ImproperlyConfigured: Unable to load the SpatiaLite library extension \"mod_spatialite\"\n", "path": "/opt/openwisp2/env/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", "state": "absent", "syspath": ["/tmp/ansible_5L_TsX", "/tmp/ansible_5L_TsX/ansible_modlib.zip", "/tmp/ansible_5L_TsX/ansible_modlib.zip", "/usr/lib/python2.7", "/usr/lib/python2.7/plat-x86_64-linux-gnu", "/usr/lib/python2.7/lib-tk", "/usr/lib/python2.7/lib-old", "/usr/lib/python2.7/lib-dynload", "/usr/local/lib/python2.7/dist-packages", "/usr/lib/python2.7/dist-packages"]}
```https://gitlab.ninux.org/openwisp/ansible-openwisp2/-/issues/76Issues with Stouts.postfix2019-01-23T18:37:21ZHispanicomarco@ingmg.comIssues with Stouts.postfix*Created by: UtkarshVerma*
The postfix role fails if the apt cache on the production server isn't up to date. We can fix this by doing the APT cache update task before it.*Created by: UtkarshVerma*
The postfix role fails if the apt cache on the production server isn't up to date. We can fix this by doing the APT cache update task before it.https://gitlab.ninux.org/openwisp/ansible-openwisp2/-/issues/74Issues with Host-only Adapter2019-01-23T18:37:21ZHispanicomarco@ingmg.comIssues with Host-only Adapter*Created by: UtkarshVerma*
The host only-adapter is causing issues with internet connectivity on my VM and hence ansible can't download packages.
This issue is regarding the VM installation instructions.*Created by: UtkarshVerma*
The host only-adapter is causing issues with internet connectivity on my VM and hence ansible can't download packages.
This issue is regarding the VM installation instructions.https://gitlab.ninux.org/openwisp/ansible-openwisp2/-/issues/71Ansible install does not work2019-01-23T18:37:21ZHispanicomarco@ingmg.comAnsible install does not work*Created by: saurabhchakrabarti*
I've started evaluating this project once again after a long break. I'm getting the following error when I try to deploy using ansible
```
ERROR! no action detected in task. This often indicates a mi...*Created by: saurabhchakrabarti*
I've started evaluating this project once again after a long break. I'm getting the following error when I try to deploy using ansible
```
ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.
The error appears to have been in '/etc/ansible/roles/openwisp.openwisp2/tasks/main.yml': line 3, column 3, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
## tasks
- import_tasks: variables.yml
^ here
The error appears to have been in '/etc/ansible/roles/openwisp.openwisp2/tasks/main.yml': line 3, column 3, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
## tasks
- import_tasks: variables.yml
^ here
```
Things work when I replace import_tasks with include.
ansible version - 2.3.1.0
Ubuntu 16.04.2 LTShttps://gitlab.ninux.org/openwisp/ansible-openwisp2/-/issues/69[django] Add support for CORS (Cross-Origin Resource Sharing)2019-01-23T18:37:22ZHispanicomarco@ingmg.com[django] Add support for CORS (Cross-Origin Resource Sharing)*Created by: nemesisdesign*
We need to make it possible to enable CORS because [other applications may need to access some APIs to get data](https://lists.funkfeuer.at/pipermail/interop-dev/2017-December/000732.html).
We can use this...*Created by: nemesisdesign*
We need to make it possible to enable CORS because [other applications may need to access some APIs to get data](https://lists.funkfeuer.at/pipermail/interop-dev/2017-December/000732.html).
We can use this module: [django-cors-headers](https://pypi.python.org/pypi/django-cors-headers/2.1.0) - which is configurable via django settings, we have to make sure we can configure every available setting of this module, possibly using a single ansible variable containing a dictionary.
This feature should be optional and turned off by default now.https://gitlab.ninux.org/openwisp/ansible-openwisp2/-/issues/68[install] Current release fails on some systems2019-01-23T18:37:22ZHispanicomarco@ingmg.com[install] Current release fails on some systems*Created by: nemesisdesign*
The current release fails on older systems (eg: ubuntu 14 LTS, debian 8), while it seems the latest commit fixes the issues but breaks installation on newer systems (ubuntu 16 LTS).
We need to solve this a...*Created by: nemesisdesign*
The current release fails on older systems (eg: ubuntu 14 LTS, debian 8), while it seems the latest commit fixes the issues but breaks installation on newer systems (ubuntu 16 LTS).
We need to solve this asap.https://gitlab.ninux.org/openwisp/ansible-openwisp2/-/issues/64[nginx] Add support for gzip2019-01-23T18:37:22ZHispanicomarco@ingmg.com[nginx] Add support for gzip*Created by: nemesisdesign*
We need these options to be added to nginx:
```
gzip on;
gzip_comp_level 6;
gzip_proxied any;
gzip_min_length 1000;
gzip_proxied expired no-cache no-store private auth;
gzip_types text/plain text/htm...*Created by: nemesisdesign*
We need these options to be added to nginx:
```
gzip on;
gzip_comp_level 6;
gzip_proxied any;
gzip_min_length 1000;
gzip_proxied expired no-cache no-store private auth;
gzip_types text/plain text/html image/svg+xml application/json application/javascript text/xml text/css application/xml application/x-font-ttf font/opentype;
```
They need to be configurable (so it can be also turned off and details may be changed.
I think we can use this chance to add a generic mechanism to add configuration variable to nginx (which will contain the default gzip values too), eg:
```
openwisp2_nginx_ssl_config:
gzip: on
gzip_comp_level 6
# etc
```
The variables of openwisp2_nginx_ssl_config will be added only to the `:443` section of the nginx configuration.https://gitlab.ninux.org/openwisp/ansible-openwisp2/-/issues/63Ansible openwisp2 install fails on migration2019-01-23T18:37:22ZHispanicomarco@ingmg.comAnsible openwisp2 install fails on migration*Created by: HizkiFW*
Installing locally fails on `TASK [openwisp.openwisp2 : migrate]`, outputting the following error:
```
fatal: [0.0.0.0]: FAILED! => {"changed": false, "cmd": "./manage.py migrate --noinput", "msg": "\n:stderr: ...*Created by: HizkiFW*
Installing locally fails on `TASK [openwisp.openwisp2 : migrate]`, outputting the following error:
```
fatal: [0.0.0.0]: FAILED! => {"changed": false, "cmd": "./manage.py migrate --noinput", "msg": "\n:stderr: Traceback (most recent call last):\n File \"/opt/openwisp2/env/lib/python3.5/site-packages/django/contrib/gis/db/backends/spatialite/base.py\", line 60, in get_new_connection\n cur.execute(\"SELECT load_extension(%s)\", (self.spatialite_lib,))\n File \"/opt/openwisp2/env/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py\", line 328, in execute\n return Database.Cursor.execute(self, query, params)\nsqlite3.OperationalError: /usr/lib/x86_64-linux-gnu/libspatialite.so.7: undefined symbol: sqlite3_spatialite_init\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n File \"./manage.py\", line 10, in <module>\n execute_from_command_line(sys.argv)\n File \"/opt/openwisp2/env/lib/python3.5/site-packages/django/core/management/__init__.py\", line 364, in execute_from_command_line\n utility.execute()\n File \"/opt/openwisp2/env/lib/python3.5/site-packages/django/core/management/__init__.py\", line 356, in execute\n self.fetch_command(subcommand).run_from_argv(self.argv)\n File \"/opt/openwisp2/env/lib/python3.5/site-packages/django/core/management/base.py\", line 283, in run_from_argv\n self.execute(*args, **cmd_options)\n File \"/opt/openwisp2/env/lib/python3.5/site-packages/django/core/management/base.py\", line 330, in execute\n output = self.handle(*args, **options)\n File \"/opt/openwisp2/env/lib/python3.5/site-packages/django/core/management/commands/migrate.py\", line 81, in handle\n connection.prepare_database()\n File \"/opt/openwisp2/env/lib/python3.5/site-packages/django/contrib/gis/db/backends/spatialite/base.py\", line 72, in prepare_database\n with self.cursor() as cursor:\n File \"/opt/openwisp2/env/lib/python3.5/site-packages/django/db/backends/base/base.py\", line 254, in cursor\n return self._cursor()\n File \"/opt/openwisp2/env/lib/python3.5/site-packages/django/db/backends/base/base.py\", line 229, in _cursor\n self.ensure_connection()\n File \"/opt/openwisp2/env/lib/python3.5/site-packages/django/db/backends/base/base.py\", line 213, in ensure_connection\n self.connect()\n File \"/opt/openwisp2/env/lib/python3.5/site-packages/django/db/backends/base/base.py\", line 189, in connect\n self.connection = self.get_new_connection(conn_params)\n File \"/opt/openwisp2/env/lib/python3.5/site-packages/django/contrib/gis/db/backends/spatialite/base.py\", line 65, in get_new_connection\n six.reraise(ImproperlyConfigured, ImproperlyConfigured(new_msg), sys.exc_info()[2])\n File \"/opt/openwisp2/env/lib/python3.5/site-packages/django/utils/six.py\", line 685, in reraise\n raise value.with_traceback(tb)\n File \"/opt/openwisp2/env/lib/python3.5/site-packages/django/contrib/gis/db/backends/spatialite/base.py\", line 60, in get_new_connection\n cur.execute(\"SELECT load_extension(%s)\", (self.spatialite_lib,))\n File \"/opt/openwisp2/env/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py\", line 328, in execute\n return Database.Cursor.execute(self, query, params)\ndjango.core.exceptions.ImproperlyConfigured: Unable to load the SpatiaLite library extension \"libspatialite.so.7\" because: /usr/lib/x86_64-linux-gnu/libspatialite.so.7: undefined symbol: sqlite3_spatialite_init\n", "path": "/opt/openwisp2/env/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin", "state": "absent", "syspath": ["/tmp/ansible_7an2FN", "/tmp/ansible_7an2FN/ansible_modlib.zip", "/tmp/ansible_7an2FN/ansible_modlib.zip", "/usr/lib/python2.7", "/usr/lib/python2.7/plat-x86_64-linux-gnu", "/usr/lib/python2.7/lib-tk", "/usr/lib/python2.7/lib-old", "/usr/lib/python2.7/lib-dynload", "/usr/local/lib/python2.7/dist-packages", "/usr/lib/python2.7/dist-packages"]}
```
It seems to be a problem with spatialite.https://gitlab.ninux.org/openwisp/ansible-openwisp2/-/issues/62GitMate Labelled Closed Issues Tonight2019-01-23T18:37:21ZHispanicomarco@ingmg.comGitMate Labelled Closed Issues Tonight*Created by: sils*
Hi everyone :)
TLDR: [GitMate.io](https://gitmate.io) acted on closed issues (and PRs) unneededly tonight, likely on your repo. The issue is fixed now and we're improving QA. More info at https://gitlab.com/gitmate...*Created by: sils*
Hi everyone :)
TLDR: [GitMate.io](https://gitmate.io) acted on closed issues (and PRs) unneededly tonight, likely on your repo. The issue is fixed now and we're improving QA. More info at https://gitlab.com/gitmate/open-source/gitmate-2/issues/275.
You're getting this email because you have been affected by a bug in GitMate.io this night and you're using the feature that was buggy.
In short: GitMate's stale rules acted on closed issues and PRs. That might have been comments like "this issue will be closed now because it's inactive" or the addition of stale labels on already closed issues.
We are sorry that this happened and fixed the problem as soon as we were aware. We are also introducing new measures to improve our stability with a new QA stage in addition to our existing ones so those kinds of issues don't happen again.
Please let us know if you would like to get a script to revert those actions; it seems though as most communities would rather keep it than sending out additional notifications.
We've summarized the incident at https://gitlab.com/gitmate/open-source/gitmate-2/issues/275 .
Please reach out to us if you have any further questions about this.
Sincerely,
Lasse Schuirmann
lasse@schuirmann.net
Founder of http://coala.io/, http://viperdev.io/ and http://gitmate.io/https://gitlab.ninux.org/openwisp/ansible-openwisp2/-/issues/61[python3] Automatically install python 3.5 or 3.6 if available2019-01-23T18:37:22ZHispanicomarco@ingmg.com[python3] Automatically install python 3.5 or 3.6 if available*Created by: nemesisdesign*
Django 2.0 officially suggests to use python 3.5 or higher.
We should add a way for the role to automatically install python 3.5 or 3.6 if available in the system packages and ensure it is used by openwisp2.*Created by: nemesisdesign*
Django 2.0 officially suggests to use python 3.5 or higher.
We should add a way for the role to automatically install python 3.5 or 3.6 if available in the system packages and ensure it is used by openwisp2.https://gitlab.ninux.org/openwisp/ansible-openwisp2/-/issues/59Improving the install instructions2019-01-23T18:37:22ZHispanicomarco@ingmg.comImproving the install instructions*Created by: HizkiFW*
I think the following passages are a bit ambiguous/hard to understand, and could be improved.
> - for "production server" we mean a server (not a laptop or a desktop computer!) with public ipv4 / ipv6 which is u...*Created by: HizkiFW*
I think the following passages are a bit ambiguous/hard to understand, and could be improved.
> - for "production server" we mean a server (not a laptop or a desktop computer!) with public ipv4 / ipv6 which is used to host openwisp2
> - for "local machine" we mean the host from which you launch ansible, eg: your own laptop
>
> Ansible is a configuration management tool that works by entering production servers via SSH, so you need to install it and configure it on the machine where you launch the deployment and this machine must be able to SSH into the production server.
This section does not explain that ansible is going to *install openwisp2 on the production server*. It also needs to make it clear that the local machine is going to be installing openwisp2 on the production server by controlling it via ssh.
> sudo ansible-galaxy install openwisp.openwisp2
Using `sudo` to install the openwisp2 role messed with some of the permissions, preventing ansible from reading the role. It could be fixed by `chown`ing the role directory, but could easily be prevnted by not using `sudo` during this step.
> Create a new file `hosts` **on your local machine** with the following contents:
Could be reworded to mention the working directory that was made in the previous step.
> Create a new playbook file `playbook.yml` **on your local machine** with the following contents:
Also add instructions to replace the `hosts` part in the yml file to the production server's hostname
> Substitute `openwisp2.mydomain.com` with your hostname - **DO NOT REPLACE `openwisp2.mydomain.com` WITH AN IP ADDRESS**, otherwise email sending through postfix will break, causing 500 internal server errors on some operations.
This is the part that confused me when I first installed it. It says to replace the hostname with *your hostname*, which is *very* ambiguous, since *your* could refer to either the local machine or the production server. Since the user is currently working on the local machine, it is assumed that the *your* here is the local machine, when in fact it should be the production server.
> The line `become: "{{ become | default('yes') }}"` means ansible will use the `sudo` program to run each command. You may remove this line if you don't need it (eg: if you are using the `root` user).
This line could be improved by stating that the `root` user here is for the production server, not for the local machine.
> Run the playbook **from your local machine** with:
>
> ansible-playbook -i hosts playbook.yml -u <user> -k --become -K
>
> Substitute `<user>` with your user.
'with your user' is ambiguous; it could mean either the local machine's username or the production server.
> **Tip**: if you have an error like `Authentication or permission failure` then try to use *root* user `ansible-playbook -i hosts playbook.yml -u root -k`
Also add another tip, if there is an error about adding the host's fingerprint to the known_hosts file, it could be easily done by manually connecting to the host via SSH before doing the install process.
> When the playbook is done running, if you got no errors you can login at:
>
> https://openwisp2.mydomain.com/admin
> username: admin
> password: admin
>
> Substitute `openwisp2.mydomain.com` with your hostname.
Again, 'your' here is ambiguous. Should be replaced with 'production server'.
---
I ~~will make~~ have made [a PR](https://github.com/openwisp/ansible-openwisp2/pull/60) fixing these issues.https://gitlab.ninux.org/openwisp/ansible-openwisp2/-/issues/58Ideas for improving documentation2019-01-23T18:37:22ZHispanicomarco@ingmg.comIdeas for improving documentation*Created by: h0n3yc4k3*
1) Create a database of error's (maybe in wiki?)
For example I (and HizkiFW) had this problem:
> ERROR! the role 'openwisp.openwisp2' was not found in /home/artem/openwisp2-ansible-playbook/roles:/home/artem/...*Created by: h0n3yc4k3*
1) Create a database of error's (maybe in wiki?)
For example I (and HizkiFW) had this problem:
> ERROR! the role 'openwisp.openwisp2' was not found in /home/artem/openwisp2-ansible-playbook/roles:/home/artem/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles:/home/artem/openwisp2-ansible-playbook
> The error appears to have been in '/home/artem/openwisp2-ansible-playbook/playbook.yml': line 4, column 7, but may
> be elsewhere in the file depending on the exact syntax problem.
> The offending line appears to be:
> roles:
> - openwisp.openwisp2
> ^ here
2) Is working `ansible-playbook -i hosts playbook.yml -u <user> -k --become -K` command? (bcs I used *root* all the time)
3) Swap "Install OpenWISP2 locally" and steps (like "Install ansible") place
4) Add subtitles for video's of installing/using openwisp
5) And maybe record new videos about openwisp
https://gitlab.ninux.org/openwisp/ansible-openwisp2/-/issues/57[postfix] Stouts.postfix2019-01-23T18:37:22ZHispanicomarco@ingmg.com[postfix] Stouts.postfix*Created by: nemesisdesign*
One patch still needs to be sent: https://github.com/nemesisdesign/Stouts.postfix/commit/3c42624da203e6f92cf340d8b828f0ec6feef181
Change the dependencies in meta/main.yml to use the latest [Stouts.postfix ...*Created by: nemesisdesign*
One patch still needs to be sent: https://github.com/nemesisdesign/Stouts.postfix/commit/3c42624da203e6f92cf340d8b828f0ec6feef181
Change the dependencies in meta/main.yml to use the latest [Stouts.postfix role](https://github.com/Stouts/Stouts.postfix) (instead of my fork, my patches have been merged months ago), remove my fork, install the main Stouts.postfix role in the local environment and test the installation again to ensure it works.https://gitlab.ninux.org/openwisp/ansible-openwisp2/-/issues/51[docs] Local installation for testing2019-01-23T18:37:22ZHispanicomarco@ingmg.com[docs] Local installation for testing*Created by: nemesisdesign*
I think it would be better to replace the section named "Install OpenWISP2 locally (laptop, desktop pc)" with a section that explains how to install OpenWISP 2 in a virtualbox VM, the same task we have asked ...*Created by: nemesisdesign*
I think it would be better to replace the section named "Install OpenWISP2 locally (laptop, desktop pc)" with a section that explains how to install OpenWISP 2 in a virtualbox VM, the same task we have asked GCI students to perform and for which they encountered all the same issues.
We can use their experience to prepare a step by step tutorial for this case that would probably work better than the kind of suggestion we give now.