On Sun, 10 Nov 2024 17:52:04 +0000, Stuart Henderson <s...@spacehopper.org> wrote:
> As long as it's not destructive to run the new version on an old > setup, I'd not do anything special with @pkgpath, let the old update > to the new as normal, and people can pkg_delete the new and add the > old if needed. Yes it's not, it will only fail to start. > I'd probably just add a MESSAGE or maybe even just an FAQ entry > rather than @ask-update as it should be easy enough to recover as the > old version is available. @ask-update stops non-interactive updates > from working. > so something like that? Index: faq/current.html =================================================================== RCS file: /cvs/www/faq/current.html,v retrieving revision 1.1122 diff -u -p -r1.1122 current.html --- faq/current.html 3 Oct 2024 00:53:36 -0000 1.1122 +++ faq/current.html 15 Nov 2024 01:43:44 -0000 @@ -56,7 +56,30 @@ use a snapshot to recover. <p> Most of these changes will have to be performed as root. -<h3 id="r20240930">2024/09/30 - No entries yet</h3> + +<h3 id="r20241120">2024/11/20 - [packages] Removal of Gateway and filesystem modes in MinIO</h3> + +<p> +The MinIO Gateway and the related filesystem mode entered a feature freeze in +July 2020. In February 2022, MinIO announced the deprecation of the MinIO +Gateway. Along with the deprecation announcement, MinIO also announced that the +feature would be removed in six months time. + +<p> +The MinIO port has been update to a version where the MinIO Gateway and the +related filesystem mode code have been removed. Deployments still using the +standalone or filesystem MinIO modes that upgrade to that latest version will +fail to start. + +<p> +The last MinIO version supporting the MinIO is provided under the package +<tt>minio-old</tt>. + +The upstream project provide a +<a href="https://min.io/docs/minio/linux/operations/install-deploy-manage/migrate-fs-gateway.html";> + procedure to migrate to a new Single-Node Single-Drive deployment +</a>. + <!-- Two blank lines before new sections. I have two remaining questions: 1. should minio and minio-old conflict? To migrate to the SNSD mode, only the old version is enough, you don't need to have both. Otherwise if we don't set a conflict marker I'll rename the minio.rc to minio-old.rc I guess 2. what should be done for credentials? As pointed out in https://min.io/docs/minio/linux/reference/minio-server/settings/root-credentials.html > If MINIO_ROOT_PASSWORD is unset, minio defaults to minioadmin. currently I have /usr/ports/net/minio/server$ cat pkg/minio.login minio:\ :openfiles-cur=4096:\ :openfiles-max=8192:\ :setenv=MINIO_ROOT_USER=root,MINIO_ROOT_PASSWORD=yourstrongpassword:\ :tc=daemon: plus a MESSAGE telling the user to update the password, should I go that way? or comment out the setenv line? or don't provide the minio.login at all and put it in the README? maybe it won't work well without the bumped limits so it will force the user to check it (and not use a default password)? Cheers, Daniel
