Website Search using Django and PostgreSQL Trigrams
Over the years I've become increasingly wary of the word "easy" in software documentation. Pick a software project at random, and there's a good chance the documentation will lead off ...
The absurdity of the fight against accessible websites
2019 was an interesting year in website accessibility. The simple and elegant premise of accessibility has been pushed aside by aggressive law firms, miserly corporations and apathetic regulatory agencies.
In ...
Multipage Forms in Django
Introduction
Most online forms fit on a single page. Think of a "join our forum" or "contact us" form into which the user enters a name, email address, and maybe ...
Django shell_plus with Pandas, and Jupyter Notebook
The Django shell provides an environment where developers can interact with the database via Django's ORM. While the shell is great for basic interactions, it quickly becomes laborious to work in, be it due to manual imports, having to scroll through shell history to repeat commands, or working with / viewing queries returning more than, say, 20 records. These issues, and more, can be remedied by interacting with the ORM in Jupyter notebooks, using Pandas.
Two very important (and overlooked) requirements for a new website vendor relationship
All relationships end. It doesn't matter whether they are personal or professional, at some point and for many reasons, they end. No one thinks about this when the relationship is budding - everything is wonderful. There is trust, there is competence, there is relief that finally the needle can be moved forward. This overflowing optimism can cloud a vital aspect of establishing a new relationship - how to get out of it gracefully. Unless a prior vendor experience has made an impact, very little attention is given to an end-of-life scenario until end-of-life is imminent. However, with a little prenuptial preparation, end-of-life drama and uncertainty can be greatly eased.
Guide to Ansible/NGINX/uWSGI/Django, Part 2: Getting uWSGI Working with NGINX and Django
In Part 1 of this post, I described the trials, tribulations and ultimate success of running Ansible to provision a cloud server, which we do often here at Imaginary ...
Guide to Ansible/NGINX/uWSGI/Django, Part 1: Running the Ansible Scripts
Here at Imaginary Landscape, we are frequently tasked with spinning up new cloud servers for our clients. Once a new server is online, we usually follow up by provisioning ...
Step-by-Step Guide to Setting up Django-RQ
Django-RQ is a Django integration with RQ, a Redis-based Python queuing library. This post is a step-by-step guide on how to set up a queue with Django-RQ plus how to make it a daemon process on a server (to always run in the background).
Scraping pdf, doc, and docx with Scrapy
In February 2017, Google announced its plans to discontinue its Google Site Search product. Those clients of Imaginary Landscape who had relied on Google to provide their users with a search engine service for their website looked to us for a new solution. Finding no obvious equivalent replacement, we decided to create our own website scraper and accompanying search app.
Continuous Integration and Deployment with Drone, Docker, Django, Gunicorn and Nginx - Part 3
The Introduction
This is the third and final part of a multi-part tutorial covering a simple(ish) setup of a continuous integration/deployment pipeline using Drone.io:0.5. Since Part 2, Drone.io:0.8 ...