enabling external repo

Author: artiomgiza

gorm-formatter/README.md

@@ -4,7 +4,7 @@
 ### Usage:
 
 
-`go get github.com/gtforge/logart/gorm-formatter`
+`go get github.com/GettEngineering/logart/gorm-formatter`
 
 
 ```
@@ -31,7 +31,7 @@ type impl struct {
 ```
 This import:
 ```
-_ "github.com/gtforge/logart/gorm-formatter/automatic-setter"
+_ "github.com/GettEngineering/logart/gorm-formatter/automatic-setter"
 ```
 should be done directly in package
 
@@ -61,11 +61,11 @@ in stage/dev environments.
 
 - Short and humble (as we are) formatted log (made by this formatter)
 
-![alt text](https://github.com/gtforge/logart/blob/master/gorm-formatter/readme_files/logart_gorm_formatter.png "Example")
+![alt text](https://github.com/GettEngineering/logart/blob/master/gorm-formatter/readme_files/logart_gorm_formatter.png "Example")
 
 - Default (long and too colored) gorm formatted log:
 
-![alt text](https://github.com/gtforge/logart/blob/master/gorm-formatter/readme_files/default_gorm_formatter.png "Example")
+![alt text](https://github.com/GettEngineering/logart/blob/master/gorm-formatter/readme_files/default_gorm_formatter.png "Example")
 
 
 ### Technical details (advanced reading):

gorm-formatter/automatic-setter/automatic-setter.go

@@ -1,10 +1,8 @@
 package automaticsetter
 
-import (
-	"github.com/gtforge/logart/gorm-formatter"
-	"github.com/gtforge/services_common_go/gett-storages"
-)
-
 func init() {
-	gettStorages.DB.SetLogger(gormlogformatter.DefaultLogger())
+	// Once DB client reference is cloned, you might use this to
+	// enable log formatter:
+	//
+	// your.db.client.set.logger(gormlogformatter.DefaultLogger())
 }

gorm-formatter/formatter.go

@@ -198,7 +198,7 @@ func retrieveData(formatOptions FormatOptions, values ...interface{}) (knownForm
 	// OR
 
 	//[]interface {}{
-	//	"\x1b[35m(/Users/gizatullinartiom/go/src/github.com/gtforge/global_ride_management_service/pkg/partition_manager/partition_manager_dao.go:55)\x1b[0m",
+	//	"\x1b[35m(/Users/user/go/src/github.com/repo_name/lib/partition_manager_dao.go:55)\x1b[0m",
 	//	"\n\x1b[33m[2019-03-25 17:46:16]\x1b[0m",
 	//	"\x1b[31;1m",
 	//	&pq.Error{...},

logrus-human-formatter/README.md

@@ -1,11 +1,11 @@
 # logrus formatter
 
 
-![alt text](https://github.com/gtforge/logart/blob/master/logrus-human-formatter/readme_files/formatted.png "Example")
+![alt text](https://github.com/GettEngineering/logart/blob/master/logrus-human-formatter/readme_files/formatted.png "Example")
 
 ### Usage:
 
-`go get github.com/gtforge/logart/logrus-human-formatter`
+`go get github.com/GettEngineering/logart/logrus-human-formatter`
 
 Default setup:
 ```
@@ -109,18 +109,18 @@ For most of the usages in real life, it can be useful to differentiate between p
 and dev/stage environments. Most likely this formatter will be enabled on
 dev/stage (output is the terminal window - we want nice formatted log) and
 disabled on prod (log management systems). Of course on prod env we'll use
-another type of formatter, such as json formatter ([like this one](https://github.com/gtforge/logart/tree/master/logrus-json-formatter))
+another type of formatter, such as json formatter ([like this one](https://github.com/GettEngineering/logart/tree/master/logrus-json-formatter))
 
 ### Comparison:
 
 Here is couple of possible options to format the log. **Same** log is shown
 in three different ways:
 
 Colorized log (made by this formatter):
-![alt text](https://github.com/gtforge/logart/blob/master/logrus-human-formatter/readme_files/formatted.png "Example")
+![alt text](https://github.com/GettEngineering/logart/blob/master/logrus-human-formatter/readme_files/formatted.png "Example")
 
 Default log (logrus default):
-![alt text](https://github.com/gtforge/logart/blob/master/logrus-human-formatter/readme_files/default-formatter.png "Example")
+![alt text](https://github.com/GettEngineering/logart/blob/master/logrus-human-formatter/readme_files/default-formatter.png "Example")
 
 JSON formatted log (log is printed as JSON):
-![alt text](https://github.com/gtforge/logart/blob/master/logrus-human-formatter/readme_files/json-formatter.png "Example")
+![alt text](https://github.com/GettEngineering/logart/blob/master/logrus-human-formatter/readme_files/json-formatter.png "Example")

logrus-json-formatter/README.md

@@ -2,11 +2,11 @@
 
 
 JSON formatted log (log is printed as JSON):
-![alt text](https://github.com/gtforge/logart/blob/master/logrus-json-formatter/readme_files/json-formatter.png "Example")
+![alt text](https://github.com/GettEngineering/logart/blob/master/logrus-json-formatter/readme_files/json-formatter.png "Example")
 
 ### Usage:
 
-`go get github.com/gtforge/logart/logrus-json-formatter`
+`go get github.com/GettEngineering/logart/logrus-json-formatter`
 
 Default setup:
 ```
@@ -37,5 +37,5 @@ current "RequestID" or "SessionID" - depends infra code is running in.
 JSON formatter is good for log managements systems.
 
 To make the log more "human readable" (for example in dev/stage environments)
-another formatter should be used, see [human readable formatter](https://github.com/gtforge/logart/tree/master/logrus-human-formatter)
+another formatter should be used, see [human readable formatter](https://github.com/GettEngineering/logart/tree/master/logrus-human-formatter)
 for more info.