Now I can save visitors locally without external tools and also track a bad acting requests.

Finally, I can have a better working middleware which can catch HTTP status errors, make a redirect-response to the main page and also save a visitor.

Now I can also catch HTTP status codes in the database to see what a bad actor wants to achieve.

Thanks to: LINK

I can now save site visits without external analytics and save a bad example to later expose them in a fancy table.

Only I need to mask IP addresses before I show requests and paths to the public.

TBH I also need to add some load balancing.

    def __call__(self, request: HttpRequest) -> typing.Optional[HttpResponse]:
        """
        Check request for validity here and response with correct answers.
        Use bad codes when needed.
        Save visitor now with status code relation.
        :param request:
        :return:
        """
        try:
            response = self.get_response(request)
        except SuspiciousOperation as e:
            log.error(f"SuspiciousOperation:"
                      f"\nException:\n{e}\n")
            save_visit_task(request, status='SUS')
            return HttpResponseForbidden('CSRF verification failed.')
        except Exception as e:
            log.error(f"General …

Please use the comments form below any post.
Or leave feedback on the Feedback page if you want to ask a general question.

I use Disqus for comments, you might need to clear your cookies at this site if Disqus fails to load properly.

UPD: Also, I'm saving a lot of data for each HTTP request to get a list of the most common URLs and POST\GET arguments.
It's interesting to see some "smartass" XSS scripts targeting WordPress admin or plugins.

Soon I'll create a view at this site with the TOP list of such kinds of requests.

Interestingly I've updated this module to save just visits counters to be able to see visitors without logging into Google Analytics. I can't use that regularly, because my Pi-Hole cuts it. So, as soon as I manage to add a better sorting in this module, I'll show you this …

How to make your Raspberry 5 talking with python lib Piper?

I wanted to make my Raspberry tell me about power outages and air alerts near my location.

The setup is pretty simple and described ar the repo:

# List devices
aplay -L
# I only have USB card:
hw:CARD=Audio,DEV=0
     USB Audio, USB Audio
    Direct hardware device without any conversions
plughw:CARD=Audio,DEV=0
     USB Audio, USB Audio
    Hardware device with all software conversions
sysdefault:CARD=Audio
     USB Audio, …

Installing NUT - Network Ups Tool Notifications and emails

Notifications and email

Just a simple work log of installing NUT and configuring email notifications from it.

• Start here: Installing NUT

 Go to file:

sudo vi /etc/nut/upsmon.conf

# Email script for NOTIFYCMD
# Simple
NOTIFYCMD "/etc/nut/notifycmd.sh"

# Notification events
NOTIFYFLAG ONLINE     SYSLOG+WALL+EXEC
NOTIFYFLAG ONBATT     SYSLOG+WALL+EXEC
NOTIFYFLAG LOWBATT    SYSLOG+WALL+EXEC
NOTIFYFLAG FSD        SYSLOG+WALL+EXEC
NOTIFYFLAG COMMOK     SYSLOG+WALL+EXEC
NOTIFYFLAG COMMBAD    SYSLOG+WALL+EXEC
NOTIFYFLAG SHUTDOWN   SYSLOG+WALL+EXEC
NOTIFYFLAG REPLBATT   SYSLOG+WALL+EXEC
NOTIFYFLAG NOCOMM     SYSLOG+WALL+EXEC
NOTIFYFLAG NOPARENT   SYSLOG+WALL+EXEC

sudo vi /etc/nut/notifycmd.sh

#!/bin/bash
EMAIL='to@YOYR_EMAIL.com'
echo -e "Subject: UPS ALERT Basic: $NOTIFYTYPE\n\nUPS: $UPSNAME\r\nAlert type: $NOTIFYTYPE\n\n\nThis is a basic notification!" | msmtp $EMAIL

# Change group to nut
sudo chown :nut /etc/nut/notifycmd.sh
# Add execution
sudo chmod 774 /etc/nut/notifycmd.sh
# Restart the NUT services
sudo systemctl restart nut-server.service
sudo systemctl restart nut-driver.service
sudo systemctl restart nut-monitor.service

Install and use Network Ups Tool - an open source Uninterruptible Power Supply software

Old

Here I'll show how to use Python (3.8.0 in the current example, but legit for latest 3.+ versions, not for os.name == 'NT') and virtualenv to setup WGSI enabled website on Django (or any) with implemented Celery + Flower + RabbitMQ. This example is my own path used for automated test framework: Octopus (not available now, but have dev branch opened: Lobster)

Here only configurations and setup for Python 3.8.0, virtualenv, WSGI, Django, Celery (worker and beat services), Flower and that's it. Later I'll show Django + Celery configuration when they run together (sort of).

You may want to install Python at first: Read

When your modern and fancy python is installed, we'll make a virtual environment for our website. Never underestimate a power of virtualenv as I did, because since you start to use it, you will never understand how did you work without them …

Old me installing Python

Centos 7 + Python 3(4,5,6,7,8) installation guide with no pain. As for me.

I can't even say how many times I have to update my python executables for web servers and how much pain I feel during this routine.

Usual Google\StackOverflow advice only describes one particular problem. But there're few of them, and they're different so you spent hours trying to collect them all and pick the right decision.

Then you just drop it and use yum for any latest python version available!

Here I'll show you and make a reminder for myself about how to install modern python in the best way, once, without pain.

I use Centos 7 typical install as for WebServer (minimal install could require to install tonnes of dev-libs and yum, be sure you prepared them before)

1. Preparations:

You need to install some compil libs.

yum …

Old stuff, very old

Test design

Our test system has a pretty simple configuration, so I do not want to bother you with the detailed description of it. Simply - it's just a standalone execution of a test.py file with all requirements (test setup and tear down) in local internal test utility. Helper local utility has a usual amount of preparation functions, test data loading and some other configurations. In the very end of test loading, it just compares a node-set result of "real" scan (software and hardware nodes in a database after the scan) with predefined node-set (from test.py). Node set we usually expect at the end of the test should be added by the developer when product discovery pattern is ready or have a new feature or fix.

Now I'm trying to implement entirely new and somewhere different test design because current is not …

Old stuff

Morning everybody…

I recommend reading this part of the blog only in the morning with a cup of dark and strong coffee.

I'll show you some new cases, and howto's to help you automate routines in the developer's life. There will be an example of my fails and win on different scenarios. The poor code I'll include also.

Very beginning

Firstly - I'll try to make this thread in English. And maybe later when I have time - to make Ukrainian and Russian translations, I'll make them.

"Octopus" story has started from a small plugin for Sublime Text editor. Later it will be ported to Atom.

I've started developing "Octopus" on spring-summer 2016, and I've not finished it yet! New functions and features were implemented continuously. Product transforms into a framework.

Now all processes executed automatically and simultaneously for 24/7.  "Octopus" has …

Вкратце: когда добавляешь пачку тасок на Celery worker'ы, случается так, что парочка из них отваливается или засыпает или еще чего. Долго не доходили руки поправить это недоразумение, поэтому я просто рестартовал все воркеры раз в пару дней или прямо перед началом проверки рутины, в общем очень сложно было поймать и воспроизвести тот случай, когда без каких-либо ошибок воркер просто молчал. И наконец дошоли руки запилить кривофикс, время покажет насколько он толковый, суть в следующем: В сразу после момента определения свободного воркера  - запускать app.control.heartbeat() и app.control.ping(timeout=10) и если ответ пришел (в виде [{'alpha@host': {'ok': 'pong'}}]) - значит воркер готов и можно передавать ему таску, пачку тасков, рутину и тп. Если ответ пришел отличным от этого - даем ошибку и ничего не запускаем далее. При плохом раскладе пользователю придется просто перезапустить задачу посредством нажатия кнопочки еще раз, а вот запланированная таска - умрет. Общий вид на код примерно такой: ^{Набросавши …}