Fix config switch issue and update docs

Author: ethanhann

docs-src/commands.md

@@ -28,7 +28,7 @@ paket add InEngine.Core
 
 Adding a class that implements **InEngine.Core.ICommand** is the simplest way to create a command.
 
-```csharp
+```c#
 using System;
 using InEngine.Core;
 
@@ -48,7 +48,7 @@ namespace MyCommandPlugin
 Extending the **InEngine.Core.AbstractCommand** class adds extra functionality, like a logger, a progress bar, and the ability to schedule the command using the scheduler.
 Minimally, the Run method should be overridden.
 
-```csharp
+```c#
 using System;
 using InEngine.Core;
 
@@ -72,7 +72,7 @@ Create a class that implements **InEngine.Core.IOptions** in the same assembly a
 Add a VerbOptions attribute from the CommandLine namespace that defines the name of the command and optional help text.
 The help text can be auto-generated from the attribute or manually specified in the GetUsage method.  
 
-```csharp
+```c#
 using CommandLine;
 using CommandLine.Text;
 using InEngine.Core;
@@ -179,15 +179,15 @@ Copyright © Ethan Hann 2017
 
 The **InEngine.Core.AbstractCommand** class provides some helper functions to output text to the console: 
 
-```csharp
+```c#
 IWrite Newline();
 IWrite Info(string val);
 IWrite Warning(string val);
 IWrite Error(string val);
 IWrite Line(string val);
 ```
 
-```csharp
+```c#
 public override CommandResult Run()
 {
     Info("Display some information");
@@ -196,13 +196,13 @@ public override CommandResult Run()
 
 Display an error message, use the Error method.
 
-```csharp
+```c#
 Error("Display some information");
 ```
 
 Display a warning message, use the Warning method.
 
-```csharp
+```c#
 Error("Display some information");
 ```
 
@@ -214,7 +214,7 @@ Line("This is a plain line.");
 
 The **InEngine.Core.AbstractCommand** class provides a Logger property. It implements the **NLog.ILogger** interface.
 
-```csharp
+```c#
 public override CommandResult Run()
 {
     Logger.Trace("Sample trace message");
@@ -250,7 +250,7 @@ Setup an [NLog configuration](https://github.com/NLog/NLog/wiki/Tutorial#configu
 
 The **InEngine.Core.AbstractCommand** class provides a ProgressBar property. This is how it is used.
 
-```csharp
+```c#
 public override CommandResult Run()
 {
     // Define the ticks (aka steps) for the command...

docs-src/configuration.md

@@ -0,0 +1,24 @@
+# Configuration 
+
+Configuration is accomplished by modifying the appsettings.json file that comes with the InEngine.NET binary distribution.
+
+
+```json
+{
+  "InEngine": {
+    "Queue": {
+      "QueueName": "InEngine:Queue",
+      "RedisHost": "localhost",
+      "RedisPort": 6379,
+      "RedisDb": 0,
+      "RedisPassword": ""
+    }
+  }
+}
+```
+
+The -c, --configuration argument can also be used to specify an alternate configuration file.
+
+
+
+

docs-src/css/style.css

@@ -1,22 +0,0 @@
-
-.navbar-default {
-    background: #0a69fa;
-}
-
-.navbar-default .navbar-nav > .active > a,
-.navbar-default .navbar-nav > .active > a:hover,
-.navbar-default .navbar-nav > .active > a:focus {
-    background-color: #0a69fa;
-}
-
-.navbar-default .navbar-nav > li > a:hover,
-.navbar-default .navbar-nav > li > a:focus {
-    background-color: #0a69fa;
-}
-
-a,
-a:hover,
-a:focus {
-  color: #2200CC;
-}
-

docs-src/img/favicon.ico renamed to docs-src/images/favicon.ico

@@ -1,8 +1,3 @@
-# InEngine.NET
- 
 InEngine.NET allows commands to be queued, scheduled, and run directly. 
 
-
-## How to Get Started
-
-Get started by reading up on [commands](commands).
+Get started by reading up on [commands](commands), then [scheduling](scheduling) and [queuing](queuing).

docs-src/index.md

@@ -27,7 +27,7 @@ It is highly recommended to <a href="https://redis.io/topics/security#authentica
 
 [Commands](commands) can be published programmatically with the **InEngine.Core.Queue.Broker** class:
 
-```csharp
+```c#
 Broker.Make().Publish(new MyCommand());
 ```
 
@@ -51,13 +51,13 @@ inengine.exe -pInEngine.Core queue:publish --command-assembly=InEngine.Core.dll
 #### Programmatically
 Consuming a command is also accomplished with the Broker class:
 
-```csharp
+```c#
 Broker.Make().Consume();
 ```
 
 Both methods take an optional second argument to indicate if the secondary queue should be used instead of the primary queue.
 
-```csharp
+```c#
 // Uses secondary queue.
 Broker.Make().Consume(true);
 ```
@@ -70,7 +70,7 @@ Commands can be consumed from the command line as well with this simple command:
 inengine.exe -pInEngine.Core queue:consume
 ```
 
-use the **--secondary** switch to consume the secondary queue instead of the primary queue:
+Use the **--secondary** switch to consume the secondary queue instead of the primary queue:
 
 ```bash
 inengine.exe -pInEngine.Core queue:consume --secondary
@@ -80,3 +80,18 @@ inengine.exe -pInEngine.Core queue:consume --secondary
 
 The InEngine scheduler is needed to consume queued messages in the background. 
 There are a variety of [ways to run the scheduler](scheduling/#running-the-scheduler).
+
+
+## Primary and Secondary Queue
+
+Other than the fact that the primary queue is used by default, there is difference between the primary and secondary queues. 
+However, it is often desirable to have more than 1 queue. 
+For example, long running jobs might be sent to the secondary queue, 
+while jobs that are expected to finish after only a few moments are sent to the primary queue.
+
+What about 3, 4, 900 queues? This gets to be a pain to manage and, practically speaking, is probably unnecessary.
+If it is desirable, different [configuration files](configuration) can be used to run multiple instances of InEngine.NET.
+
+ 
+  
+

docs-src/queuing.md

@@ -6,7 +6,7 @@
 
 A job schedule is created by adding a class to your plugin assembly that implements the **InEngine.Core.Jobs** interface.
 
-```csharp
+```c#
 
 using System;
 using Quartz;
@@ -26,7 +26,7 @@ namespace MyCommandPlugin
 This class is automatically discovered by the InEngine.NET scheduler.
 It will call the Jobs.Schedule method with an initialized Quartz.NET scheduler object.
 
-```csharp
+```c#
 using System;
 using Quartz;
 

docs-src/scheduling.md

@@ -1,16 +1,36 @@
 docs_dir: docs-src
 site_dir: docs
 site_name: InEngine.NET
+repo_name: 'InEngine.NET'
 repo_url: https://github.com/InEngine-NET/InEngine.NET
 site_author: Ethan Hann
 copyright: © 2017 - Ethan Hann
+edit_uri: ''
 
 pages:
 - Getting Started: 'index.md'
 - Documentation:
   - commands.md
   - scheduling.md
   - queuing.md
+  - configuration.md
 
 extra_css:
     - css/style.css
+
+theme:
+  name: 'material'
+  favicon: 'images/favicon.ico'
+  logo: 'images/inengine-logo-32-alt.png'
+  palette:
+    primary: 'blue'
+    accent: 'blue'
+  feature:
+    tabs: false
+
+markdown_extensions:
+  - admonition
+  - codehilite:
+      guess_lang: false
+  - toc:
+      permalink: true

mkdocs.yml

@@ -7,14 +7,15 @@ namespace InEngine.Core
     public class InEngineSettings
     {
         public static string BasePath { get; set; } = Directory.GetCurrentDirectory();
+        public static string ConfigurationFile { get; set; } = "appsettings.json";
         public QueueSettings Queue { get; set; }
 
         public static InEngineSettings Make()
         {
             var inEngineSettings = new InEngineSettings();
             new ConfigurationBuilder()
                 .SetBasePath(BasePath)
-                .AddJsonFile("appsettings.json")
+                .AddJsonFile(ConfigurationFile)
                 .Build()
                 .GetSection("InEngine")
                 .Bind(inEngineSettings);

src/InEngine.Core/InEngineSettings.cs

@@ -21,13 +21,14 @@ public Plugin(Assembly assembly)
 
         public static Plugin LoadFrom(string assemblyPath)
         {
+            var path = Path.Combine(InEngineSettings.BasePath, assemblyPath);
             try
             {
-                return new Plugin(Assembly.LoadFrom(Path.Combine(InEngineSettings.BasePath, assemblyPath)));   
+                return new Plugin(Assembly.LoadFrom(path));   
             }
             catch (Exception exception)
             {
-                throw new PluginNotFoundException($"Could not load plugin: {assemblyPath}", exception);
+                throw new PluginNotFoundException($"Plugin not found at {path}", exception);
             }
         }