https://github.com/seamapi/fake-seam-connect
Fake for Seam Connect.
https://github.com/seamapi/fake-seam-connect
Last synced: 5 months ago
JSON representation
Fake for Seam Connect.
- Host: GitHub
- URL: https://github.com/seamapi/fake-seam-connect
- Owner: seamapi
- License: mit
- Created: 2023-04-14T16:02:43.000Z (about 2 years ago)
- Default Branch: main
- Last Pushed: 2025-01-21T18:37:40.000Z (5 months ago)
- Last Synced: 2025-01-28T03:13:07.014Z (5 months ago)
- Language: TypeScript
- Homepage: https://fake-seam-connect.seam.vc
- Size: 1.85 MB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 8
-
Metadata Files:
- Readme: README.md
- License: LICENSE.txt
- Codeowners: .github/CODEOWNERS
Awesome Lists containing this project
README
# Fake Seam Connect
[](https://www.npmjs.com/package/@seamapi/fake-seam-connect)
[](https://github.com/seamapi/fake-seam-connect/actions/workflows/check.yml)
Fake for Seam Connect. Simulate the behavior of Seam Connect in an easy-to-use typescript module.
## Description
This module allows you to spin up an in-memory server
for Seam Connect.
## Installation
Add this as a dependency to your project using [npm] with
```
$ npm install @seamapi/fake-seam-connect
```
[npm]: https://www.npmjs.com/
## Usage
### From Docker
The application is distributed as a [Docker container].
Start the server inside a container with
```
$ docker run --init --read-only --publish 8080:8080 ghcr.io/seamapi/fake-seam-connect
```
Start a pre-seeded instance with
```
$ docker run --init --read-only --publish 8080:8080 ghcr.io/seamapi/fake-seam-connect --seed
```
[Docker container]: https://github.com/seamapi/fake-seam-connect/pkgs/container/fake-seam-connect
### From npx
The server is included in the published [npm package] and may be run using npx with
```
$ npx @seamapi/fake-seam-connect
```
Start a pre-seeded instance with
```
$ npx @seamapi/fake-seam-connect --seed
```
[npm package]: https://www.npmjs.com/package/@makenew/nodets-server
## Development and Testing
### Quickstart
```
$ git clone https://github.com/seamapi/fake-seam-connect.git
$ cd fake-seam-connect
$ nvm install
$ npm install
$ npm run test:watch
```
Primary development tasks are defined under `scripts` in `package.json`
and available via `npm run`.
View them with
```
$ npm run
```
### Source code
The [source code] is hosted on GitHub.
Clone the project with
```
$ git clone [email protected]:seamapi/fake-seam-connect.git
```
[source code]: https://github.com/seamapi/fake-seam-connect
### Requirements
You will need [Node.js] with [npm] and a [Node.js debugging] client.
Be sure that all commands run under the correct Node version, e.g.,
if using [nvm], install the correct version with
```
$ nvm install
```
Set the active version for each shell session with
```
$ nvm use
```
Install the development dependencies with
```
$ npm install
```
[Node.js]: https://nodejs.org/
[Node.js debugging]: https://nodejs.org/en/docs/guides/debugging-getting-started/
[npm]: https://www.npmjs.com/
[nvm]: https://github.com/creationix/nvm
### Publishing
#### Automatic
New versions are released automatically with [semantic-release]
as long as commits follow the [Angular Commit Message Conventions].
[Angular Commit Message Conventions]: https://semantic-release.gitbook.io/semantic-release/#commit-message-format
[semantic-release]: https://semantic-release.gitbook.io/
#### Manual
Publish a new version by triggering a [version workflow_dispatch on GitHub Actions].
The `version` input will be passed as the first argument to [npm-version].
This may be done on the web or using the [GitHub CLI] with
```
$ gh workflow run version.yml --raw-field version=
```
[GitHub CLI]: https://cli.github.com/
[npm-version]: https://docs.npmjs.com/cli/version
[version workflow_dispatch on GitHub Actions]: https://github.com/seamapi/fake-seam-connect/actions?query=workflow%3Aversion
## GitHub Actions
_GitHub Actions should already be configured: this section is for reference only._
The following repository secrets must be set on [GitHub Actions]:
- `NPM_TOKEN`: npm token for installing and publishing packages.
- `GH_USER`: The GitHub user's username to pull and push containers.
- `GH_TOKEN`: A personal access token for the user
- `GH_TOKEN`: A personal access token for the bot user with
`packages:write` and `contents:write` permission,
and permission to pull and push containers.
- `GIT_USER_NAME`: The GitHub bot user's real name.
- `GIT_USER_EMAIL`: The GitHub bot user's email.
- `GPG_PRIVATE_KEY`: The GitHub bot user's [GPG private key].
- `GPG_PASSPHRASE`: The GitHub bot user's GPG passphrase.
[GitHub Actions]: https://github.com/features/actions
[GPG private key]: https://github.com/marketplace/actions/import-gpg#prerequisites
## Contributing
> If using squash merge, edit and ensure the commit message follows the [Angular Commit Message Conventions] specification.
> Otherwise, each individual commit must follow the [Angular Commit Message Conventions] specification.
1. Create your feature branch (`git checkout -b my-new-feature`).
2. Make changes.
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 draft pull request.
6. Ensure all checks pass.
7. Mark your pull request ready for review.
8. Wait for the required approval from the code owners.
9. Merge when ready.
[Angular Commit Message Conventions]: https://semantic-release.gitbook.io/semantic-release/#commit-message-format
## License
This npm package is licensed under the MIT license.
## Warranty
This software is provided by the copyright holders and contributors "as is" and
any express or implied warranties, including, but not limited to, the implied
warranties of merchantability and fitness for a particular purpose are
disclaimed. In no event shall the copyright holder or contributors be liable for
any direct, indirect, incidental, special, exemplary, or consequential damages
(including, but not limited to, procurement of substitute goods or services;
loss of use, data, or profits; or business interruption) however caused and on
any theory of liability, whether in contract, strict liability, or tort
(including negligence or otherwise) arising in any way out of the use of this
software, even if advised of the possibility of such damage.