Update License File Instructions
jacpete opened this issue · comments
We should move to depreciate the license-manager activate-file command to what has been recommended by the product teams in the admin guide.
License files should be the easiest activation method for containers because as long as the file ends up in the correct format with the correct permissions under /var/lib/<rstudio-product> it should license without issue and shouldn't have the risk of bleeding activations due to bad container exits.
In the future, when we move all customers to license files, we could think up a way to have customers mount the license files directly into /var/lib/<rstudio-product> and remove the activation steps from the startup.sh because the deactivation trap isn't needed for license files.
Connect
https://docs.posit.co/connect/admin/licensing/#license-file-activation
chown root $RSC_LICENSE_FILE_PATH
chmod 0600 $RSC_LICENSE_FILE_PATH
cp -a $RSC_LICENSE_FILE_PATH /var/lib/rstudio-connect/.PPM
Commands not published until next release:
https://github.com/rstudio/package-manager/blob/58070369ab1d2a8bf460dac6952d9c7bb3378824/docs/main/docs/admin/licensing.md?plain=1#L84-L99
chown rstudio-pm $RSPM_LICENSE_FILE_PATH
chmod 0600 $RSPM_LICENSE_FILE_PATH
cp -a $RSPM_LICENSE_FILE_PATH /var/lib/rstudio-pm/I don't think we need to do anything special with the --userspace flag, but we should verify with PPM
Workbench
chown rstudio-server $RSW_LICENSE_FILE_PATH
chmod 0600 $RSW_LICENSE_FILE_PATH
cp -a $RSW_LICENSE_FILE_PATH /var/lib/rstudio-server/**