react_on_rails 16.2.0.beta.4 → 16.2.0.beta.8

data/react_on_rails_pro/docs/installation.md

@@ -1,108 +1,112 @@
 # 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 [justin@shakacode.com](mailto:justin@shakacode.com) to give you one.
+React on Rails Pro packages are published publicly on npmjs.org and RubyGems.org. Installation requires a valid **license token** for runtime validation. Contact [justin@shakacode.com](mailto:justin@shakacode.com) to purchase a license.
 
-Check the [CHANGELOG](https://github.com/shakacode/react_on_rails_pro/blob/master/CHANGELOG.md) to see what version you want.
+**Upgrading from GitHub Packages?** See the [Upgrading Guide](./updating.md) for migration instructions.
 
-# 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
+For the below docs, find the desired `<version>` in the CHANGELOG. Note that for pre-release versions:
 
-## Gem Installation
+- Gems use all periods: `16.2.0.beta.1`
+- NPM packages use dashes: `16.2.0-beta.1`
 
-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.
+# Ruby Gem Installation
 
-## Gemfile Change
+## Prerequisites
 
-Replace the following in the snippet for the Gemfile
+Ensure your **Rails** app is using the **react_on_rails** gem, version 16.0.0 or higher.
 
-1. `<account>` for the api key
-2. `<api-key>`
-3. `<version>` desired
+## Install react_on_rails_pro Gem
+
+Add the `react_on_rails_pro` gem to your **Gemfile**:
 
 ```ruby
-source "https://<rorp-account>:<token>@"\
-  "rubygems.pkg.github.com/shakacode-tools" do
-  gem "react_on_rails_pro", "<version>"
-end
+gem "react_on_rails_pro", "~> 16.2"
 ```
 
-## Alternate installation keeping the key out of your Gemfile
+Then run:
 
-```ruby
-source "https://rubygems.pkg.github.com/shakacode-tools" do
-  gem "react_on_rails_pro", "<version>"
-end
+```bash
+bundle install
 ```
 
-Or use the `gem install` command:
+Or install directly:
 
 ```bash
-gem install react_on_rails_pro --version "<version>> --source "https://rubygems.pkg.github.com/shakacode-tools"
+gem install react_on_rails_pro --version "<version>"
 ```
 
-Then edit your permissions for bundler at the command line:
+## License Configuration
 
-```
-bundle config set rubygems.pkg.github.com <username>:<token>
-```
+Set your license token as an environment variable:
 
-## Using a branch in your Gemfile
+```bash
+export REACT_ON_RAILS_PRO_LICENSE="your-license-token-here"
+```
 
-Note, you should probably use an ENV value for the token so that you don't check this into your source code.
+Or configure it in your Rails initializer (not recommended for production):
 
 ```ruby
-gem "react_on_rails_pro", version: "<version>", git: "https://[your-github-token]:x-oauth-basic@github.com/shakacode/react_on_rails_pro.git", tag: "<version>"
+# config/initializers/react_on_rails_pro.rb
+ReactOnRailsPro.configure do |config|
+  config.license_token = ENV["REACT_ON_RAILS_PRO_LICENSE"]
+end
 ```
 
+⚠️ **Security Warning**: Never commit your license token to version control. Always use environment variables or secure secret management systems (like Rails credentials, Heroku config vars, AWS Secrets Manager, etc.).
+
 ## Rails Configuration
 
-You don't need to create an initializer if you are satisfied with the default as described in
-[Configuration](./configuration.md)
+You don't need to create an initializer if you are satisfied with the defaults as described in [Configuration](./configuration.md).
 
-# Node Package
+For basic setup:
 
-Note, you only need to install the Node Package if you are using the standalone node renderer, `NodeRenderer`.
+```ruby
+# config/initializers/react_on_rails_pro.rb
+ReactOnRailsPro.configure do |config|
+  # Your configuration here
+  # See docs/configuration.md for all options
+end
+```
 
-## Installation
+# Node Package Installation
 
-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
+**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
 ```
-always-auth=true
-//npm.pkg.github.com/:_authToken=<token>
-@shakacode-tools:registry=https://npm.pkg.github.com
+
+### 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.2.0"
   }
 }
 ```
 
-4. Be sure to run `npm i` **and not** `yarn` as only npm seems to work with the private github packages.
-
-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)
+## Node Renderer Setup
 
-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 { reactOnRailsProNodeRenderer } = require('react-on-rails-pro-node-renderer');
 
 const env = process.env;
 
@@ -112,34 +116,24 @@ const config = {
   // 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,
-  // Also, you can set he parameter gracefulWorkerRestartTimeout to force the worker to restart
-  // If it's the time for the worker to restart, the worker waits until it serves all active requests before restarting
-  // If a worker stuck because of a memory leakage or an infinite loop, you can set a timeout that master waits for it before killing the worker
+  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
+  // gracefulWorkerRestartTimeout: undefined, // timeout for graceful worker restart; forces restart if worker stuck
 };
 
 // Renderer detects a total number of CPUs on virtual hostings like Heroku
@@ -152,50 +146,58 @@ if (env.CI) {
 reactOnRailsProNodeRenderer(config);
 ```
 
-## Instructions for using a branch
-
-Install the node-renderer executable, possibly globally. Substitute the branch name or tag for `master`
+Add a script to your `package.json`:
 
+```json
+{
+  "scripts": {
+    "node-renderer": "node ./react-on-rails-pro-node-renderer.js"
+  }
+}
 ```
-yarn global add https://<your-github-token>:x-oauth-basic@github.com/shakacode/react_on_rails_pro.git\#master
-```
-
-This installs a binary `node-renderer`.
 
-### Using Github packages
-
-Login into npm
+Start the renderer:
 
 ```bash
-npm install @shakacode-tools/react-on-rails-pro-node-renderer@<version>
+npm run node-renderer
 ```
 
-or edit package.json directly
+## Rails Configuration for Node Renderer
 
-```json
-"@shakacode-tools/react-on-rails-pro-node-renderer": "<version>"
-```
+Configure Rails to use the remote node renderer:
 
-### Configuration
+```ruby
+# config/initializers/react_on_rails_pro.rb
+ReactOnRailsPro.configure do |config|
+  config.server_renderer = "NodeRenderer"
 
-See [NodeRenderer JavaScript Configuration](./node-renderer/js-configuration.md).
+  # Configure renderer connection
+  config.renderer_url = ENV["REACT_RENDERER_URL"] || "http://localhost:3800"
+  config.renderer_password = ENV["RENDERER_PASSWORD"] || "changeme"
 
-#### Webpack Configuration
+  # Enable prerender caching (recommended)
+  config.prerender_caching = true
+end
+```
 
-Set your server bundle webpack configuration to use a target of `node` per the [Webpack docs](https://webpack.js.org/concepts/targets/#usage).
+### Configuration Options
 
-## Authentication when using Github packages
+See [Rails Configuration Options](./configuration.md) for all available settings.
 
-[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:
 
-Create a new ~/.npmrc file if one doesn't exist.
+- `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)
 
-```
-//npm.pkg.github.com/:_authToken=TOKEN
-```
+## Webpack Configuration
 
-To configure bundler if you don't want the token in your Gemfile:
+Set your server bundle webpack configuration to use a target of `node` per the [Webpack docs](https://webpack.js.org/concepts/targets/#usage).
 
-```
-bundle config https://rubygems.pkg.github.com/OWNER USERNAME:TOKEN
-```
+## 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)

data/react_on_rails_pro/docs/node-renderer/basics.md

@@ -37,16 +37,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]:x-oauth-basic@github.com/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 serverBundleCachePath:
 
    ```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 = {
      serverBundleCachePath: path.resolve(__dirname, '../.node-renderer-bundles'),

data/react_on_rails_pro/docs/node-renderer/error-reporting-and-tracing.md

@@ -14,10 +14,10 @@ It should initialize the services according to your requirements and then enable
 3. Then load the integration:
 
     ```js
-    require('@shakacode-tools/react-on-rails-pro-node-renderer/integrations/sentry').init();
+    require('react-on-rails-pro-node-renderer/integrations/sentry').init();
    ```
 
-   - Use `@shakacode-tools/react-on-rails-pro-node-renderer/integrations/sentry6` instead of `.../sentry` for versions of Sentry SDK older than 7.63.0.
+   - Use `react-on-rails-pro-node-renderer/integrations/sentry6` instead of `.../sentry` for versions of Sentry SDK older than 7.63.0.
    - For Sentry SDK v8+ you can use `.init({ fastify: true })` to capture additional Fastify-related information.
 
 ### Sentry Tracing
@@ -40,7 +40,7 @@ To enable Sentry Tracing:
 2. Then load the integration:
 
     ```js
-    require('@shakacode-tools/react-on-rails-pro-node-renderer/integrations/honeybadger').init();
+    require('react-on-rails-pro-node-renderer/integrations/honeybadger').init();
     ```
 
     Use `init({ fastify: true })` to capture additional Fastify-related information.
@@ -49,7 +49,7 @@ To enable Sentry Tracing:
 You can create your own integrations in the same way as the provided ones.
 If you have access to the React on Rails Pro repository,
 you can use [their implementations](https://github.com/shakacode/react_on_rails_pro/tree/master/packages/node-renderer/src/integrations) as examples.
-Import these functions from `@shakacode-tools/react-on-rails-pro-node-renderer/integrations/api`:
+Import these functions from `react-on-rails-pro-node-renderer/integrations/api`:
 
 ### Error reporting services
 
@@ -59,7 +59,7 @@ Import these functions from `@shakacode-tools/react-on-rails-pro-node-renderer/i
 For example, integrating with BugSnag can be as simple as
 ```js
 const Bugsnag = require('@bugsnag/js');
-const { addNotifier } = require('@shakacode-tools/react-on-rails-pro-node-renderer/integrations/api');
+const { addNotifier } = require('react-on-rails-pro-node-renderer/integrations/api');
 
 Bugsnag.start({ /* your options */ });
 
@@ -76,7 +76,7 @@ To track requests as [sessions](https://docs.bugsnag.com/platforms/javascript/ca
 the above example becomes
 ```js
 const Bugsnag = require('@bugsnag/js');
-const { addNotifier, setupTracing } = require('@shakacode-tools/react-on-rails-pro-node-renderer/integrations/api');
+const { addNotifier, setupTracing } = require('react-on-rails-pro-node-renderer/integrations/api');
 
 Bugsnag.start({ /* your options */ });
 
@@ -117,7 +117,7 @@ Bugsnag v7 is a bit more complicated:
 
 ```js
 const Bugsnag = require('@bugsnag/js');
-const { addNotifier, setupTracing } = require('@shakacode-tools/react-on-rails-pro-node-renderer/integrations/api');
+const { addNotifier, setupTracing } = require('react-on-rails-pro-node-renderer/integrations/api');
 
 Bugsnag.start({ /* your options */ });
 
@@ -142,7 +142,7 @@ If you want to report HTTP requests from Fastify, you can use `configureFastify`
 Extending the above example:
 
 ```js
-const { configureFastify } = require('@shakacode-tools/react-on-rails-pro-node-renderer/integrations/api');
+const { configureFastify } = require('react-on-rails-pro-node-renderer/integrations/api');
 
 configureFastify((app) => {
   app.addHook('onError', (_req, _reply, error, done) => {

data/react_on_rails_pro/docs/node-renderer/js-configuration.md

@@ -57,7 +57,7 @@ Create a file './node-renderer.js'
 
 ```js
 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 = {
   // Save bundles to relative "./.node-renderer-bundles" dir of our app

data/react_on_rails_pro/docs/updating.md

@@ -1,25 +1,219 @@
-# Using a Branch Rather Than a Published Package
-_And Old Installation Instructions_
+# Upgrading React on Rails Pro
 
-## Get the oauth token from justin@shakacode.com
+## Upgrading from GitHub Packages to Public Distribution
 
-* ShakaCode does:
-  * Creates a github user, like customer-rorp with email customer-rorp@shakacode.com created via a Google apps group.
-  * Confirm email for account
-  * Add user to have read-only access for shakacode/react_on_rails_pro
-  * Create an auth token for this user.
+### Who This Guide is For
 
+This guide is for existing React on Rails Pro customers who are:
 
-## Update the Gemfile
+- Currently using GitHub Packages authentication (private distribution)
+- On version 16.2.0-beta.x or earlier
+- Upgrading to version 16.2.0 or higher
+
+If you're a new customer, see [Installation](./installation.md) instead.
+
+### What's Changing
+
+React on Rails Pro packages are now **publicly distributed** via npmjs.org and RubyGems.org:
+
+- ✅ No more GitHub Personal Access Tokens (PATs)
+- ✅ No more `.npmrc` configuration
+- ✅ Simplified installation with standard `gem install` and `npm install`
+- ✅ License validation now happens at **runtime** using JWT tokens
+
+Package names have changed:
+
+- **Scoped** (old): `@shakacode-tools/react-on-rails-pro-node-renderer`
+- **Unscoped** (new): `react-on-rails-pro-node-renderer`
+
+### Your Current Setup (GitHub Packages)
+
+If you're upgrading, you currently have:
+
+**1. Gemfile with GitHub Packages source:**
+
+```ruby
+source "https://rubygems.pkg.github.com/shakacode-tools" do
+  gem "react_on_rails_pro", "16.1.1"
+end
+```
+
+**2. `.npmrc` file with GitHub authentication:**
+
+```
+always-auth=true
+//npm.pkg.github.com/:_authToken=YOUR_TOKEN
+@shakacode-tools:registry=https://npm.pkg.github.com
+```
+
+**3. Scoped package name in package.json:**
+
+```json
+{
+  "private": true,
+  "dependencies": {
+    "@shakacode-tools/react-on-rails-pro-node-renderer": "16.1.1"
+  }
+}
+```
+
+**4. Scoped require statements:**
+
+```javascript
+const { reactOnRailsProNodeRenderer } = require('@shakacode-tools/react-on-rails-pro-node-renderer');
+```
+
+### Migration Steps
+
+#### Step 1: Update Gemfile
+
+**Remove** the GitHub Packages source and use standard gem installation:
+
+```diff
+- source "https://rubygems.pkg.github.com/shakacode-tools" do
+-   gem "react_on_rails_pro", "16.1.1"
+- end
++ gem "react_on_rails_pro", "~> 16.2"
+```
+
+Then run:
+
+```bash
+bundle install
+```
+
+#### Step 2: Remove .npmrc Configuration
+
+If you have a `.npmrc` file with GitHub Packages authentication, **delete it** or remove the GitHub-specific lines:
+
+```bash
+# Remove the entire file if it only contained GitHub Packages config
+rm .npmrc
+
+# Or edit it to remove these lines:
+# always-auth=true
+# //npm.pkg.github.com/:_authToken=YOUR_TOKEN
+# @shakacode-tools:registry=https://npm.pkg.github.com
+```
+
+#### Step 3: Update package.json
+
+Change the package name from **scoped** to **unscoped**:
+
+```diff
+{
+  "dependencies": {
+-   "@shakacode-tools/react-on-rails-pro-node-renderer": "16.1.1"
++   "react-on-rails-pro-node-renderer": "^16.2.0"
+  }
+}
+```
+
+Then reinstall:
+
+```bash
+npm install
+# or
+yarn install
+```
+
+#### Step 4: Update Require Statements
+
+Update all require/import statements to use the **unscoped** package name:
+
+**In your node renderer configuration file:**
+
+```diff
+- const { reactOnRailsProNodeRenderer } = require('@shakacode-tools/react-on-rails-pro-node-renderer');
++ const { reactOnRailsProNodeRenderer } = require('react-on-rails-pro-node-renderer');
+```
+
+**If using integrations (Sentry, Honeybadger):**
+
+```diff
+- require('@shakacode-tools/react-on-rails-pro-node-renderer/integrations/sentry').init();
++ require('react-on-rails-pro-node-renderer/integrations/sentry').init();
+
+- require('@shakacode-tools/react-on-rails-pro-node-renderer/integrations/honeybadger').init();
++ require('react-on-rails-pro-node-renderer/integrations/honeybadger').init();
+```
+
+#### Step 5: Configure License Token
+
+Add your React on Rails Pro license token as an environment variable:
+
+```bash
+export REACT_ON_RAILS_PRO_LICENSE="your-license-token-here"
+```
+
+**Or** configure it in your Rails initializer:
 
 ```ruby
-CUSTOMER_GITHUB_AUTH = '3f5fblahblahblah:x-oauth-basic'
-gem "react_on_rails_pro", git: "https://#{CUSTOMER_GITHUB_AUTH}@github.com/shakacode/react_on_rails_pro.git", tag: '1.0.0'
+# config/initializers/react_on_rails_pro.rb
+ReactOnRailsPro.configure do |config|
+  config.license_token = ENV["REACT_ON_RAILS_PRO_LICENSE"]
+end
+```
+
+⚠️ **Security Warning**: Never commit your license token to version control. Always use environment variables or secure secret management systems (Rails credentials, Heroku config vars, AWS Secrets Manager, etc.).
+
+**Where to get your license token:** Contact [justin@shakacode.com](mailto:justin@shakacode.com) if you don't have your license token.
+
+### Verify Migration
+
+#### 1. Verify Gem Installation
+
+```bash
+bundle list | grep react_on_rails_pro
+# Should show: react_on_rails_pro (16.2.0) or higher
+```
+
+#### 2. Verify NPM Package Installation
+
+```bash
+npm list react-on-rails-pro-node-renderer
+# or
+yarn list --pattern react-on-rails-pro-node-renderer
+
+# Should show: react-on-rails-pro-node-renderer@16.2.0 or higher
 ```
 
-## Update the client/package.json
+#### 3. Verify License Token
+
+Start your Rails server. You should see a success message in the logs:
 
-```sh
-CUSTOMER_GITHUB_AUTH=3f5fblahblahblah
-yarn add https://${CUSTOMER_GITHUB_AUTH}:x-oauth-basic@github.com/shakacode/react_on_rails_pro.git\#1.0.0
 ```
+React on Rails Pro license validated successfully
+```
+
+If the license is invalid or missing, you'll see an error with instructions.
+
+#### 4. Test Your Application
+
+- Start your Rails server
+- Start the node renderer (if using): `npm run node-renderer`
+- Verify that server-side rendering works correctly
+
+### Troubleshooting
+
+#### "Could not find gem 'react_on_rails_pro'"
+
+- Ensure you removed the GitHub Packages source from your Gemfile
+- Run `bundle install` again
+- Check that you have the correct version specified
+
+#### "Cannot find module 'react-on-rails-pro-node-renderer'"
+
+- Verify you updated all require statements to the unscoped name
+- Delete `node_modules` and reinstall: `rm -rf node_modules && npm install`
+- Check that package.json has the correct unscoped package name
+
+#### "License validation failed"
+
+- Ensure `REACT_ON_RAILS_PRO_LICENSE` environment variable is set
+- Verify the token string is correct (no extra spaces or quotes)
+- Contact [justin@shakacode.com](mailto:justin@shakacode.com) if you need a new token
+
+### Need Help?
+
+If you encounter issues during migration, contact [justin@shakacode.com](mailto:justin@shakacode.com) for support.