-
Notifications
You must be signed in to change notification settings - Fork 2
Update project #93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
tschaffter
wants to merge
15
commits into
main
Choose a base branch
from
update-project
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update project #93
Changes from 11 commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
4803c8a
Start updating docker-compose.yml
tschaffter 7e186b7
Update dependabot config
tschaffter 8383124
Update CI workflow
tschaffter 6664ed0
Fix hadlint path to Dockerfile
tschaffter 8d8ad72
Improve Dockerfile
tschaffter ae92822
Improve Dockerfile
tschaffter 7d17c19
Ignore apk package version warning
tschaffter f2faa70
Ignore apk package version warning
tschaffter 3320453
Comment out validation of docker-compose.yml
tschaffter fa0c861
Merge branch 'main' into update-project
tschaffter 90c8bc3
Add in -example
thomasyu888 b313cc3
Merge branch 'main' into update-project
boyleconnor 2aa21e8
Merge branch 'main' into update-project
boyleconnor 7b448bf
Remove Consecutive RUNs in Dockerfile
boyleconnor 6fa7b3e
'physical-address' -> 'location'
boyleconnor File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
File renamed without changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,135 @@ | ||
| # Contributing | ||
|
|
||
| A big welcome and thank you for considering contributing to this project. | ||
|
|
||
| This project is a community effort and lives off your contributions, be it in | ||
| the form of bug reports, feature requests, discussions, or fixes and other | ||
| code changes. | ||
|
|
||
| Reading and following these guidelines will help us make the contribution | ||
| process easy and effective for everyone involved. It also communicates that you | ||
| agree to respect the time of the developers managing and developing these open | ||
| source projects. In return, we will reciprocate that respect by addressing your | ||
| issue, assessing changes, and helping you finalize your pull requests. | ||
|
|
||
| ## Quicklinks | ||
|
|
||
| - [Code of Conduct](#code-of-conduct) | ||
| - [Getting Started](#getting-started) | ||
| - [Issues](#issues) | ||
| - [Pull Requests](#pull-requests) | ||
| - [Setup Development Environment](#setup-development-environment) | ||
| - [Testing](#testing) | ||
| - [Release Procedure](#release-procedure) | ||
| - [Getting Help](#getting-help) | ||
|
|
||
| ## Code of Conduct | ||
|
|
||
| We take our open source community seriously and hold ourselves and other | ||
| contributors to high standards of communication. By participating and | ||
| contributing to this project, you agree to uphold our [Code of Conduct]. | ||
|
|
||
| ## Getting Started | ||
|
|
||
| Contributions are made to this repo via Issues and Pull Requests (PRs). A few | ||
| general guidelines that cover both: | ||
|
|
||
| - Search for existing Issues and PRs before creating your own. | ||
| - We work hard to makes sure issues are handled in a timely manner but, | ||
| depending on the impact, it could take a while to investigate the root cause. | ||
| A friendly ping in the comment thread to the submitter or a contributor can | ||
| help draw attention if your issue is blocking. | ||
|
|
||
| ### Issues | ||
|
|
||
| Issues should be used to report problems with this project, request a new | ||
| feature, or to discuss potential changes before a PR is created. When you | ||
| create a new Issue, a template will be loaded that will guide you through | ||
| collecting and providing the information we need to investigate. | ||
|
|
||
| If you find an Issue that addresses the problem you're having, please add your | ||
| own reproduction information to the existing issue rather than creating a new | ||
| one. Adding a [reaction] can also help be indicating to our maintainers that a | ||
| particular problem is affecting more than just the reporter. | ||
|
|
||
| ### Pull Requests | ||
|
|
||
| PRs to our repositories are always welcome and can be a quick way to get your | ||
| fix or improvement slated for the next release. In general, PRs should: | ||
|
|
||
| - Only fix/add the functionality in question **OR** address wide-spread | ||
| whitespace/style issues, not both. | ||
| - Add unit or integration tests for fixed or changed functionality | ||
| (if a test suite already exists). | ||
| - Address a single concern in the least number of changed lines as possible. | ||
| - Include documentation in the repo or on our [docs site]. | ||
| - Be accompanied by a complete Pull Request template (loaded automatically | ||
| when a PR is created). | ||
|
|
||
| For changes that address core functionality or would require breaking changes | ||
| (e.g. a major release), it's best to open an Issue to discuss your proposal | ||
| first. This is not required but can save time creating and reviewing changes. | ||
|
|
||
| In general, we follow the [Forking Workflow]: | ||
|
|
||
| 1. Fork the repository to your own Github account | ||
| 2. Clone the project to your machine | ||
| 3. Create a branch locally with a succinct but descriptive name | ||
| 4. Commit changes to the branch | ||
| 5. Following any formatting and testing guidelines specific to this repo | ||
| 6. Push changes to your fork | ||
| 7. Open a PR in our repository and follow the PR template so that we can | ||
| efficiently review the changes. | ||
|
|
||
| We recommend that you add this repository as an [upstream remote] to your local | ||
| git repository so that you can fetch the latest updates. | ||
|
|
||
| On your local machine make sure you have the latest version of the `develop` | ||
| branch from this upstream repository: | ||
|
|
||
| git checkout develop | ||
| git pull upstream develop | ||
|
|
||
| ### Setup Development Environment | ||
|
|
||
| This project relies on Node tools and project-specific commands listed in the | ||
| file [package.json] to streamline the development and testing of this project. | ||
| The command below will install the required development tools. | ||
|
|
||
| npm ci | ||
|
|
||
| ### Testing | ||
|
|
||
| Please add tests for new code. These might include unit tests (to test specific | ||
| functionality of code that was added to support fixing the bug or feature), | ||
| integration tests (to test that the feature is usable - e.g., it should have | ||
| complete the expected behavior as reported in the feature request or bug | ||
| report), or both. | ||
|
|
||
| Before submitting a PR, please check that the content of the branch that you | ||
| plan to submit passes with the tests defined for this project: | ||
|
|
||
| npm run lint | ||
| npm run test | ||
|
|
||
| ## Release Procedure | ||
|
|
||
| Maintainers are required to follow the procedure below when creating a new | ||
| release. | ||
|
|
||
| TBA | ||
|
|
||
| ## Getting Help | ||
|
|
||
| Join us on the [NLP Sandbox Discord server] and post your question to the | ||
| channel that best matches the topic of your request. | ||
|
|
||
| <!-- Links --> | ||
|
|
||
| [Code of Conduct]: CODE_OF_CONDUCT.md | ||
| [upstream remote]: https://help.github.com/en/articles/configuring-a-remote-for-a-fork | ||
| [reaction]: https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/ | ||
| [docs site]: https://nlpsandbox.io | ||
| [Forking Workflow]: https://www.atlassian.com/git/tutorials/comparing-workflows/forking-workflow | ||
| [package.json]: ../package.json | ||
| [NLP Sandbox Discord server]: https://nlpsandbox.io/discord |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| name: 'Lock Threads' | ||
| name: Lock threads | ||
|
|
||
| on: | ||
| schedule: | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,13 +1,17 @@ | ||
| # pull official node base image | ||
| FROM node:16.2.0-alpine3.12 as build | ||
|
|
||
| WORKDIR /app | ||
| ENV PATH /app/node_modules/.bin:$PATH | ||
| COPY package.json ./ | ||
| COPY package-lock.json ./ | ||
| RUN npm ci --silent | ||
| RUN npm install [email protected] -g --silent | ||
|
|
||
| # TODO Either copy file individually or use this line + .gitignore | ||
| COPY . ./ | ||
| RUN npm run build | ||
|
|
||
| RUN npm ci --silent \ | ||
| && npm install [email protected] -g --silent \ | ||
| && npm run build | ||
|
|
||
| # production environment | ||
| FROM nginx:1.21.0-alpine | ||
|
|
@@ -19,8 +23,9 @@ WORKDIR /usr/share/nginx/html | |
| COPY env.sh . | ||
| COPY env_vars . | ||
|
|
||
| RUN apk add --no-cache bash | ||
| RUN chmod +x env.sh | ||
| # hadolint ignore=DL3018 | ||
| RUN apk add --no-cache bash \ | ||
| && chmod +x env.sh | ||
|
|
||
| EXPOSE 80 | ||
| CMD ["/bin/bash", "-c", "/usr/share/nginx/html/env.sh && nginx -g \"daemon off;\""] | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As Thomas and I just discussed, this should probably follow the example of one of the example annotators, e.g. https://github.com/nlpsandbox/person-name-annotator-example/blob/8423e95c924d1232f68560127815dacfd3a4ccd0/server/Dockerfile#L19
("
.gitignore" should be ".dockerignore")