https://patchwork.kernel.org/patch/8784071/
While renaming the policy would have been a “cleaner” solution, this would create a scenario where our setup playbooks would need to check for the policy by it’s old name before installing the new one. Updating the filename to reflect the policy name is the least invasive and risky change.
A reference to socketio in awx/settings/production.py was removed in f399c90a69a1b846eedfbf94ee255c1cb5d4ef53. I’m guessing it also needs to be removed here.
Fixes this error:
```
ERROR: yaml.parser.ParserError: while parsing a block mapping
in "./tools/docker-compose/unit-tests/docker-compose.yml", line 10, column 7
expected <block end>, but found '<scalar>'
in "./tools/docker-compose/unit-tests/docker-compose.yml", line 11, column 40
```
node_modules was being overwritten by the bind-mount when the container started. This is kind of hacky, but it’s the only way to do this without changing everything.
- Added a script that allows for piping signing keys into the container’s stdin stream.
- Got sign.exp working
- I ended up getting mock to run as root, which means both RPM and DEB jobs both use —unsafe-perm now, so I added that back to the Makefile.
The SWIG_FEATURES environment variable is to get pip install working with M2Crypto==0.22.3. It works without SWIG_FEATURES if we update to M2Crypto >= 0.23.0.
Also did some organization, add README.
By default, bootstrap pads the “navbar-brand” element with 15px, and sets margin-left to -15px. Since we had removed all the padding, it meant that the logo was -15px to the left of the main page margin.
Shane McDonald