Update documentation for public distribution

Remove all references to GitHub Packages and private distribution.
Update package name from @shakacode-tools/react-on-rails-pro-node-renderer to react-on-rails-pro-node-renderer throughout documentation.

Changes:
- Completely rewrite installation.md to remove GitHub PAT authentication
- Simplify to standard gem install and npm install commands
- Add JWT license token configuration section
- Update all code examples with unscoped package name
- Remove GitHub Packages authentication instructions
- Update contributor documentation to reflect all packages are public
- Update CONTRIBUTING.md files to remove private package sections

Documentation files updated:
- react_on_rails_pro/docs/installation.md (major rewrite)
- react_on_rails_pro/docs/node-renderer/basics.md
- react_on_rails_pro/docs/node-renderer/js-configuration.md
- react_on_rails_pro/docs/node-renderer/error-reporting-and-tracing.md
- react_on_rails_pro/docs/code-splitting-loadable-components.md
- docs/contributor-info/releasing.md
- react_on_rails_pro/docs/contributors-info/releasing.md
- CONTRIBUTING.md
- react_on_rails_pro/CONTRIBUTING.md

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Author: ihabadham

CONTRIBUTING.md

@@ -128,7 +128,7 @@ Package [email protected] added ==> /Users/justin/shakacode/react-o
 Don't forget you may need to run yarn after adding packages with yalc to install/update dependencies/bin scripts.
 ```
 
-Of course, you can do the same with `react-on-rails-pro` and `@shakacode-tools/react-on-rails-pro-node-renderer` packages.
+Of course, you can do the same with `react-on-rails-pro` and `react-on-rails-pro-node-renderer` packages.
 
 This is the approach `spec/dummy` apps use, so you can also look at their implementation.
 

docs/contributor-info/releasing.md

@@ -58,9 +58,9 @@ The release task publishes 5 packages with unified versioning:
 
 1. **react-on-rails** - NPM package
 2. **react-on-rails-pro** - NPM package
-3. **react_on_rails** - RubyGem
-
-**PRIVATE (GitHub Packages):** 4. **@shakacode-tools/react-on-rails-pro-node-renderer** - NPM package 5. **react_on_rails_pro** - RubyGem
+3. **react-on-rails-pro-node-renderer** - NPM package
+4. **react_on_rails** - RubyGem
+5. **react_on_rails_pro** - RubyGem
 
 ### Version Synchronization
 

react_on_rails_pro/CONTRIBUTING.md

@@ -292,24 +292,13 @@ Contact Justin Gordon, [[email protected]](mailto:[email protected]) for r
 
 ## Prerequisites
 
-You need authentication for both public and private package registries:
+You need authentication for public package registries:
 
 **Public packages (npmjs.org + rubygems.org):**
 - NPM: Run `npm login`
 - RubyGems: Standard credentials via `gem push`
 
-**Private packages (GitHub Packages):**
-- Get a GitHub personal access token with `write:packages` scope
-- Configure `~/.npmrc`:
-  ```ini
-  //npm.pkg.github.com/:_authToken=<TOKEN>
-  always-auth=true
-  ```
-- Configure `~/.gem/credentials`:
-  ```yaml
-  :github: Bearer <GITHUB_TOKEN>
-  ```
-- Set environment variable: `export GITHUB_TOKEN=<TOKEN>`
+All React on Rails and React on Rails Pro packages are now published publicly to npmjs.org and RubyGems.org.
 
 ## Release Command
 

react_on_rails_pro/docs/code-splitting-loadable-components.md

@@ -245,7 +245,7 @@ In your `node-renderer.js` file which runs node renderer, you need to specify `s
 ```js
 const path = require('path');
 const env = process.env;
-const { reactOnRailsProNodeRenderer } = require('@shakacode-tools/react-on-rails-pro-node-renderer');
+const { reactOnRailsProNodeRenderer } = require('react-on-rails-pro-node-renderer');
 
 const config = {
   ...

react_on_rails_pro/docs/contributors-info/releasing.md

@@ -35,6 +35,6 @@ rake release[17.0.0,false,verdaccio]
 This unified script releases all 5 packages together:
 - react-on-rails (NPM)
 - react-on-rails-pro (NPM)
+- react-on-rails-pro-node-renderer (NPM)
 - react_on_rails (RubyGem)
-- @shakacode-tools/react-on-rails-pro-node-renderer (NPM, GitHub Packages)
-- react_on_rails_pro (RubyGem, GitHub Packages)
+- react_on_rails_pro (RubyGem)

react_on_rails_pro/docs/installation.md

@@ -1,183 +1,196 @@
 # Installation
-Since the repository is private, you will get a **GitHub Personal Access Token** and an account that can access the packages. Substitute that value in the commands below. If you dont' have this, ask [[email protected]](mailto:[email protected]) to give you one.
 
-Check the [CHANGELOG](https://github.com/shakacode/react_on_rails_pro/blob/master/CHANGELOG.md) to see what version you want.
+React on Rails Pro packages are published publicly on npmjs.org and RubyGems.org. Installation requires a valid **license token** for runtime validation. Contact [[email protected]](mailto:justin@shakacode.com) to purchase a license.
 
-# Version
+Check the [CHANGELOG](https://github.com/shakacode/react_on_rails/blob/master/CHANGELOG.md) to see what version you want.
 
-For the below docs, find the desired `<version>` in the CHANGELOG. Note, for pre-release versions, gems have all periods, and node packages uses a dash, like gem `3.0.0.rc.0` and node package `3.0.0-rc.0`.
+## Version Format
 
-# Ruby
-## Gem Installation
-1. Ensure your **Rails** app is using the **react_on_rails** gem, version greater than 11.0.7.
-1. Add the `react_on_rails_pro` gem to your **Gemfile**. Substitute the appropriate version number. 
-   
-## Gemfile Change
+For the below docs, find the desired `<version>` in the CHANGELOG. Note that for pre-release versions:
+- Gems use all periods: `16.2.0.beta.1`
+- NPM packages use dashes: `16.2.0-beta.1`
 
-Replace the following in the snippet for the Gemfile
-1. `<account>` for the api key
-2. `<api-key>`
-3. `<version>` desired
+# Ruby Gem Installation
 
-```ruby
-source "https://<rorp-account>:<token>@"\
-  "rubygems.pkg.github.com/shakacode-tools" do
-  gem "react_on_rails_pro", "<version>"
-end
-```
+## Prerequisites
+
+Ensure your **Rails** app is using the **react_on_rails** gem, version 16.0.0 or higher.
 
-## Alternate installation keeping the key out of your Gemfile
+## Install react_on_rails_pro Gem
+
+Add the `react_on_rails_pro` gem to your **Gemfile**:
 
 ```ruby
-source "https://rubygems.pkg.github.com/shakacode-tools" do
-  gem "react_on_rails_pro", "<version>"
-end
+gem "react_on_rails_pro", "~> 16.1"
 ```
-Or use the `gem install` command:
+
+Then run:
 
 ```bash
-gem install react_on_rails_pro --version "<version>> --source "https://rubygems.pkg.github.com/shakacode-tools"
+bundle install
 ```
 
-Then edit your permissions for bundler at the command line:
+Or install directly:
 
+```bash
+gem install react_on_rails_pro --version "<version>"
 ```
-bundle config set rubygems.pkg.github.com <username>:<token>
+
+## License Configuration
+
+Set your license token as an environment variable:
+
+```bash
+export REACT_ON_RAILS_PRO_LICENSE="your-license-token-here"
 ```
 
-## Using a branch in your Gemfile
-Note, you should probably use an ENV value for the token so that you don't check this into your source code.
-   ```ruby
-   gem "react_on_rails_pro", version: "<version>", git: "https://[your-github-token]:[email protected]/shakacode/react_on_rails_pro.git", tag: "<version>"
-   ```
+Or configure it in your Rails initializer (not recommended for production):
+
+```ruby
+# config/initializers/react_on_rails_pro.rb
+ReactOnRailsPro.configure do |config|
+  config.license_token = ENV["REACT_ON_RAILS_PRO_LICENSE"]
+end
+```
 
 ## Rails Configuration
-You don't need to create an initializer if you are satisfied with the default as described in 
-[Configuration](./configuration.md)
 
-# Node Package
-Note, you only need to install the Node Package if you are using the standalone node renderer, `NodeRenderer`.
+You don't need to create an initializer if you are satisfied with the defaults as described in [Configuration](./configuration.md).
 
-## Installation
+For basic setup:
 
-1. Create a subdirectory of your rails project for the Node renderer. Let's use `react-on-rails-pro`.
-   
-2. Create a file `react-on-rails-pro/.npmrc` with the following
+```ruby
+# config/initializers/react_on_rails_pro.rb
+ReactOnRailsPro.configure do |config|
+  # Your configuration here
+  # See docs/configuration.md for all options
+end
 ```
-always-auth=true
-//npm.pkg.github.com/:_authToken=<token>
-@shakacode-tools:registry=https://npm.pkg.github.com
+
+# Node Package Installation
+
+**Note:** You only need to install the Node Package if you are using the standalone node renderer (`NodeRenderer`). If you're using `ExecJS` (the default), skip this section.
+
+## Install react-on-rails-pro-node-renderer
+
+### Using npm:
+
+```bash
+npm install react-on-rails-pro-node-renderer
+```
+
+### Using yarn:
+
+```bash
+yarn add react-on-rails-pro-node-renderer
 ```
 
-3. Create a `react-on-rails-pro/package.json`
+### Add to package.json:
+
 ```json
 {
-  "private": true,
   "dependencies": {
-    "@shakacode-tools/react-on-rails-pro-node-renderer": "<version>"
-  },
-  "scripts": {
-    "node-renderer": "echo 'Starting React on Rails Pro Node Renderer.' && node ./react-on-rails-pro-node-renderer.js"
+    "react-on-rails-pro-node-renderer": "16.1.1"
   }
 }
 ```
 
-4. Be sure to run `npm i` **and not** `yarn` as only npm seems to work with the private github packages.
+## Node Renderer Setup
 
-If you really want to use yarn, see [Yarn can't find private Github npm registry](https://stackoverflow.com/questions/58316109/yarn-cant-find-private-github-npm-registry)
-
-5. You can start the renderer with either the executable `node-renderer` or, preferably, with 
-   a startup JS file, say called `react-on-rails-pro/react-on-rails-pro-node-renderer.js` with
-   these contents. _Note the use of the namespaced **`@shakacode-tools/react-on-rails-pro-node-renderer`** for the package.
+Create a JavaScript file to configure and launch the node renderer, for example `react-on-rails-pro-node-renderer.js`:
 
 ```js
-const path = require('path')
-const {
-  reactOnRailsProNodeRenderer,
-} = require('@shakacode-tools/react-on-rails-pro-node-renderer')
+const path = require('path');
+const { reactOnRailsProNodeRenderer } = require('react-on-rails-pro-node-renderer');
 
-const env = process.env
+const env = process.env;
 
 const config = {
   bundlePath: path.resolve(__dirname, '../.node-renderer-bundles'),
 
   // Listen at RENDERER_PORT env value or default port 3800
   logLevel: env.RENDERER_LOG_LEVEL || 'debug', // show all logs
 
-  // See value in /config/initializers/react_on_rails_pro.rb. Should use env
-  // value in real app.
-  password: 'myPassword1',
+  // Password for Rails <-> Node renderer communication
+  // See value in /config/initializers/react_on_rails_pro.rb
+  password: env.RENDERER_PASSWORD || 'changeme',
 
-  // Save bundle to "tmp/bundles" dir of our dummy app
-  // This is the default
   port: env.RENDERER_PORT || 3800,
 
   // supportModules should be set to true to allow the server-bundle code to
-  // see require, exports, etc.
-  // `false` is like the ExecJS behavior
-  // this option is required to equal `true` in order to use loadable components
+  // see require, exports, etc. (`false` is like the ExecJS behavior)
+  // This option is required to equal `true` in order to use loadable components
   supportModules: true,
 
   // workersCount defaults to the number of CPUs minus 1
-  workersCount: Number(process.env.NODE_RENDERER_CONCURRENCY || 3),
-
-  // Next 2 params, allWorkersRestartInterval and
-  // delayBetweenIndividualWorkerRestarts must both should be set if you wish
-  // to have automatic worker restarting, say to clear memory leaks.
-  // time is in minutes between restarting all workers
-  // Enable next 2 if the renderer is running out of memory
-  // allWorkersRestartInterval: 15,
-  // time in minutes between each worker restarting when restarting all workers
-  // delayBetweenIndividualWorkerRestarts: 2,
-}
+  workersCount: Number(env.NODE_RENDERER_CONCURRENCY || 3),
+
+  // Optional: Automatic worker restarting (for memory leak mitigation)
+  // allWorkersRestartInterval: 15, // minutes between restarting all workers
+  // delayBetweenIndividualWorkerRestarts: 2, // minutes between each worker restart
+};
 
 // Renderer detects a total number of CPUs on virtual hostings like Heroku
 // or CircleCI instead of CPUs number allocated for current container. This
 // results in spawning many workers while only 1-2 of them really needed.
 if (env.CI) {
-  config.workersCount = 2
+  config.workersCount = 2;
 }
 
-reactOnRailsProNodeRenderer(config)
+reactOnRailsProNodeRenderer(config);
 ```
 
-## Instructions for using a branch
+Add a script to your `package.json`:
 
-Install the node-renderer executable, possibly globally. Substitute the branch name or tag for `master`
+```json
+{
+  "scripts": {
+    "node-renderer": "node ./react-on-rails-pro-node-renderer.js"
+  }
+}
 ```
-yarn global add https://<your-github-token>:[email protected]/shakacode/react_on_rails_pro.git\#master
+
+Start the renderer:
+
+```bash
+npm run node-renderer
 ```
 
-This installs a binary `node-renderer`.
+## Rails Configuration for Node Renderer
 
-### Using Github packages
+Configure Rails to use the remote node renderer:
 
-Login into npm
+```ruby
+# config/initializers/react_on_rails_pro.rb
+ReactOnRailsPro.configure do |config|
+  config.server_renderer = "NodeRenderer"
 
-```bash
-npm install @shakacode-tools/react-on-rails-pro-node-renderer@<version>
-```                      
+  # Configure renderer connection
+  config.renderer_url = ENV["REACT_RENDERER_URL"] || "http://localhost:3800"
+  config.renderer_password = ENV["RENDERER_PASSWORD"] || "changeme"
 
-or edit package.json directly
-```json
-"@shakacode-tools/react-on-rails-pro-node-renderer": "<version>"
-```                     
+  # Enable prerender caching (recommended)
+  config.prerender_caching = true
+end
+```
 
-### Configuration
-See [NodeRenderer JavaScript Configuration](./node-renderer/js-configuration.md).
+### Configuration Options
 
-#### Webpack Configuration
-Set your server bundle webpack configuration to use a target of `node` per the [Webpack docs](https://webpack.js.org/concepts/targets/#usage).
+See [Rails Configuration Options](./configuration.md) for all available settings.
 
-## Authentication when using Github packages
-[Auth for the npm package](https://docs.github.com/en/packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages#authenticating-to-github-packages)
+Pay attention to:
+- `config.server_renderer = "NodeRenderer"` - Required to use node renderer
+- `config.renderer_url` - URL where your node renderer is running
+- `config.renderer_password` - Shared secret for authentication
+- `config.prerender_caching` - Enable caching (recommended)
 
-Create a new ~/.npmrc file if one doesn't exist.
-```
-//npm.pkg.github.com/:_authToken=TOKEN
-```                  
+## Webpack Configuration
 
-To configure bundler if you don't want the token in your Gemfile:
-```
-bundle config https://rubygems.pkg.github.com/OWNER USERNAME:TOKEN
-``` 
+Set your server bundle webpack configuration to use a target of `node` per the [Webpack docs](https://webpack.js.org/concepts/targets/#usage).
+
+## Additional Documentation
+
+- [Node Renderer Basics](./node-renderer/basics.md)
+- [Node Renderer JavaScript Configuration](./node-renderer/js-configuration.md)
+- [Rails Configuration Options](./configuration.md)
+- [Error Reporting and Tracing](./node-renderer/error-reporting-and-tracing.md)

react_on_rails_pro/docs/node-renderer/basics.md

@@ -33,16 +33,16 @@ For the most control over the setup, create a JavaScript file to start the NodeR
    cd renderer-app
    ```
 2. Make sure you have **Node.js** version **14** or higher and **Yarn** installed.
-3. Init node application and yarn add to install `@shakacode-tools/react-on-rails-pro-node-renderer` package.
+3. Init node application and install the `react-on-rails-pro-node-renderer` package.
    ```sh
    yarn init
-   yarn add https://[your-github-token]:[email protected]/shakacode/react_on_rails_pro.git\#master
+   yarn add react-on-rails-pro-node-renderer
    ```
 4. Configure a JavaScript file that will launch the rendering server per the docs in [Node Renderer JavaScript Configuration](./js-configuration.md). For example, create a file `node-renderer.js`. Here is a simple example that uses all the defaults except for bundlePath:
 
    ```javascript
    import path from 'path';
-   import reactOnRailsProNodeRenderer from '@shakacode-tools/react-on-rails-pro-node-renderer';
+   import reactOnRailsProNodeRenderer from 'react-on-rails-pro-node-renderer';
 
    const config = {
      bundlePath: path.resolve(__dirname, '../.node-renderer-bundles'),