https://medium.com/@Pinterest_Engineering/how-we-switched-our-template-rendering-engine-to-react-a799a3d540b0
How we switched our template rendering engine to #React
In 2015, we made the decision to migrate our legacy web experience to React to keep up with our fast growth and perform better with increased developer velocity.
When we began this project, Pinterest.com was humming along on the existing architecture for some time. On the server, #Django, a Python web application framework, served our web requests and #Jinja was rendering our #templates. The server response to the browser included all the markup, assets and data the browser needed to fetch our JavaScript, images and CSS, and initialize our client-side application. Nunjucks, a JavaScript template rendering engine that uses the same template syntax as Jinja, did all subsequent template renders on the client side.
https://stackoverflow.com/questions/30288351/how-to-setup-django-1-8-to-use-jinja2
The #Jinja template folder for app dirs defaults to #jinja2 not the standard templates folder.
So try the following directory structure and #Django will locate your Jinja #templates:
mysite
mysite
myapp
jinja2
myapp
index.html
manage.py
And instead of: return render(request, 'myapp/index.html') you should write: return render(request, 'index.html')
#jinja#ansible#ansible_collection#collection#devsec#hacktoberfest#hardening#linux#mysql_hardening#nginx#nginx_hardening#os_hardening#playbook#protection#role#ssh_hardening#sysctl
devsec.hardening is an Ansible collection that battle-tests security hardening for Linux (CentOS, AlmaLinux, Rocky, Debian, Ubuntu, etc.), MySQL, Nginx, and SSH, matching DevSec Inspec baselines. Install via `ansible-galaxy collection install devsec.hardening` and apply roles like os_hardening easily. It saves you time by automating secure configs across servers, cuts manual work, boosts compliance, and shrinks attack surfaces for safer systems.
https://github.com/dev-sec/ansible-collection-hardening