Initial commit

.gitattributes

@@ -0,0 +1 @@
+internal/proxy/bin/bin_assets.go filter=lfs diff=lfs merge=lfs -text

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,22 @@
+## Prerequisites
+
+* [ ] I am running the latest version. (`up upgrade`)
+* [ ] I searched to see if the issue already exists.
+* [ ] I inspected the verbose debug output with the `-v, --verbose` flag.
+* [ ] Are you an Up Pro subscriber?
+
+## Description
+
+Describe the bug or feature.
+
+## Steps to Reproduce
+
+Describe the steps required to reproduce the issue if applicable.
+
+## Love Up?
+
+Please consider signing up for Up Pro (https://up.docs.apex.sh/#guides.subscribing_to_up_pro) or donating via https://opencollective.com/apex-up/donate.
+
+## Slack
+
+Join us on Slack https://chat.apex.sh/

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,14 @@
+Open an issue and discuss changes before spending time on them, unless the change is trivial or an issue already exists.
+
+Use "VERB some thing here. Closes #n" to close the relevant issue, where VERB is one of:
+
+  - add
+  - remove
+  - change
+  - refactor
+
+If the change is documentation related prefix with "docs: ", as these are filtered from the changelog.
+
+  docs: add ~/.aws/config
+
+Run `dep ensure` if you introduce any new `import`'s so they're included in the ./vendor dir.

.gitignore

@@ -0,0 +1,14 @@
+.envrc
+node_modules/
+.shards/
+lib
+vendor/
+testing
+up-proxy
+!cmd/up-proxy
+dist
+.idea
+.vscode
+.DS_Store
+internal/proxy/bin/bin_assets.go
+internal/shim/bindata.go

.goreleaser.yml

@@ -0,0 +1,19 @@
+build:
+  main: cmd/up/main.go
+  binary: up
+  goos:
+    - darwin
+    - linux
+    - windows
+    - freebsd
+    - netbsd
+    - openbsd
+  goarch:
+    - amd64
+    - 386
+changelog:
+  sort: asc
+  filters:
+    exclude:
+      - '^docs:'
+      - '^refactor'

.travis.yml

@@ -0,0 +1,10 @@
+language: go
+go:
+  - 1.9
+
+script:
+  - curl -sL https://github.com/golang/dep/releases/download/v0.4.1/dep-linux-amd64 > dep
+  - chmod +x ./dep
+  - ./dep ensure
+  - make install.deps
+  - make test.ci

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant 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 at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems 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,84 @@
+# Contributing
+
+Before contributing to Up you'll need a few things:
+
+- Install [Golang 1.9](https://golang.org/dl/) for that Go thing if you don't have it
+- Install [golang/dep](https://github.com/golang/dep) for dependency management
+
+The following are optional:
+
+- Install [pointlander/peg](https://github.com/pointlander/peg) if you're working on the log grammar
+- Install [jteeuwen/go-bindata](https://github.com/jteeuwen/go-bindata) if you need to bake `up-proxy` into `up`
+- Or run `make install.deps` to grab these tools
+
+## Setup
+
+Grab Up:
+
+```
+$ go get github.com/apex/up
+```
+
+Change into the project:
+
+```
+$ cd $GOPATH/src/github.com/apex/up
+```
+
+Grab the dependencies:
+
+```
+$ dep ensure
+```
+
+Grab the dev dependencies:
+
+```
+make install.deps
+```
+
+## Testing
+
+```
+$ make test
+```
+
+## Layout
+
+Although Up is not provided as a library it is structured as if it was, for organizational purposes. The project layout is loosely:
+
+- *.go – Primary API
+- [reporter](reporter) – Event based CLI reporting
+- [platform](platform) – Platform specifics (AWS Lambda, Azure, Google, etc)
+- [internal](internal) – Internal utilities and lower level tooling
+- [http](http) – HTTP middleware for up-proxy
+- [handler](handler) – HTTP middleware aggregate, effectively the entire proxy
+- [docs](docs) – Documentation used to generate the static site
+- [config](config) – Configuration structures and validation for `up.json`
+- [cmd](cmd) – Commands, where `up` is the CLI and `up-proxy` is serving requests in production
+
+Note that this is just a first past, and the code / layout will be refactored. View [Godoc](http://godoc.org/github.com/apex/up) for more details of the internals.
+
+## Proxy
+
+One oddity is that the `up-proxy` is baked into `up`. Yes there's a binary within the binary :) – this is so `up` can inject the proxy before deploying your function to Lambda.
+
+The proxy accepts AWS Lambda events from API Gateway, translates them to HTTP, and sends a request to your application, then translates it back to an event that API Gateway understands.
+
+Reverse proxy features such as URL rewriting, gzip compression, script injection, error pages and others are also provided in `up-proxy`.
+
+## Roadmap
+
+Up uses GitHub issue tracking and milestones for its loose roadmap. I highly recommend installing Zenhub (https://www.zenhub.com/) as well, however I primarily organize by milestones and labels for now.
+
+## Releases
+
+Notes for myself:
+
+- Run `make build` if necessary to re-build the proxy
+- Run `git changelog`
+- Run `git release`
+- Run `make release`
+- Re-build documentation
+- Notes about any backwards compat issues, migration, IAM policy changes
+- Adjust schemastore JSON schema if necessary