CRcraftkiller·Dec 7, 2024
poudriere is roughly 3 FreeBSD Update clients of sh code: https://github.com/freebsd/poudriere/blob/master/src/share/p...
In Biggest shell programsfreebsd
poudriere
Shell2015–2024
freebsd / poudriere
poudriere
Port/Package build and test system
5Distinct people
6Mentions
1Explicit recommenders
448GitHub stars
What to know before exploring
What it is
Port/Package build and test system
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
Really nice summary! If you really want to make your life with ports easier, I highly recommend Poudriere (https://github.com/freebsd/poudriere). Poudriere can build your ports…
pgib used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year6 dated mentions
Observed mentions: 2015-09-21 21:10:47 UTC to 2024-12-07 13:38:00 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
6 sourcesFrom reading your response I think there are more questions than answers. I'll quickly go through the first ones and get to the main items.
1. Docker does run on Debian[1][2] which is why I referenced "Freebsd or Debian." For reference I've run and used jails for a number of years with development, staging, and production environments. I don't know why frontend developers would be doing system administration, setting security controls, or that using Docker would count as "system management knowledge."
2. I spoke to the on premise part with foreman[2] and pxe booting. The VPS uploading was in comparison to the default images already available for linux with cloud providers verse FreeBSD.
Generally speaking, on your FreeBSD example and most of your points, it reads to me as regular system administration. You can manage your ports and packag
Read the rest
es just like having .rpm or .dep repos with poudriere[4]. You can lock specific versions of software from automatic updates or not. I'm not really sure why 5 years isn't enough time for a base OS to be supported since you can build your ports from source at anytime. Yes you are required to check the UPDATING file for any breaking changes however if nginx or similar application is critical to your operation and you are speaking to using Docker and other build tools wouldn't you be testing software upgrades anyway? As a vendor wouldn't you have nightly builds to download the latest nginx version and test it? It would seem a bit naive to just "trust" that an auto update would never cause issues because its in LTS.
The bigger item to address, if you are purchasing and using SAP products as part of your business or are a vendor producing/selling a module I don't think the CentOS complaint holds water. The risk you have accepted is that you have no control over how the support, development or updates progress but you want no surprises because it affects your ability to get revenue. That would appear, to me, to be a cost you should pass on to your customer, maybe they will move over to Ubuntu and make things a bit easier for you support and training wise. Most people choose CentOS because it was free and not RHEL thats the risk taken and sometimes risks come with new costs. If your module(in this example) makes them enough revenue, similar to anyone running SAP products, they should have the budget to pay for it.
[1] https://docs.docker.com/desktop/install/linux-install/
[2] https://docs.docker.com/engine/install/
[3] https://www.theforeman.org/
[4] https://github.com/freebsd/poudriere
> pkg is an amazing system that beats dpkg or rpm
What's your reasoning for this statement? I find poudriere[1] handy for compiling one's own packages from ports configured to fit one's goals, but I see nothing outstanding in plain pkg.
It has issues when there's an IPv6 address up (even link-local) but no egress v6 routing. It would hang and wait for a timeout when an IPv6 address is selected from resolved addresses. After a timeout - pkg connects to v4 endpoint but if there's several packages to be downloaded, it can fall back to trying to connect to v6 with the next package.
On the other hand, I've recently had Ubuntu 22.04 register Python-related packages which were not successfully installed, resulting in all dpkg/apt/apt-get commands failing due to py3clean script throwing tracebacks, until /var/lib/dpkg/status was edited and these
Read the rest
packages were in fact installed and then removed.
[1] https://github.com/freebsd/poudriere/wiki
I use this with Poudriere to speed up my FreeBSD pkg host building multiple Sets of ports https://github.com/freebsd/poudriere/wiki/ccache
In Ccache – a fast C/C++ compiler cache> Do some people only exchange security updates and crash dumps off of physical media given in person?
Sure it's not "the norm" but personally I run a Poudriere[0] server and build all my own software packages. One server syncs the FreeBSD Ports collection and downloads the needed software source distfiles, but then none of my other machines/jails are allowed to install software from anywhere outside my own network. A lot of them don't get any Internet access at all.
That still has nothing to do with in-app analytics though.
[0] https://github.com/freebsd/poudriere/wiki
In Audacity: Clarification of Privacy PolicyReally nice summary! If you really want to make your life with ports easier, I highly recommend Poudriere (https://github.com/freebsd/poudriere). Poudriere can build your ports collection for one or more machines running any version of FreeBSD that's <= of the Poudriere hosts. After you configure your ports, you can easily archive all of the options you've set (e.g. should want/need to move your Poudriere setup elsewhere).
I run Poudriere on my home server, and then I point pkg to a local Nginx server. Every night, it builds the latest versions of all of the ports I use, and I can simply type "pkg upgrade" any time I want. For work, I run a Poudriere server on an EC2 instance to build packages for a variety of configurations. Depending on your needs, you could pretty easily have an EC2 instance that remains shutdown most of the time, and
Read the rest
then on some sort of schedule you spin it up, build the latest, publish your packages, and shut down again.