Anonymous | Login | Signup for a new account | 09-07-2024 17:39 PDT |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0005008 | [Resin] | minor | always | 03-30-12 00:26 | 03-30-12 12:59 | ||||
Reporter | rickHigh | View Status | public | ||||||
Assigned To | alex | ||||||||
Priority | normal | Resolution | fixed | Platform | |||||
Status | closed | OS | |||||||
Projection | none | OS Version | |||||||
ETA | none | Fixed in Version | 4.0.28 | Product Version | |||||
Product Build | |||||||||
Summary | 0005008: Use license-add to add a license to an un-licensed instance | ||||||||
Description |
$ resinctl license-add --license 1013792.license command 'license-add' is only available with Resin Pro Expectations: I can use license-add to add a license to an un-licensed instance. User Story (as I understand it): Customer downloads Resin Pro. Customer installs Resin Pro on n-number of EC2 or remote instances. Customer buys a license. Customer uses license-add to add the license to said remote instances. Cloud Tutorial Perspective: From a cloud / cluster tutorial perspective, if license-add only works with licensed copies, then I have to figure out a secure reliable way to transmit license files from dev box to EC2 instance. If license-add works with non-licensed Resin, then I can just us license-add to add the license to the remote server and not explain how to setup secure file transfer or use S3 to transmit files. |
||||||||
Steps To Reproduce | |||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed. 26 unique queries executed. |