Skip to content

Update License File Instructions #734

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jacpete opened this issue Apr 23, 2024 · 2 comments
Open

Update License File Instructions #734

jacpete opened this issue Apr 23, 2024 · 2 comments

Comments

@jacpete
Copy link

jacpete commented Apr 23, 2024

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

/opt/rstudio-connect/bin/license-manager activate-file $RSC_LICENSE_FILE_PATH

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

/opt/rstudio-pm/bin/license-manager activate-file $RSPM_LICENSE_FILE_PATH --userspace

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

https://docs.posit.co/ide/server-pro/license_management/license_activation_and_details.html#activation

/usr/lib/rstudio-server/bin/license-manager activate-file $RSW_LICENSE_FILE_PATH

chown rstudio-server $RSW_LICENSE_FILE_PATH
chmod 0600 $RSW_LICENSE_FILE_PATH
cp -a $RSW_LICENSE_FILE_PATH /var/lib/rstudio-server/

**

@kfeinauer kfeinauer added the needs refinement Marked for review at a future meeting label Mar 5, 2025
@emcrisan
Copy link

emcrisan commented Mar 5, 2025

Came up in ticket 115766

@kfeinauer kfeinauer removed the needs refinement Marked for review at a future meeting label Apr 2, 2025
@jacpete
Copy link
Author

jacpete commented Apr 29, 2025

I did some work on a customer ticket and was able to identify what changes need made to use with the --userspace licensing flag in Posit Package Manager. Essentially, it looks for the license in the HOME folder (specifically /home/$USER/.rstudio-pm) for the run-as user (by default rstudio-pm) instead of /var/lib/rstudio-pm

PPM

/opt/rstudio-pm/bin/license-manager activate-file $RSPM_LICENSE_FILE_PATH --userspace

mkdir -p /home/rstudio-pm/.rstudio-pm/
cp -a $RSPM_LICENSE_FILE_PATH /home/rstudio-pm/.rstudio-pm/
chown rstudio-pm:rstudio-pm /home/rstudio-pm/.rstudio-pm/$(basename $RSPM_LICENSE_FILE_PATH)
chmod 0600 /home/rstudio-pm/.rstudio-pm/$(basename $RSPM_LICENSE_FILE_PATH)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants