|
@@ -67,18 +67,20 @@ The `stable` branch contains the latest release. You can run this for a producti
|
67
|
67
|
|
68
|
68
|
#### Building
|
69
|
69
|
|
70
|
|
-[![Build Status](https://travis-ci.org/oragono/oragono.svg?branch=master)](https://travis-ci.org/oragono/oragono)
|
71
|
|
-
|
72
|
|
-Clone the appropriate branch. You should also run `git submodule update --init` to set up vendored dependencies.
|
|
70
|
+Clone the appropriate branch. You should also run this command to set up vendored dependencies:
|
|
71
|
+```
|
|
72
|
+git submodule update --init
|
|
73
|
+```
|
73
|
74
|
|
74
|
|
-From the root folder, run `make` to generate all release files in `/dist` for all of our target OSes:
|
|
75
|
+From the root folder, you can run `make`, using [GoReleaser](https://goreleaser.com/) to generate all of our release binaries in `/dist`:
|
75
|
76
|
```
|
76
|
77
|
make
|
77
|
78
|
```
|
78
|
79
|
|
79
|
|
-Otherwise, if you'd like to manually build a very specific executable, you can run the typical `go build oragono.go` command.
|
80
|
|
-
|
81
|
|
-However, when just developing I usually execute `go run oragono.go`. That rebuilds Oragono on the fly with the latest changes.
|
|
80
|
+However, when just developing I instead just use this command to rebuild and run Oragono on the fly with the latest changes:
|
|
81
|
+```
|
|
82
|
+go run oragono.go
|
|
83
|
+```
|
82
|
84
|
|
83
|
85
|
|
84
|
86
|
## Configuration
|