Commit 52d490c9 authored by Andrew Hazelden's avatar Andrew Hazelden

Reactor Docs

parent 2f803050
......@@ -150,11 +150,11 @@ ul, ol {
color: #C4C4C4;
}
ul li > :first-child,
ol li > :first-child,
ul li ul:first-of-type,
ol li ol:first-of-type,
ul li ol:first-of-type,
ul li > :first-child,
ol li > :first-child,
ul li ul:first-of-type,
ol li ol:first-of-type,
ul li ol:first-of-type,
ol li ul:first-of-type {
margin-top: 0px;
}
......@@ -298,8 +298,8 @@ table th {
}
table th, table td {
/* border: 1px solid #ccc; */
/* padding: 6px 13px; */
/* border: 1px solid #ccc; */
/* padding: 6px 13px; */
}
table tr {
......@@ -366,9 +366,12 @@ img {
<p>or</p>
<p><code>REACTOR_INSTALL_PATHMAP=Profile:</code></p>
<p>or your own custom Reactor installation location on a local or network path like:</p>
<p><code>REACTOR_INSTALL_PATHMAP=E:\Pipeline\Reactor</code><br />
<code>REACTOR_INSTALL_PATHMAP=/Volumes/Pipeline/Reactor</code><br />
<code>REACTOR_INSTALL_PATHMAP=/opt/Reactor</code></p>
<pre><code> REACTOR_INSTALL_PATHMAP=E:\Pipeline\Reactor
REACTOR_INSTALL_PATHMAP=/Volumes/Pipeline/Reactor
REACTOR_INSTALL_PATHMAP=/opt/Reactor
</code></pre>
<p>On Windows you would open the <strong>System Control Panel &gt; Advanced System Settings &gt; Environment Variables...</strong> window and add a new <code>REACTOR_INSTALL_PATHMAP</code> entry like this:</p>
<p><img src="Images/windows-adding-an-environment-variable.png" alt="Windows Environment Variable" /></p>
<h3><a name="reactor-local-system"></a>Reactor Local System</h3>
<p>The <code>REACTOR_LOCAL_SYSTEM</code> environment variable allows you to do local development of the files in the <code>Reactor:/System/</code> folder without needing to git sync each of those revisions with the Reactor GitLab repository.</p>
<p>Whatever folderpath you define in the <code>REACTOR_LOCAL_SYSTEM</code> environment variable will be used as a local source of the <code>Reactor:/System/</code> folder contents. When you run the <strong>Reactor &gt; Open Reactor...</strong> menu item the <code>REACTOR_LOCAL_SYSTEM</code> defined files will be copied automatically to the <code>Reactor:/System/</code> folder.</p>
......@@ -416,8 +419,9 @@ img {
-rw-r--r--@ 1 root wheel 473 Dec 7 22:23 setenv.reactor.REACTOR_INSTALL_PATHMAP.plist
</code></pre>
<p>If you don't want to install the .plist files in the system wide LaunchAgents folder you have the option to use a user account specific entry of:</p>
<pre><code> $HOME/Library/LaunchAgents/</code></pre>
<pre><code> $HOME/Library/LaunchAgents/
</code></pre>
<p>On MacOS you can type <code>env</code> into the Terminal window to see all of the active environment variables on the system.</p>
<p>Last Revised 2018-05-21</p>
<p>Last Revised 2018-07-16</p>
</body>
</html>
</html>
\ No newline at end of file
......@@ -67,9 +67,13 @@ or
or your own custom Reactor installation location on a local or network path like:
`REACTOR_INSTALL_PATHMAP=E:\Pipeline\Reactor`
`REACTOR_INSTALL_PATHMAP=/Volumes/Pipeline/Reactor`
`REACTOR_INSTALL_PATHMAP=/opt/Reactor`
REACTOR_INSTALL_PATHMAP=E:\Pipeline\Reactor
REACTOR_INSTALL_PATHMAP=/Volumes/Pipeline/Reactor
REACTOR_INSTALL_PATHMAP=/opt/Reactor
On Windows you would open the **System Control Panel > Advanced System Settings > Environment Variables...** window and add a new `REACTOR_INSTALL_PATHMAP` entry like this:
![Windows Environment Variable](Images/windows-adding-an-environment-variable.png)
### <a name="reactor-local-system"></a>Reactor Local System ###
......@@ -145,4 +149,4 @@ If you don't want to install the .plist files in the system wide LaunchAgents fo
On MacOS you can type `env` into the Terminal window to see all of the active environment variables on the system.
Last Revised 2018-05-28
Last Revised 2018-07-16
......@@ -2,8 +2,8 @@ Atom {
Name = "Reactor Docs",
Category = "Docs",
Author = "We Suck Less",
Version = 2.0,
Date = {2018, 5, 28},
Version = 2.01,
Date = {2018, 7, 16},
Description = [[<h2>Reactor Documentation</h2>
<p>This package includes HTML and Markdown (.md) format documentation that covers Reactor usage and atom package creation.</p>
......@@ -62,6 +62,7 @@ https://gitlab.com/WeSuckLess/Reactor/blob/master/README.md</p>
"Docs/ReactorDocs/Images/reactorlog-textfile.png",
"Docs/ReactorDocs/Images/taskbar-render-node-settings.png",
"Docs/ReactorDocs/Images/uninstall-pathmap-entries.png",
"Docs/ReactorDocs/Images/windows-adding-an-environment-variable.png",
"Docs/ReactorDocs/Images/windows-environment-variables.png",
"Docs/ReactorDocs/Installing-Reactor.html",
"Docs/ReactorDocs/Installing-Reactor.md",
......
......@@ -67,9 +67,13 @@ or
or your own custom Reactor installation location on a local or network path like:
`REACTOR_INSTALL_PATHMAP=E:\Pipeline\Reactor`
`REACTOR_INSTALL_PATHMAP=/Volumes/Pipeline/Reactor`
`REACTOR_INSTALL_PATHMAP=/opt/Reactor`
REACTOR_INSTALL_PATHMAP=E:\Pipeline\Reactor
REACTOR_INSTALL_PATHMAP=/Volumes/Pipeline/Reactor
REACTOR_INSTALL_PATHMAP=/opt/Reactor
On Windows you would open the **System Control Panel > Advanced System Settings > Environment Variables...** window and add a new `REACTOR_INSTALL_PATHMAP` entry like this:
![Windows Environment Variable](Images/windows-adding-an-environment-variable.png)
### <a name="reactor-local-system"></a>Reactor Local System ###
......@@ -141,4 +145,4 @@ You will then see a directory listing that looks something like this:
On MacOS you can type `env` into the Terminal window to see all of the active environment variables on the system.
Last Revised 2018-05-21
Last Revised 2018-07-16
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment