Anton Shestakov <av6@dwimlabs.net>, Mon, 28 Sep 2020 11:31:48 +0800
hgweb: run on Python 3
playbook-example.yml
Permissions: -rw-r--r--
# NOTE: you probably don't want to run these pre_tasks on a real box. Just # bear in mind that to be able to access hgweb from inside the box, you # need to use the virtual host name (i.e. http://127.0.0.1/ won't work). # So make sure you either have DNS records for hg.mydomain or it's in - name: Update /etc/hosts line: '127.0.0.1 {{ hostname }} hg.{{ hostname }}' # NOTE: hgweb role depends on Lighttpd and uWSGI being installed. It's # recommended to install them in separate lighttpd and uwsgi roles, not in # pre_tasks like in this example playbook. # NOTE: hgweb role notifies two handlers: # Naturally, the handlers are not defined in the role itself, so this # example playbook includes them here. # NOTE: how to test that it works correctly (also see the note about DNS): # curl -I http://hg.mydomain/ # curl -I http://hg.mydomain/static/mercurial.js # then check /var/log/uwsgi/app/50-hgweb.log for problems # make sure it doesn't see requests /static/ (Lighttpd should handle them)