-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Ansible and Vagrant for Debian 12 #279
base: master
Are you sure you want to change the base?
Conversation
- vnc4server | ||
- libjpeg-turbo8-dev | ||
- chromium | ||
- tigervnc-standalone-server |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
vnc4server
has a proprietary license so I switched over to tigervnc
which is in the main repositories.
@@ -70,7 +70,7 @@ | |||
changed_when: false | |||
|
|||
- name: ensure service user {{user}} exists | |||
user: name={{user}} system=yes createhome=no home=/nonexistent | |||
user: name={{user}} system=yes createhome=yes home=/home/{{user}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This user does actually have to exist, as {{user}}
is used later in the warcproxy
playbook. The only reason this didn't error before is because /home/vagrant
is created by default by Vagrant itself. (I wasn't running inside Vagrant though, so I hit this).
shell=/usr/sbin/nologin | ||
become: true | ||
when: id_user|failed | ||
when: id_user.rc != 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the style suggested by the Ansible docs, although #218 suggests is failed
which is nicer to read? |failed
filter definitely does not work any longer.
(converting to draft because it looks like Xvnc is crash looping in this configuration) |
Ubuntu no longer packages
chromium
as a .deb, only as a snap. Debian is keeping the .deb dream alive.I've made the playbook more resilient to path changes with Python versions by using
-mvirtualenv
instead of executing the module file and usingpython3
instead of expectingpython
on the system path to point to the right place.This proposed PR would lose the ability to archive Adobe Flash as no equivalent is packaged (or would work with a modern Chromium, I think?)