mirror of
https://github.com/ergochat/ergo.git
synced 2024-11-10 22:19:31 +01:00
readme: Update a lil more
This commit is contained in:
parent
391c6a8c31
commit
026ff5cb12
16
README.md
16
README.md
@ -67,18 +67,20 @@ The `stable` branch contains the latest release. You can run this for a producti
|
|||||||
|
|
||||||
#### Building
|
#### Building
|
||||||
|
|
||||||
[![Build Status](https://travis-ci.org/oragono/oragono.svg?branch=master)](https://travis-ci.org/oragono/oragono)
|
Clone the appropriate branch. You should also run this command to set up vendored dependencies:
|
||||||
|
```
|
||||||
|
git submodule update --init
|
||||||
|
```
|
||||||
|
|
||||||
Clone the appropriate branch. You should also run `git submodule update --init` to set up vendored dependencies.
|
From the root folder, you can run `make`, using [GoReleaser](https://goreleaser.com/) to generate all of our release binaries in `/dist`:
|
||||||
|
|
||||||
From the root folder, run `make` to generate all release files in `/dist` for all of our target OSes:
|
|
||||||
```
|
```
|
||||||
make
|
make
|
||||||
```
|
```
|
||||||
|
|
||||||
Otherwise, if you'd like to manually build a very specific executable, you can run the typical `go build oragono.go` command.
|
However, when just developing I instead just use this command to rebuild and run Oragono on the fly with the latest changes:
|
||||||
|
```
|
||||||
However, when just developing I usually execute `go run oragono.go`. That rebuilds Oragono on the fly with the latest changes.
|
go run oragono.go
|
||||||
|
```
|
||||||
|
|
||||||
|
|
||||||
## Configuration
|
## Configuration
|
||||||
|
Loading…
Reference in New Issue
Block a user