Giter Club home page Giter Club logo

nest-permissions-seed's Introduction

nest-permissions-seed

Greenkeeper badge Build Status dependencies-release

A simple application demonstrating the basic usage of permissions with NestJS.

Current repository no longer supported, all changes are in the new repository https://github.com/rucken/core-nestjs

Usage

  • clone or fork repository git clone --recursive https://github.com/EndyKaufman/nest-permissions-seed.git
  • make sure you have node.js installed version 6+
  • make sure you have NPM installed version 3+
  • run npm install to install project dependencies
  • copy _env to .env and set environments for use
  • run npm run schema:sync to create all tables in database
  • run npm run migrate:run to run all migrations
  • run npm run start:prod to fire up prod server (npm run start:watch - dev server)
  • Open browser to http://localhost:3000

Demo application on Heroku

Users

Swagger

License

MIT

nest-permissions-seed's People

Contributors

endykaufman avatar greenkeeper[bot] avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

nest-permissions-seed's Issues

⚠️ Greenkeeper is no longer available for new installations

Hello!

Greenkeeper is no longer available for new installations.

The service will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020. Find out more at greenkeeper.io.

If this is your only Greenkeeper installation, you can just sign up for Snyk directly, it’s free for Open Source and even has free features for private projects as well.

Nevertheless, thanks for your interest in Greenkeeper! We’re sure your repositories will find a good home at Snyk ☀️🏡💜

All the best from everyone at Greenkeeper! 👋🤖🌴

An in-range update of tweetnacl-util is breaking the build 🚨

The dependency tweetnacl-util was updated from 0.15.0 to 0.15.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

tweetnacl-util is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 8 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml
  • The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖


FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of swagger-test-templates is breaking the build 🚨

The dependency swagger-test-templates was updated from 1.5.0 to 1.5.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

swagger-test-templates is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 2 commits ahead by 2, behind by 1.

  • 3851930 1.5.1
  • 31f18d4 Ensure "descriptions" are correctly formatted as JavaScript strings (#174)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of jsonwebtoken is breaking the build 🚨

The dependency jsonwebtoken was updated from 8.3.0 to 8.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

jsonwebtoken is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 27 commits.

  • 86334aa 8.4.0
  • e7938f0 Add verify option for nonce validation (#540)
  • 0268813 devDeps: [email protected] (#539)
  • dc89a64 Edited the README.md to make certain parts of the document for the api easier to read, emphasizing the examples. (#548)
  • 8864542 Refactor tests related to kid and keyid (#545)
  • 0906a3f Refactor tests related to iss and issuer (#543)
  • 1956c40 Update README.md (#538)
  • 7f9604a Fixed error message when empty string passed as expiresIn or notBefore option (#531)
  • cfd1079 Updating Node version in Engines spec in package.json (#528)
  • 1c8ff5a Implement async/sync tests for the aud claim (#535)
  • 88bc965 Implement async/sync tests for nbf claim (#537)
  • 9ae3f20 Implement async/sync tests for exp claim (#536)
  • 342b07b Implement async/sync tests for sub claim (#534)
  • 29cd654 Document NotBeforeError (#529)
  • 683d8a9 Create and implement async/sync test helpers (#523)

There are 27 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

An in-range update of reflect-metadata is breaking the build 🚨

The dependency reflect-metadata was updated from 0.1.12 to 0.1.13.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

reflect-metadata is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 3 commits.

  • aacaeb1 0.1.13
  • 5b98fe1 Do not generate source maps when publishing
  • c2dbe1d Add test to verify does not overwrite existing implementation

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

About error ocurred

Good morning my friends

About error ocurred

I'm testing this project and the following error is being returned

$ npm run schema:sync
Debugger attached.

> [email protected] schema:sync /workspace/EndyKaufman_nest-permissions-seed
> ts-node ./node_modules/typeorm/cli.js schema:sync

Debugger attached.
Debugger attached.
Error during schema synchronization:
Error [DriverPackageNotInstalledError]: SQLite package has not been found installed. Try to install it: npm install sqlite3 --save
    at new DriverPackageNotInstalledError (/workspace/EndyKaufman_nest-permissions-seed/src/error/DriverPackageNotInstalledError.ts:8:9)
    at SqliteDriver.loadDependencies (/workspace/EndyKaufman_nest-permissions-seed/src/driver/sqlite/SqliteDriver.ts:112:19)
    at new SqliteDriver (/workspace/EndyKaufman_nest-permissions-seed/src/driver/sqlite/SqliteDriver.ts:46:14)
    at DriverFactory.create (/workspace/EndyKaufman_nest-permissions-seed/src/driver/DriverFactory.ts:32:24)
    at new Connection (/workspace/EndyKaufman_nest-permissions-seed/src/connection/Connection.ts:115:43)
    at ConnectionManager.create (/workspace/EndyKaufman_nest-permissions-seed/src/connection/ConnectionManager.ts:64:28)
    at Object.<anonymous> (/workspace/EndyKaufman_nest-permissions-seed/src/index.ts:186:35)
    at step (/workspace/EndyKaufman_nest-permissions-seed/node_modules/typeorm/index.js:32:23)
    at Object.next (/workspace/EndyKaufman_nest-permissions-seed/node_modules/typeorm/index.js:13:53)
    at /workspace/EndyKaufman_nest-permissions-seed/node_modules/typeorm/index.js:7:71
Waiting for the debugger to disconnect...
Waiting for the debugger to disconnect...

Thanks in advance to everyone who can contribute.

An in-range update of typeorm is breaking the build 🚨

The dependency typeorm was updated from 0.2.7 to 0.2.8.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

typeorm is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of nodemon is breaking the build 🚨

The devDependency nodemon was updated from 1.18.4 to 1.18.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

nodemon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v1.18.5

1.18.5 (2018-10-26)

Bug Fixes

  • nodemon installation for node 10.x and beyond (#1441) (3afa52c)
Commits

The new version differs by 1 commits.

  • 3afa52c fix: nodemon installation for node 10.x and beyond (#1441)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.