KSP-SpaceDock · Feb 16, 2018
diff --git a/Diff for: ‎README.md
+4-2 b/Diff for: ‎README.md
+4-2
diff --git a/Diff for: ‎build/fetch_plugins.ps1
100644100755 b/Diff for: ‎build/fetch_plugins.ps1
100644100755
diff --git a/Diff for: ‎build/fetch_plugins.sh
100644100755
+4-3 b/Diff for: ‎build/fetch_plugins.sh
100644100755
+4-3
diff --git a/Diff for: ‎build/install_glide.ps1
100644100755 b/Diff for: ‎build/install_glide.ps1
100644100755
diff --git a/Diff for: ‎build/install_glide.sh
100644100755 b/Diff for: ‎build/install_glide.sh
100644100755
diff --git a/Diff for: ‎config/config.example.yml
+2-2 b/Diff for: ‎config/config.example.yml
+2-2
@@ -2,8 +2,8 @@
 SpaceDock is an open source website software that can host modifications for multiple games. It started as a fork of the popular KerbalStuff software for Kerbal Space Program and evolved since then.
 
 SpaceDock is split into two parts:
-* The frontend, which is not released under an open source license and unavailable to the public
-* The backend which is licensed as MIT and free for everyone to use.
+* The frontend, which is currently developed under the name [OpenDock](https://github.com/KSP-SpaceDock/OpenDock)
+* The backend which developed here.
 
 The backend handles all the content that SpaceDock stores, like mods and users. The program is designed to be as lightweight as possible to distribute it across multiple nodes. A frontend can then query the multiple nodes. Due to the modular nature of the framework, third party persons who are interested in mod hosting can either host their own backend together with a custom frontend, or create just a frontend and rely on SpaceDocks infrastructure internally to host their mods. This allows for flexible and easily customised mod repositories (once there are free frontends available)
 
@@ -51,6 +51,8 @@ Well, "plugins"...
 
 If you want to use plugins in your SpaceDock instance, you need to enter their goland dependency urls into build/plugins.txt. You can use full glide versioning syntax here. After doing so, you need to run `build/fetch_plugins.sh` if you are on Linux/MacOS or `build/fetch_plugins.ps1` on Windows. This will create a file called `build_sdb.go` that includes the specified plugins and fetch them using glide.
 
+Even if you don't plan to use plugins, execute the `fetch_plugins` script. It will work without a `build/plugins.txt` file being present, and just creates the `build_sdb.go` file.
+
 #### Building and starting the application
 To build the app you need to call `go build` on the `build_sdb.go` file. The only difference between Linux and Windows is, that Windows users should use `sdb.exe` instead of `sdb`
 
 
@@ -12,10 +12,11 @@ while IFS= read -r line; do
     then
         if [ -e "$PWD/build/plugins.txt" ]
         then
-            while IFS= read -r line2; do 
+            for line2 in `cat $PWD/build/plugins.txt`; do
+                echo $line2
                 FILE="$FILE    _ \"$line2\"\n"
-                $GOPATH/bin/glide get $line2 || true
-            done < $PWD/build/plugins.txt
+                glide get $line2 || true
+            done
         fi
     fi        
     FILE="$FILE$line\n"
 
@@ -32,8 +32,8 @@ smtp-password: ""
 smtp-tls: false
 
 # SQL settings
-dialect: "mysql"
-connection-data: ""
+dialect: "postgres"
+connection-data: "postgresql://user:password@host/dbname?sslmode=disable"
 
 # Absolute path to the directory you want to store mods in
 storage: ""