Dev/code reorg (#1)

* code reorg + initial beta release

Author: ppetko

.circleci/config.yml

@@ -0,0 +1,13 @@
+# Golang CircleCI 2.0 configuration file
+#
+# Check https://circleci.com/docs/2.0/language-go/ for more details
+version: 2
+jobs:
+  build:
+    docker:
+      - image: circleci/golang:1.11
+    working_directory: /go/src/github.com/ppetko/gopxe
+    steps:
+      - checkout
+      - run: go get -v -t -d ./...
+      - run: go test -v ./...

CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+## Code of Conduct
+
+### Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+### Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+### Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+### Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+### Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+### Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,16 @@
+# Contributing
+
+When contributing to this repository, please first discuss the change you wish to make via issue,
+email, or any other method with the owners of this repository before making a change. 
+
+Please note we have a code of conduct, please follow it in all your interactions with the project.
+
+## Pull Request Process
+
+1. Fork the project
+2. Create a topic branch from master.
+3. Make some commits to improve the project.
+4. Push this branch to your GitHub project.
+5. Open a Pull Request on GitHub.
+6. Discuss, and optionally continue committing.
+7. The project owner merges or closes the Pull Request.

Dockerfile

@@ -1,18 +1,21 @@
-FROM centos:7.3.1611
-
-RUN yum install tftp tftp-server* xinetd* dhcp* -y && \
-   yum clean all
-
-RUN mkdir /var/lib/tftpboot/pxelinux.cfg
+FROM golang:latest as builder 
+RUN mkdir -p /go/src/github.com/ppetko/gopxe
+ADD . /go/src/github.com/ppetko/gopxe
+WORKDIR /go/src/github.com/ppetko/gopxe
+RUN go test ./...
+RUN go build -o main .
 
+FROM centos:7.5.1804
+RUN yum install -y tftp tftp-server* xinetd* dhcp* epel-release syslinux  && yum clean all 
 EXPOSE 67 67/udp 69/udp 9090 9090/udp
-
-ADD ./conf/dhcpd_template /etc/dhcp/dhcpd.conf
-ADD ./conf/tftp /etc/xinetd.d/tftp
-ADD ./pxe_conf /var/lib/tftpboot
-ADD ./pxe/pxe_api /
-ADD ./run_pxe.sh /
-
-HEALTHCHECK --interval=4m --timeout=3s CMD curl --fail http://localhost:9090/status || exit 1
-
-CMD ["/run_pxe.sh"]
+RUN mkdir /var/lib/tftpboot/pxelinux.cfg /opt/localrepo
+RUN cp -r /usr/share/syslinux/pxelinux.0 /var/lib/tftpboot
+ADD ./pxebootImages /var/lib/tftpboot
+RUN mkdir -p /gopxe/public ; mkdir /gopxe/ksTempl
+WORKDIR /gopxe
+COPY --from=builder /go/src/github.com/ppetko/gopxe/main /gopxe/
+ADD ./public /gopxe/public
+ADD ./ksTempl /gopxe/ksTempl
+ADD ./start-gopxe.sh /gopxe/
+HEALTHCHECK --interval=4m --timeout=60s CMD curl --fail http://localhost:9090/health || exit 1
+ENTRYPOINT ["/gopxe/start-gopxe.sh"]

Gopkg.lock

@@ -0,0 +1,38 @@
+# Gopkg.toml example
+#
+# Refer to https://golang.github.io/dep/docs/Gopkg.toml.html
+# for detailed Gopkg.toml documentation.
+#
+# required = ["github.com/user/thing/cmd/thing"]
+# ignored = ["github.com/user/project/pkgX", "bitbucket.org/user/project/pkgA/pkgY"]
+#
+# [[constraint]]
+#   name = "github.com/user/project"
+#   version = "1.0.0"
+#
+# [[constraint]]
+#   name = "github.com/user/project2"
+#   branch = "dev"
+#   source = "github.com/myfork/project2"
+#
+# [[override]]
+#   name = "github.com/x/y"
+#   version = "2.4.0"
+#
+# [prune]
+#   non-go = false
+#   go-tests = true
+#   unused-packages = true
+
+
+[[constraint]]
+  name = "github.com/coreos/bbolt"
+  version = "1.3.0"
+
+[[constraint]]
+  name = "github.com/gorilla/mux"
+  version = "1.6.2"
+
+[prune]
+  go-tests = true
+  unused-packages = true

Gopkg.toml

@@ -0,0 +1,30 @@
+# Expected Behavior
+
+Please describe the behavior you are expecting
+
+# Current Behavior
+
+What is the current behavior?
+
+# Failure Information (for bugs)
+
+Please help provide information about the failure if this is a bug. If it is not a bug, please remove the rest of this template.
+
+## Steps to Reproduce
+
+Please provide detailed steps for reproducing the issue.
+
+1. step 1
+2. step 2
+3. ...
+
+## Context
+
+Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.
+
+* Operating System:
+* Go version:
+
+## Failure Logs
+
+Please include any relevant log snippets or files here.

ISSUE_TEMPLATE.md

@@ -0,0 +1,40 @@
+PROJECT_NAME := "gopxe"
+PKG := "github.com/ppetko/$(PROJECT_NAME)"
+PKG_LIST := $(shell go list ${PKG}/... | grep -v /vendor/)
+GO_FILES := $(shell find . -name '*.go' | grep -v /vendor/ | grep -v _test.go)
+
+.PHONY: all dep build docker-build clean test coverage lint
+
+all: build
+
+lint: ## Lint the files
+	@golint -set_exit_status ${PKG_LIST}
+
+test: ## Run unittests
+	@go test -v ./...
+
+race: dep ## Run data race detector
+	@go test -race -short ${PKG_LIST}
+
+cover: ## Generate global code coverage report in HTML
+	./tools/coverage.sh html;
+
+dep: ## Get the dependencies
+	@go get -v -d ./...
+
+build: dep ## Build the binary file
+	@go build -v
+
+docker-build: ## Build docker container from Dockerfile
+	@docker build -t $(PROJECT_NAME) -f Dockerfile . 
+
+docker-test: ## Run all go tests in Docker
+	@docker run --rm -ti $(PROJECT_NAME) go tests -v ./... 
+
+clean: ## Remove previous build
+	@rm -f $(PROJECT_NAME)
+	@rm -f coverage.html
+
+help: ## Display this help screen
+	@grep -h -E '^[a-zA-Z_-]+:.*?## .*$$' $(MAKEFILE_LIST) | awk 'BEGIN {FS = ":.*?## "}; {printf "\033[36m%-30s\033[0m %s\n", $$1, $$2}'
+

Makefile

@@ -0,0 +1,21 @@
+# Description - What does this PR do?
+
+Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
+
+## Types of changes
+
+What types of changes does your code introduce to Appium?
+_Put an `x` in the boxes that apply_
+
+- [ ] Bugfix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+
+Before submitting your PR, please review the following checklist:
+
+- [ ] I have signed the [**GoPXE CLA**](http://add-this-later).
+- [ ] I have read the [**CONTRIBUTING guide**](github.com/ppetko/gopxe/CONTRIBUTING.md).
+- [ ] **CONSIDER** adding a unit test if your PR resolves an issue.
+- [ ] **DO** keep pull requests small so they can be easily reviewed.
+- [ ] **DO** make sure unit tests pass.
+- [ ] **DO** make sure its documented.
+- [ ] **AVOID** breaking the continuous integration build.