What’s in the pipeline, how it works, how it’s made…
Today at about 1:00 pm Philadelphia time, the website went offline. It was still there, it just could not answer any queries. In this post: Website and database server running in AWS FreeBSD 12.2 on a t3.medium EC2 instance PostgreSQL 12.5 running on a db.t2.large RDS instance Initial look Looking at load, it was acceptable: […]
lack of index brings website to a crawl Read More »
This post is mostly for personal use as I investigate this topic. It may take a few days and I need to keep notes. Last week, FreshPorts went live with git commits. There are some outstanding issues, such as commits to branches, which I will catch up on in the weeks to come. During that
Removing ‘unused’ tables Read More »
Hello, The changeover from subversion to git for the FreeBSD project enters it’s final stage about three hours from now (as I type this). At 3:01 UTC on Mar 31 2021, the repository will become read-only. The full schedule for that process is in the FreeBSD wiki. The first git commit is not expected until
FreshPorts will disable user login/updates on March 31 as part of transition to git Read More »
One of the many useful features on FreshPorts is: what port[s] install[s] this file? That’s the pkg-plist search option. pkg-plist is a file which “lists all the files installed by the port”. However not all ports have a pkg-plist file because the list is compiled automatically. That is why the configure_plist table was created to
Replacing a column search with a full text search solution Read More »
In this post I will show you how I discovered that the backend was putting data into a new table (generate_plist) but the website was still using the ports.pkg_plist column. The result was stale data being shown on the website (for older ports) or no data at all (for newer ports). How long? Since Oct
Converting a column-based expression to a row based solution Read More »
This is a cheat sheet for FreshPorts behind-the-scenes administration. If you want one for users, please start with suggested content. Ingress Actions git-single-commit.sh – Take a commit from the repo and insert it into the database. Will fail if commit is already there. REPO is one of src, ports, doc. Hash is the git commit
FreshPorts cheat sheet Read More »
EDIT: update, I think I have solved this via help on IRC. See solution. I need help configuring Postfix. I am overwhelmed by the options available and I need to stay on track by working on the rest of the git changes. I have changed references to the FreshPorts domain. I’m using example.org instead. Background
Postfix help wanted Read More »
This is what runs in an ingress jail: This runs in a nginx jail:
What runs in a FreshPorts jail? Read More »
In this post I’ll talk about how the code intially took the easy way out and how recent changes have tightened that up. In short, the code would raise N messages when just a single notification is sufficient. Today the full vuxml database was reloaded into FreshPorts. This affects approximately 3454 ports and the marking
Changing how we record ports which need cache clearing Read More »
FreshPorts can display a single commit based upon commit id, which is based upon the Message-Id of the commit email (for subversion and cvs) or the commit hash (for git). Commit ids are specified in the URL. Cached entries are stored on disk and are named after the commit. It is because are are using
Changing cache file name for commits Read More »