liudng / dogo

Monitoring changes in the source file and automatically compile and run (restart).

dogo

Monitoring changes in the source file and automatically compile and run (restart).

中文

Install

go get github.com/liudng/dogo

Create config

Here's a config file sample, save the file as dogo.json:

{
    "WorkingDir": "{GOPATH}/src/github.com/liudng/dogo/example",
    "SourceDir": [
        "{GOPATH}/src/github.com/liudng/dogo/example"
    ],
    "SourceExt": [".c", ".cpp", ".go", ".h"],
    "BuildCmd": "go build github.com/liudng/dogo/example",
    "RunCmd": "example.exe",
    "Decreasing": 1
}

WorkingDir: working directory, dogo will auto change to this directory.

SourceDir: the list of source directories.

SourceExt: monitoring file type.

BuildCmd: the command of build and compile.

RunCmd: the program (full) path.

Decreasing: Ignore the number of modifies, it's only start counting after build success. Now it's supported in linux and windows.

Start monitoring

type the command to start:

dogo

or, specify a config file with -c

dogo -c=/path/to/dogo.json

the path can contain {GOPATH}.

screen capture

dogo's Issues

mac 使用重新编译的时候提示错误

[dogo] Changed files: sms.go
[dogo] Terminate the process 21062:
exit status 1---

Exlude directories option

Is it possible to exclude certain directories? We have a node_modules directory and a vendor directory and these have a lot of files. Even putting a file extension as .go doensn't do much help.

Improve test coverage

use DelayTime instead of Decreasing

I use sublime to edit my file. After I press ctr+s, sublime will format my file and save it again.
dogo will get two modify events and trigger 2 build and run. (because my app is web, it will report port is used error)
If dogo delay 0.5 second to build and run, there will be no such issue.
Maybe we don't need decreasing but just increase DelayTime, then we will not ignore any change.

ignore some directory. such as vendor

RunCmd 如何支持参数？

There is no monitoring of new files and delete files

using with code generation causes looping behavior

In my project, I am using a Makefile that causes code generation. The build command, thus results in new .go files being created/changed, which triggers dogo to restart the build process, and now it starts looping. I think listening for changes should be paused until the build commend process exits.

Empty directory cause an infinite loop

朋友。这个组件，无法同时监控多个工程，也就是多个项目路径吧。

RT 目前我看只支持一个go工程目录吧。配置多个的话，就只监控最后一个。

Deleting source file causes infinite error

Hi, "dogo" is really simplifying my workflow, thank you guys for creating and maintaining this utility but one thing makes me sad sometimes.

Let's say I have the following scenario:

1. Create new file(let's say "test.go")
2. Start "dogo"
3. Remove file

In result "dogo" will constantly log: stat %filepath%: no such file or directory and I need to restart in order to continue the auto build. I'm using the latest version on OS X El Capitan by the way.

BuildCmd and RunCmd can be set for multiple commands?

Runcmd is launched with wrong working dir

Executable file should have working dir set to filepath.dir("[runcmd command]").
Why exist both "WorkingDir" and "SourceDir" if they must have the same value?
I use "go install" as build command and wouldn't want to switch to an arbitrary build.
(apart from issue it'a very useful utility)

Display configuration node.