testdata/router | ||
.gitignore | ||
apiapp.go | ||
autorouter_test.go | ||
autorouter.go | ||
bale.go | ||
bee.go | ||
bee.json | ||
code.go | ||
conf.go | ||
g_appcode.go | ||
g_controllers.go | ||
g_docs.go | ||
g_migration.go | ||
g_model.go | ||
g_scaffold.go | ||
g_views.go | ||
g.go | ||
LICENSE | ||
migrate.go | ||
new.go | ||
pack.go | ||
README.md | ||
run.go | ||
rundocs.go | ||
test.go | ||
util.go | ||
version.go | ||
watch.go |
bee
Bee is a command line tool facilitating development with beego framework.
Requirements
- Go version >= 1.1.
Installation
Begin by installing bee
using go get
command.
go get github.com/beego/bee
Then you can add bee
binary to PATH environment variable in your ~/.bashrc
or ~/.bash_profile
file:
export PATH=$PATH:<your_main_gopath>/bin/bee
If you already have
bee
installed, updatingbee
is simple:
go get -u github.com/beego/bee
Basic commands
Bee provides a variety of commands which can be helpful at various stage of development. The top level commands include:
new create an application base on beego framework
run run the app which can hot compile
pack compress an beego project
api create an api application base on beego framework
bale packs non-Go files to Go source files
version show the bee & beego version
generate source code generator
migrate run database migrations
bee version
The first command is the easiest: displaying which version of bee
, beego
and go
is installed on your machine:
$ bee version
bee :1.2.2
beego :1.4.0
Go :go version go1.2.1 linux/amd64
bee new
Creating a new beego web application is no big deal, too.
$ bee new myapp
[INFO] Creating application...
/home/zheng/gopath/src/myapp/
/home/zheng/gopath/src/myapp/conf/
/home/zheng/gopath/src/myapp/controllers/
/home/zheng/gopath/src/myapp/models/
/home/zheng/gopath/src/myapp/routers/
/home/zheng/gopath/src/myapp/tests/
/home/zheng/gopath/src/myapp/static/
/home/zheng/gopath/src/myapp/static/js/
/home/zheng/gopath/src/myapp/static/css/
/home/zheng/gopath/src/myapp/static/img/
/home/zheng/gopath/src/myapp/views/
/home/zheng/gopath/src/myapp/conf/app.conf
/home/zheng/gopath/src/myapp/controllers/default.go
/home/zheng/gopath/src/myapp/views/index.tpl
/home/zheng/gopath/src/myapp/routers/router.go
/home/zheng/gopath/src/myapp/tests/default_test.go
/home/zheng/gopath/src/myapp/main.go
2014/08/29 15:45:47 [SUCC] New application successfully created!
bee run
bee pack
bee api
bee bale
bee migrate
bee generate
Shortcuts
Because you'll likely type these generator commands over and over, it makes sense to create aliases.
# Generator Stuff
alias g:a="bee generate appcode"
alias g:m="bee generate model"
alias g:c="bee generate controller"
alias g:v="bee generate view"
alias g:mi="bee generate migration"
These can be stored in, for example, your ~/.bash_profile
or ~/.bashrc
files.
Help
If you happend to forget the usage of a command, you can always find the usage information by bee help <command>
.
For instance, to get more information about the run
command:
$ bee help run
usage: bee run [appname] [watchall] [-main=*.go] [-downdoc=true] [-gendoc=true]
start the appname throw exec.Command
then start a inotify watch for current dir
when the file has changed bee will auto go build and restart the app
file changed
|
check if it's go file
|
yes no
| |
go build do nothing
|
restart app