Closed msimerson closed 1 year ago
So I understand the general concept and I can imagine the caching makes sense. I struggle a bit with the method how I can verify all the changes. Don't have a test machine at hand at the moment
I run VMware Fusion on my mac and do all my dev testing in there. Makes it really easy to roll back to snapshots and start over.
The caching server doesn't get built or used by default. It's not a documented feature. Yet. I figure it needs some real world shaking out before it's ready for mass consumption.
The nginx stuff is more what I wanted your thoughts on. Everything else is just run-of-the-mill updates.
Conceptual NGINX Config Change
Currently the nginx config has the http block in /data/etc/nginx.conf and part of the server config in /data/etc/nginx-locations.conf. This was useful to minimize the amount of config needed in the 'locations' section, but that lacks the flexibility to have more than one server block. In a nod towards the trend of having local configs in conf.d dirs, this PR does the same for nginx server configs.
Feature: bsd_cache
Run a local nginx server in proxy mode that caches pkg and freebsd-update files. This has the most potential for time (and bandwidth) savings when managing (build, update, audit) a bunch of jails, reducing the need to wait for files to download within each jail.
Changes proposed in this pull request:
Checklist: