1
- # GoDotEnv [ ![ Build Status] ( https://travis-ci.org/mniak /godotenv.svg?branch=master )] ( https://travis-ci.org/mniak /godotenv ) [ ![ Build status] ( https://ci.appveyor.com/api/projects/status/9v40vnfvvgde64u4?svg=true )] ( https://ci.appveyor.com/project/mniak /godotenv ) [ ![ Go Report Card] ( https://goreportcard.com/badge/github.com/mniak /godotenv )] ( https://goreportcard.com/report/github.com/mniak /godotenv )
1
+ # GoDotEnv [ ![ Build Status] ( https://travis-ci.org/joho /godotenv.svg?branch=master )] ( https://travis-ci.org/joho /godotenv ) [ ![ Build status] ( https://ci.appveyor.com/api/projects/status/9v40vnfvvgde64u4?svg=true )] ( https://ci.appveyor.com/project/joho /godotenv ) [ ![ Go Report Card] ( https://goreportcard.com/badge/github.com/joho /godotenv )] ( https://goreportcard.com/report/github.com/joho /godotenv )
2
2
3
3
A Go (golang) port of the Ruby dotenv project (which loads env vars from a .env file)
4
4
@@ -17,12 +17,12 @@ There is test coverage and CI for both linuxish and windows environments, but I
17
17
As a library
18
18
19
19
``` shell
20
- go get github.com/mniak /godotenv
20
+ go get github.com/joho /godotenv
21
21
```
22
22
23
23
or if you want to use it as a bin command
24
24
``` shell
25
- go get github.com/mniak /godotenv/cmd/godotenv
25
+ go get github.com/joho /godotenv/cmd/godotenv
26
26
```
27
27
28
28
## Usage
@@ -40,7 +40,7 @@ Then in your Go app you can do something like
40
40
package main
41
41
42
42
import (
43
- " github.com/mniak /godotenv"
43
+ " github.com/joho /godotenv"
44
44
" log"
45
45
" os"
46
46
)
@@ -61,7 +61,7 @@ func main() {
61
61
If you're even lazier than that, you can just take advantage of the autoload package which will read in ` .env ` on import
62
62
63
63
``` go
64
- import _ " github.com/mniak /godotenv/autoload"
64
+ import _ " github.com/joho /godotenv/autoload"
65
65
```
66
66
67
67
While ` .env ` in the project root is the default, you don't have to be constrained, both examples below are 100% legit
@@ -177,11 +177,11 @@ Contributions are most welcome! The parser itself is pretty stupidly naive and I
177
177
178
178
Releases should follow [ Semver] ( http://semver.org/ ) though the first couple of releases are ` v1 ` and ` v1.1 ` .
179
179
180
- Use [ annotated tags for all releases] ( https://github.com/mniak /godotenv/issues/30 ) . Example ` git tag -a v1.2.1 `
180
+ Use [ annotated tags for all releases] ( https://github.com/joho /godotenv/issues/30 ) . Example ` git tag -a v1.2.1 `
181
181
182
182
## CI
183
183
184
- Linux: [ ![ Build Status] ( https://travis-ci.org/mniak /godotenv.svg?branch=master )] ( https://travis-ci.org/mniak /godotenv ) Windows: [ ![ Build status] ( https://ci.appveyor.com/api/projects/status/9v40vnfvvgde64u4 )] ( https://ci.appveyor.com/project/mniak /godotenv )
184
+ Linux: [ ![ Build Status] ( https://travis-ci.org/joho /godotenv.svg?branch=master )] ( https://travis-ci.org/joho /godotenv ) Windows: [ ![ Build status] ( https://ci.appveyor.com/api/projects/status/9v40vnfvvgde64u4 )] ( https://ci.appveyor.com/project/joho /godotenv )
185
185
186
186
## Who?
187
187
0 commit comments