added linux-release, more readme

Makefile

@@ -66,13 +66,18 @@ build: prep linux windows
 linux:
 > @GOOS=$@ GOARCH=$(arch) go build -o build/$@/$(progName) . && echo $@ "Build success" || echo $@ "[FAILED] go build"
 
+linux-release:
+> @GOOS=linux GOARCH=$(arch) go build -ldflags=${linkerflags} -o build/linux/$(progName)-linux-$(arch)-$(releaseTag) . && echo $@ "Build success" || echo $@ "[FAILED] go build"
+
 windows:
-> @GOOS=$@ GOARCH=$(arch) go build -o build/$@/$(progName)-$(arch)-$(releaseTag).exe . && echo $@ "Build success" || echo $@ "[FAILED] go build"
+> @GOOS=$@ GOARCH=$(arch) go build -o build/$@/$(progName)-$@-$(arch)-$(releaseTag).exe . && echo $@ "Build success" || echo $@ "[FAILED] go build"
 
 build-production: prep linx-production
 
 linux-production:
-> @GOOS=linx GOARCH=$(arch) go build -ldflags=${linkerflags} -o build/$@/$(progName) . && echo "production build success" || echo "[FAILED] production build"
+> @GOOS=linux GOARCH=$(arch) go build -ldflags=${linkerflags} -o build/$@/$(progName) . && echo "production build success" || echo "[FAILED] production build"
+
+release: prep linux-release windows
 
 #-------------------------------------------------------------
 # Install - same as build, but places binary on system path
@@ -85,4 +90,4 @@ install-production: prep
 > @go install -ldflags=${linkerflags} . && echo "Production build and install success" || echo "[FAILED] Production install"
 
 ## Commands that don't relate to a specific file
-.PHONY: help confirm clean prep build build-production linux windows amd64
+.PHONY: help confirm clean prep build build-production linux windows amd64 release

README.md

@@ -9,24 +9,30 @@ Use scaffold to setup a new project with a directory skeleton of your design, an
 - A new project directory is created
 - Your project skeleton/template is copied from your config/projectType/sample directory
 - your setup/initialization commmands are run
+- And if you enable them
   - a git repository is initialized in the project directory
-  - and if you enable it, a remote repository is created and setup
+  - a remote repository is created and setup
+  - a gitea repository is created and setup
 
 ## Installation
 
-1 - Grab a version for your system from the releases page.
-2 - Put it in a directory that is on your path.
-3 - now configure your preferred setups/layouts/skeletons/templates for your projects.
+1. Grab a version for your system from the releases page.
+2. Put it in a directory that is on your path.
+3. Now configure your preferred setups/layouts/skeletons/templates for your projects.
 
 ## Configuration
 
-On linux the configuration directory will be at /home/user/.config/devel/scaffold
+On linux, the configuration directory will be at /home/user/.config/devel/scaffold
 
 For the windows versions, you might want to look at your User_Configuration_Directories location, and change it according to your needs. On windows it's value is the %APPDATA% environment variable.
 
 In a PowerShell, use `Get Child-Item Env:` to display all the environment variables.
 Then `[Environment]::SetEnvironmentVariable("APPDATA","C:\Users\You\Wherever-you-like\","User")` to set the new value.
 
+It's a little simpler at a command prompt -- type the command `set` and hit `Enter`. See what `APPDATA` is currently set to. Change it with `setx APPDATA "C:\Users\You\SomeWhere"`.
+
+The examples directory contains an example-scaffold-projectType.toml configuration file. Place a copy in each projectType directory, adjusted to your preferences per the given project type.
+
 ## The `scaffold` command
 
 | Command | Description |