I recently saw this project became a package in freshports (Which is really exciting, Congratulation for all the hardwork)!!!I
I would like some guidance therefore on how to move forward. If packages error out, they are very easily left behind (ex. mongodb-3.6) and I would hate to see that happen here.
The reason for checking in as a install-unifi-7.1.68.sh is because the original script does not work on pfSense (2.4.5, 2.5.1, 2.5.2 or 2.6) for the snappyjava replacement but I added jq instead of sed. That was to incorporate the package url with All/type-class tree in ABI whereas in the past it would just be net, it would just pick pkgname and that failed coming form previous versions. I also added mongo-tools 4.2 as part of installation because that helps with migration from 3.6.
to 4.2. I migrated last year but forgot to document exact steps.
using MONGODB_CURRENT_VER does give the flexibility to use v3.6 vs v4.0 vs v4.2 but might also astray the user in believing that the package might work with > 4.2 versions of mongodb.
I recently saw this project became a package in freshports (Which is really exciting, Congratulation for all the hardwork)!!!I
I would like some guidance therefore on how to move forward. If packages error out, they are very easily left behind (ex. mongodb-3.6) and I would hate to see that happen here.
The reason for checking in as a install-unifi-7.1.68.sh is because the original script does not work on pfSense (2.4.5, 2.5.1, 2.5.2 or 2.6) for the snappyjava replacement but I added jq instead of sed. That was to incorporate the package url with
All/type-class
tree in ABI whereas in the past it would just be net, it would just pick pkgname and that failed coming form previous versions. I also added mongo-tools 4.2 as part of installation because that helps with migration from 3.6. to 4.2. I migrated last year but forgot to document exact steps.