You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
⚠️ **Security Warning**: Never commit your license token to version control. For production, use environment variables or secure secret management systems (Rails credentials, Heroku config vars, AWS Secrets Manager, etc.).
141
141
142
+
### License Validation Lifecycle
143
+
144
+
React on Rails Pro validates licenses offline with the public key embedded in the gem and node renderer package. There
145
+
is no network call to ShakaCode during validation.
146
+
147
+
License validation happens in these places:
148
+
149
+
- Rails checks the license after application initialization and logs the result.
150
+
- The standalone node renderer checks the license when the renderer master process starts and logs the result.
151
+
- The browser receives `railsContext.rorPro` as a Pro-installed signal only; it does not validate the license.
152
+
153
+
A missing, expired, or invalid license does not prevent Rails or the node renderer from starting. In production, license
154
+
issues are logged as warnings, and Rails includes an HTML attribution comment indicating the license state.
155
+
156
+
### Verify License Compliance
157
+
158
+
Use the built-in task as a deploy or release gate:
For complete license setup instructions, see [LICENSE_SETUP.md](https://github.com/shakacode/react_on_rails/blob/main/react_on_rails_pro/LICENSE_SETUP.md).
0 commit comments