This documents the git specific code which I need to package and deploy. /usr/local/libexec/freshports This is installed by freshports-scripts-git, and I have the directory symlinked to ~/scripts on devgit.freshports.org for convenience. In this directory, we have the following symlinks to other directories: Ignoring lines 2 and 4 which are not relevant, we have this list […]
packaging up the git-specific code Read More »
FreshPorts had a cache clearing issue recently. It lingered. For a long time. It took me a while to figure it out. It turned out to be a Python 3 compatibility issue. In this post: PostgreSQL 12.1 FreeBSD 12.1 I will outline how database changes invoke external scripts asynchronously which then clear the cache. I
Cache clearing issue Read More »
Back in 2007, perhaps earlier, I wrote a Python script which listens for various PostgreSQL events. In particular, this script will invalidate the cache for a port when it is updated. There are several other such tasks, such as the creation of a new category. When the commit processing daemon (freshports) detects that a new
Listening daemon out of date Read More »
FreshPorts has a CVS history that dates back to mid 2000 (and that’s just what I could find with a quick search). It started on a MySQL, which isn’t really up to the job. It quickly moved to PostgreSQL, the finest database server out there, and it just happens to be Open Source. Somewhere along
Merging from branch to HEAD Read More »
The Python listening script is now in production. With a few luser-type problems along the way. Specifically: I have discovered, quite recently, that having the same name for both the NOTIFY command and the LISTEN command is kind of a good strategy when you actually want your listener to be notified. The problem? The code
Python listening now in production Read More »
Following on from the previous post, I found myself with a few hours to myself tonight. The estrogen in the house went out as a group so I managed to do a bit more coding on the FreshPorts listening daemon.
Adding stubs for listening – data driven Read More »
Data driven applications are a good concept to keep in mind when design an application, especially when that application needs to have new bits added to it on a regular basis. My idea for using Python to listen for FreshPorts events is a case in point.
Data driven listening Read More »
Today I started playing with Python again. My goal is to create a listening “daemon†to process PostgreSQL events. I wrote about my initial proof of concept at the start of the month. Today, it’s time to look at using this for real.
More on Python Listen Read More »
PostgreSQL is my database of choice. Any who has worked with commercial databases will find more in common with PostgreSQL than any other open source database. I moved to PostgreSQL for the transactions, the stored procecdures, and the relational integrity Sure, other databases have begun to catch up, but they still don’t have the polish
Python, PostgreSQL, and LISTEN Read More »