diff --git a/.cz-config.js b/.cz-config.js
new file mode 100644
index 0000000000000000000000000000000000000000..15dde7e748b74e4147f21fa9f0532b9b93a42e3e
--- /dev/null
+++ b/.cz-config.js
@@ -0,0 +1,51 @@
+'use strict';
+
+module.exports = {
+
+ types: [
+ {value: 'feat', name: 'feat: A new feature'},
+ {value: 'fix', name: 'fix: A bug fix'},
+ {value: 'docs', name: 'docs: Documentation only changes'},
+ {value: 'style', name: 'style: Changes that do not affect the meaning of the code\n (white-space, formatting, etc)'},
+ {value: 'refactor', name: 'refactor: A code change that neither fixes a bug nor adds a feature'},
+ {value: 'perf', name: 'perf: A code change that improves performance'},
+ {value: 'test', name: 'test: Adding missing tests or correcting existing tests'},
+ {value: 'build', name: 'build: Changes that affect the build system or external dependencies (example scopes: maven, gradle, npm, gulp)'},
+ {value: 'ci', name: 'ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)'},
+ {value: 'chore', name: 'chore: Other changes that dont modify src or test files'},
+ {value: 'revert', name: 'revert: Reverts a previous commit'}
+ ],
+
+ scopes: [
+ {name: 'jni'},
+ {name: 'internal'},
+ {name: 'swing'},
+ {name: 'opencl'}
+ ],
+
+ scopeOverrides: {
+ build: [
+ {name: 'dependencies'},
+ {name: 'versioning'},
+ {name: 'release'},
+ {name: 'build plugin'}
+ ],
+ ci: [
+ {name: 'travis'}
+ ],
+ chore: [
+ {name: 'commitizen'},
+ {name: 'editorconfig'},
+ {name: 'git'}
+ ],
+ docs: [
+ {name: 'javadocs'},
+ {name: 'repo'},
+ {name: 'maven'}
+ ]
+ },
+
+ allowCustomScopes: true,
+ allowBreakingChanges: ['feat', 'fix', 'docs', 'style', 'refactor', 'perf', 'test', 'build', 'ci', 'chore', 'revert']
+
+};
diff --git a/.cz.json b/.cz.json
new file mode 100644
index 0000000000000000000000000000000000000000..d4856e0f01c0fd7a73d9905a6c4e1d4c440464d6
--- /dev/null
+++ b/.cz.json
@@ -0,0 +1 @@
+{ "path": "cz-customizable" }
diff --git a/.editorconfig b/.editorconfig
new file mode 100644
index 0000000000000000000000000000000000000000..27f6865af138bc89bb7e578d13f606b2611d0e15
--- /dev/null
+++ b/.editorconfig
@@ -0,0 +1,14 @@
+# top-most EditorConfig file
+root = true
+
+[*]
+#unix style line ending
+end_of_line = lf
+#newline at end of file
+insert_final_newline = true
+#charset UTF-8
+charset = utf-8
+#indent using spaces
+indent_style = space
+#4 spaces per indent
+indent_size = 4
diff --git a/.gitattributes b/.gitattributes
new file mode 100644
index 0000000000000000000000000000000000000000..456e49e990094033c42c86cedc1801edd2d3d159
--- /dev/null
+++ b/.gitattributes
@@ -0,0 +1,4 @@
+* eol=lf
+*.bat eol=crlf
+*.sh eol=lf
+.git* export-ignore
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
new file mode 100644
index 0000000000000000000000000000000000000000..b297fc63562e6a51639d1966459fe2959e52ebe3
--- /dev/null
+++ b/.gitlab-ci.yml
@@ -0,0 +1,30 @@
+image: docker:stable
+
+services:
+ - docker:stable-dind
+
+variables:
+ REPOSITORY: "qotoorg/nginx-redirect"
+
+before_script:
+ - echo "${DOCKER_TOKEN}" | docker login --username "${DOCKER_USER}" --password-stdin
+
+stages:
+ - deploy
+
+nginx-redirect:
+ stage: deploy
+ script:
+ - if [ $CI_COMMIT_REF_NAME == "develop" ]; then
+ REV="git";
+ elif [ $CI_COMMIT_REF_NAME == "master" ]; then
+ REV="latest";
+ else
+ REV="$CI_COMMIT_REF_NAME";
+ fi
+ - docker build --network=host --pull -t "${REPOSITORY}:${REV}"
+ --no-cache
+ "."
+ - docker push "${REPOSITORY}"
+ tags:
+ - dind
diff --git a/ATTRIBUTIONS.md b/ATTRIBUTIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..a7ad9ca66fb6f4817327f62c73a350b97a25a296
--- /dev/null
+++ b/ATTRIBUTIONS.md
@@ -0,0 +1,8 @@
+This file contains all attributions and other notices that are required by law.
+
+## Copyright Notices
+
+The following are the list of all recognized copyright notices added by contributors to this project:
+
+Copyright (c) 2020, Syncleus, Inc. All rights reserved.
+Copyright (c) 2020, Jeffrey Phillips Freeman. All rights reserved.
diff --git a/CHANGELOG.md b/CHANGELOG.md
new file mode 100644
index 0000000000000000000000000000000000000000..2fbd6b619f55f6a486ba549da0d6799d41e71e63
--- /dev/null
+++ b/CHANGELOG.md
@@ -0,0 +1,5 @@
+# Aparapi Docker Image Changelog
+
+# 2.0.0-1
+
+* Initial version of the docker images for amdgpu and nvidia.
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
new file mode 100644
index 0000000000000000000000000000000000000000..1031d6749743c5b12fbfd188e050f0613220f612
--- /dev/null
+++ b/CODE_OF_CONDUCT.md
@@ -0,0 +1,72 @@
+# 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:
+
+* Unwelcomed sexual attention or advances.
+* Derogatory comments about a persons appearance, race, or sexual orientation.
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+
+## 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
+[aparapi@syncleus.com](mailto:aparapi@syncleus.com). 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/
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 0000000000000000000000000000000000000000..96afd74976d43cd3435bec33d2a597eb8da67916
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,102 @@
+# Contributing
+
+[](http://commitizen.github.io/cz-cli/)
+[](http://semver.org/spec/v2.0.0.html)
+[](https://gitter.im/Syncleus/aparapi?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
+
+When contributing to this repository, it is usually a good idea to 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. This could potentially save a lot of wasted hours.
+
+Please note we have a code of conduct, please follow it in all your interactions with the project.
+
+## Development
+
+### Commit Message Format
+
+Starting version 1.3.3 and later all commits on the Syncleus Aparapi repository follow the
+[Conventional Changelog standard](https://github.com/conventional-changelog/conventional-changelog-eslint/blob/master/convention.md).
+It is a very simple format so you can still write commit messages by hand. However it is
+highly recommended developers install [Commitizen](https://commitizen.github.io/cz-cli/),
+it extends the git command and will make writing commit messages a breeze. All the Aparapi
+repositories are configured with local Commitizen configuration scripts.
+
+Getting Commitizen installed is usually trivial, just install it via npm. You will also
+need to install the cz-customizable adapter which the Aparapi repository is configured
+to use.
+
+```bash
+
+npm install -g commitizen@2.8.6 cz-customizable@4.0.0
+```
+
+Below is an example of Commitizen in action. It replaces your usual `git commit` command
+with `git cz` instead. The new command takes all the same arguments however it leads you
+through an interactive process to generate the commit message.
+
+
+
+Commit messages are used to automatically generate our changelogs, and to ensure
+commits are searchable in a useful way. So please use the Commitizen tool and adhere to
+the commit message standard or else we cannot accept Pull Requests without editing
+them first.
+
+Below is an example of a properly formated commit message.
+
+```
+chore(Commitizen): Made repository Commitizen friendly.
+
+Added standard Commitizen configuration files to the repo along with all the custom rules.
+
+ISSUES CLOSED: #31
+```
+
+### Pull Request Process
+
+1. Ensure that install or build dependencies do not appear in any commits in your code branch.
+2. Ensure all commit messages follow the [Conventional Changelog](https://github.com/conventional-changelog/conventional-changelog-eslint/blob/master/convention.md)
+ standard explained earlier.
+3. Update the CONTRIBUTORS.md file to add your name to it if it isn't already there (one entry
+ per person).
+4. Adjust the project version to the new version that this Pull Request would represent. The
+ versioning scheme we use is [Semantic Versioning](http://semver.org/).
+5. Your pull request will either be approved or feedback will be given on what needs to be
+ fixed to get approval. We usually review and comment on Pull Requests within 48 hours.
+
+### Making a Release
+
+Only administrators with privilages to push to the Aparapi Maven Central account can deploy releases. If this isn't you
+then you can just skip this section.
+
+First ensure the package is prepared for the release process:
+
+* Make sure any references to the version number or branch name in the readme is at the pre-release branch/version
+ * The branch name in the build pipeline badge
+* Ensure the Aparapi version set in .gitlab.yml correctly points to the correct version for the branch.
+* Update the changelog file.
+* When possible make all changes that are universal to all versions in the develop branch and merge to the others.
+* Develop should always have the latest Aparapi version.
+
+Next lets take a few steps to do the actual release:
+
+1. Update everything listed above. Any functional changes should be made in develop branch when possible. Make sure develop
+ points to latest Aparapi version.
+2. Checkout the branch for the Aparapi version you are working on, for example `git checkout 2.0.0` or create
+ a new one if this is for a new version. For new branches make sure they are off of develop. Never add a `v` to the begining.
+3. Merge develop into the branch your working on, `git merge develop`.
+4. Update the README.md to ensure pipeline badge points to the correct branch.
+5. Update .gitlab-ci.yml to ensure the Aparapi version points to the correct version fpr new branches. If this is the latest version
+ of aparapi you should not need to update this, it should have been done in the first step.
+6. Push the branch to the server, make sure pipeline passes, such as `git push origin 2.0.0:2.0.0`.
+7. If pipeline passed, create a generic new branch, do not push it, as follows `git checkout -b release`.
+8. Update the pipeline badge in the readme to point to the to-be-released repository tag/version.
+9. Commit the current changes using a generic commit message such as `build(release): version 1.2.3 revision 4`. But do not push.
+10. Create a new tag for the current revision with the following command: `git tag -a 1.2.3-4 -m "Version 1.2.3 revision 4"`. Ensure
+ tags **always** have the aparapi version followed by revsion and never have the letter `v` prepending it.
+11. Push the newly created tag to the server: `git push origin 1.2.3-4:1.2.3-4`.
+12. Delete the release branch you created locally `git branch -D release`.
+13. If the Aparapi version deployed is the latest then merge develop branch into master, develop branch should already contain latest
+ Aparapi version from the first step.
+14. Ensure the pipeline badge in the readme points to the master branch
+15. Push master branch to server.
+16. Go to Github and GitLab and go to the releases. Update the description with the changelog for the version.
diff --git a/CONTRIBUTORS.md b/CONTRIBUTORS.md
new file mode 100644
index 0000000000000000000000000000000000000000..c8b074c25784e77da35c92741165d9720d9801c0
--- /dev/null
+++ b/CONTRIBUTORS.md
@@ -0,0 +1,7 @@
+# Contributors
+
+* Jeffrey Phillips Freeman <jeffrey.freeman@syncleus.com>
+
+# Details
+
+* Jeffrey Phillips Freeman - creator and maintainer of this docker image.
diff --git a/Dockerfile b/Dockerfile
index 8f9c64e0e3e9acbe6b5f9bb71e09063372718ebb..5b128ccfbd7be433163e71163baa54043a0d5507 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -1,8 +1,16 @@
FROM nginx:alpine
+LABEL maintainer "Jeffrey Phillips Freeman <the@jeffreyfreeman.me>"
+
ADD run.sh /run.sh
ADD default.conf /etc/nginx/conf.d/default.conf
RUN chmod +x /run.sh
CMD ["/run.sh"]
+
+ENV VIRTUAL_HOST
+ENV LETSENCRYPT_HOST
+ENV VIRTUAL_PORT 80
+ENV LETSENCRYPT_EMAIL jeffrey.freeman@qoto.org
+
diff --git a/LICENSE b/LICENSE
new file mode 100644
index 0000000000000000000000000000000000000000..e06d2081865a766a8668acc12878f98b27fc9ea0
--- /dev/null
+++ b/LICENSE
@@ -0,0 +1,202 @@
+Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "{}"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright {yyyy} {name of copyright owner}
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+
diff --git a/NOTICE b/NOTICE
new file mode 100644
index 0000000000000000000000000000000000000000..e32a61a84c7fcd4ca1aafda517599d57353419c8
--- /dev/null
+++ b/NOTICE
@@ -0,0 +1,13 @@
+Copyright (c) 2016 - 2018 Syncleus, Inc.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
diff --git a/README.md b/README.md
index 0bbed128b8b0946e76d881ff74591075b555c041..6a278e27768aa30fe39e636f29641fcd8e7459f6 100644
--- a/README.md
+++ b/README.md
@@ -2,10 +2,6 @@
A very simple container to redirect HTTP traffic to another server, based on `nginx`
-## Resources
-
-- [Docker Hub](https://hub.docker.com/r/schmunk42/nginx-redirect/)
-
## Configuration
### Environment variables
@@ -40,14 +36,17 @@ See also `docker-compose.yml` file.
With `docker-compose`
- docker-compose up -d
+````bash
+docker-compose up -d
+````
With `docker`
- docker run -e SERVER_REDIRECT=www.example.com -p 8888:80 schmunk42/nginx-redirect
- docker run -e SERVER_REDIRECT=www.example.com -e SERVER_REDIRECT_PATH=/landingpage -p 8888:80 schmunk42/nginx-redirect
- docker run -e SERVER_REDIRECT=www.example.com -e SERVER_REDIRECT_PATH=/landingpage -e SERVER_REDIRECT_SCHEME=https -p 8888:80 schmunk42/nginx-redirect
-
----
+```bash
+docker run -e SERVER_REDIRECT=www.example.com -p 8888:80 schmunk42/nginx-redirect
+docker run -e SERVER_REDIRECT=www.example.com -e SERVER_REDIRECT_PATH=/landingpage -p 8888:80 schmunk42/nginx-redirect
+docker run -e SERVER_REDIRECT=www.example.com -e SERVER_REDIRECT_PATH=/landingpage -e SERVER_REDIRECT_SCHEME=https -p 8888:80 schmunk42/nginx-redirect
+```
+## Resources
-Built by [dmstr](http://diemeisterei.de)
+This tool was adapted from the original you can get at [Github](https://github.com/schmunk42/docker-nginx-redirect)
diff --git a/docker-compose.yml b/docker-compose.yml
index 462f290fe1ab119f7e59eaabdb38472c3da3479b..5077eccdde5bf46d4203b5d8305a5bf02796a86a 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -1,5 +1,6 @@
-to:
- image: schmunk42/nginx-redirect
+nginx-redirect:
+ image: qoto/nginx-redirect
+ build: .
ports:
- "8888:80"
environment: