annismckenzie/fleet-ui

Web based UI for fleet

fleet-ui

Web based UI for fleet

Getting started

(1) run docker container

• -e ETCD_PEER=protocol://your_etcd_peer_ip:peer_port
• -e BIND=bind_ip:bind_port
• -p port:3000
• -v your_ssh_private_key_file_path:/root/id_rsa

docker run --rm -p 3000:3000 -e ETCD_PEER=http://10.0.0.1:4001 -v ~/.ssh/id_rsa:/root/id_rsa purpleworks/fleet-ui

(2) enjoy!

Prerequire

• backend
  • go
  • fleetctl
• frontend
  • nodejs
  • yeoman
  • grunt
  • bower
  • ruby
  • compass

Organize your workspace

clone your forked github repository to workspace($GOPATH)

$ mkdir $GOPATH/src/github.com
$ cd $GOPATH/src/github.com
$ git clone git@github.com:your_name/fleet-ui.git

here's an example:

bin/
pkg/
src/
    github.com/
        your_name/
          fleet-ui/
              .git/
              .dockerignore
              .gitignore
              CHANGELOG.md
              Dockerfile
              README.md
              angular
              app.go
              (...)

Development

backend (api server)

$ go install
$ fleet-ui -etcd-peer=[protocol://your_etcd_peer_ip:your_etcd_peer_port] -bind=[bind_ip:bind_port]

frontend (web based ui)

$ cd angular
$ npm install
$ bower install
$ grunt server

Build All

$ ./build.sh

LINK

• fleet-ui API list
• coreos/fleet
• coreos-clustering document
• fleet unit file

Contributing

1. Fork it ( https://github.com/purpleworks/fleet-ui/fork )
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create a new Pull Request

License

MIT (see LICENSE file)