What’s in the pipeline, how it works, how it’s made…
Today, the UI on the website was updated. The primary changes are to the home page and the date pages (i.e. lists of commits). I have purposely not cleared the cache. This should help you see the before and after images. For comparison, see today’s commits and the commits from Dec 16. This latest work […]
My thanks go out the AWS team who deal with the credits for open source projects. FreshPorts hit a big problem in Sep/Oct and I thought the project was going to have a non-trivial bill to pay. The main FreshPorts nodes are hosted on AWS – there are other nodes. Despite my own shortcomings (see
This was originally written in September 2018, but never published (for unknown reasons). I found it in the drafts section of the website today. In this post, you will see me change approach and not use a secondary table in one instance, but use multiple secondary tables in another. In one case, you will also
Using triggers to update a table with calculated values Read More »
I’m so very happy about recent changes to the website. It’s been a great day. I was volunteering at a flu shot clinic. A new coffee shop has opened up, and I was there before the clinic. After the clinic, it was walking the dog, then some serious changes to the the PostgreSQL queries which
Great changes to the websites Read More »
The front page of FreshPorts is about to change, slightly. At present, the front page contains only the the commits to the main branch of the FreeBSD. More precisely, it does not include: Commits to Mk/ or other similar non-port entities within the ports tree Commits to the quarterly branch (whatever the latest quarter is;
Displaying all ports tree commits on the front page Read More »
When setting up a new FreshPorts ingress node, the repositories must be configured with tags so FreshPorts knows the last commit it has processed. This is the starting point each time FreshPorts goes to search for new commits. This post about Processing commits on branches with git might help with background. Those tags must be
Configuring the repo for a new ingress node Read More »
Tonight I was setting up a new FreshPorts node for development. It took me a while to remember the steps. sudo su -l postgres psql template1 < globals.sql createdb -T template0 -E SQL_ASCII freshports.org psql freshports.org create language plperl; exit; time pg_restore -j 32 -d freshports.org ~dan/dump/freshports.org.dump
note to self: restoring a database Read More »
Based on the Add links to GitHub and GitLab mirrors for ports and commits request, the website has some new links arriving soon. Link to GitHub from each commit A similar link to GitLab Use the one you like. Each git web interface has it’s own followers. Also, while there, the commit hash at the
New links to GitLab and GitHub, in addition to the exist cgit.freebsd.org Read More »
The Libreoffice homepages seem wrong. dev and test do not show a homepage for arabic/libreoffice, but stage and prod do. Could this be a commit which corrected something after dev and test were corrected? I think so. I think this commit did that. Let’s check from the command line. I’m doing this in my empty
What’s up with libreoffice homepages Read More »
By “post correction”, I meant “post-correction script”, i.e. after the correction script completed. A recent commit started the process of moving the WWW from pkg-descr to Makefile. These were huge commits, about 27930 ports each. FreshPorts is dumb. It sees a commit and it refreshes all ports touched by that commit. Refreshing every port takes
homepage – post correction Read More »