GithubHelp home page GithubHelp logo

webhintio / online-service Goto Github PK

View Code? Open in Web Editor NEW
92.0 23.0 16.0 7.46 MB

🔬 Online version of webhint

Home Page: https://webhint.io/scanner/

License: Apache License 2.0

JavaScript 4.00% Shell 3.96% TypeScript 88.39% CSS 1.49% HTML 2.16%

online-service's Introduction

online-service Build Status Greenkeeper badge FOSSA Status

Requirements

  • A MongoDB database or API compatible (Azure Cosmos DB)
  • Azure service bus
  • Kubernetes

Installation

git clone https://github.com/webhintio/online-service.git
cd online-service
npm install
npm run build

Configuration

You need to configure at least the following env variables in order to run the service:

  • database: The connection string for the database
  • queue: The connection string for Azure service bus
  • port: The port where the job manager will be listening

Quick start user guide

Run the Job manager

npm run online-service -- --microservice job-manager

Run the Config manager

npm run online-service -- --microservice config-manager --name new-config-name --file path/to/you/config-file.json --cache 120 --run 120

NOTE: use npm run online-service -- --help to get more information about what each argument means

Run the Worker service

npm run online-service -- --microservice worker

Run the Sync service

npm run online-service -- --microservice sync

Run everything at the same time (except the config manager)

npm run online-service -- --microservice all

NOTE: You need to set up the following environment variables before continue: NODE_ENV=production, database=YourConnectionStringToTheDatabase and queue=YourConnectionStringToServiceBus

Kubernetes

Local environment

If you want to run the online-service in you local machine, you just need to run:

kubectl apply -f kubernetes.yml

NOTE:

Kubernetes needs to be installed in your computer.

We are assuming that you are in the folder compose before running kubectl. If you are in another folder, replace the file with your path to the file kubernetes.yml.

Remember you need to replace the enviroment variables values in compose/kubernetes.yml with your own values before run kubectl.

Azure environment

First of all we need to deploy kubernetes services in Azure.

To do so, first you need to go to the folder deploy inside the folder scripts.

cd scripts/deploy

Make the file deploy.sh executable.

chmod +x deploy.sh

Run deploy.sh. If you don't want to pass the parameters, the script will ask you later for the information needed.

./deploy.sh -i <subscriptionName> -g <resourceGroupName> -l <resourceGroupLocation> -k <sshPublicKey> -r <containerRegistryName>"

The deployment script will create all the necessary to run the online scanner:

  1. An Azure kubernetes service.
  2. An Azure Service bus.
  3. A Virtual machine with linux to install nginx.
  4. If needed, a replicated mongodb.
  5. The peering between the linux VM and the database (the new one or an old one).

NOTE:

sshPublicKey is the path to the file containing the public ssh key.

Build images

To build all the images at the same time you need to run the script build-images.js.

To do so, first you need to go to the folder scripts.

cd scripts

Run build-images.js with the name of your repository and the image version as parameters.

node build-images.js --repository webhint --version 1

Upload the images to your Container Registry

To upload all the images at the same time you need to run the script update-images.js.

To do so, first you need to go to the folder scripts.

cd scripts

Run upload-images.js with the name of your repository and the image version as parameters.

node upload-images.js --repository webhint --version 1

NOTE: You need to be logged in into you Container Registry az acr login --name ContainerRegistryName before upload the images.

Update the configuration file

Before deploy, the configuration file needs to point to the right repository and to the current version of the images. You can do that manually or you can run the script update-config-file.js.

To do so, first you need to go to the folder scripts.

cd scripts

Run update-config-file.js with the name of your repository, the image version and the path to the configuration file as parameters.

node update-config-file.js --repository webhint --version 1 --kubernetes ../compose/kubernetes-azure.yml

NOTE:

The file path is optional, by default the value is ../compose/kubernetes-azure.yml

You also need the config from your cluster az aks get-credentials --resource-group ResourceGroupName --name ClusterName

Deploy

To deploy the online scanner in kubernetes you need to run the script deploy-kubernetes.js

To do so, first you need to go to the folder scripts.

cd scripts

Run deploy-kubernetes.js with the path to the configuration file as a parameter.

node deploy-kubernetes.js --kubernetes ../compose/kubernetes-azure.yml

NOTE:

The file path is optional, by default the value is ../compose/kubernetes-azure.yml

Build, upload, configure and deploy (all in one)

You can run all the previous steps with just one script using build-and-deploy.js

To do so, first you need to go to the folder scripts.

cd scripts

Run build-and-deploy.js with the name of your repository and the path to the configuration file as parameters.

node build-and-deploy.js --repository webhint --kubernetes ../compose/kubernetes-azure.yml

NOTE:

The version for the images will be auto calculated using your current images you have in your computer.

Deploy NGINX

To deploy NGINX, you will find a few files in scripts/deploy/nginx:

  • install-nginx.sh
  • configure-nginx.sh
  • nginx-step1.conf
  • nginx-step2.conf

Before start deploying NGINX, you need to copy these files to your NGINX machine:

Copy files into the machine where we want to deploy:

  1. Copy files:

    scp *.sh *.conf [email protected]:~
  2. Go into the machine:

    ssh -p your.port [email protected]
  3. Install NGINX and Certbot:

    sudo ./install-nginx.sh

NOTE: If you get an error GPG error, look for the instructions in install-nginx.sh.

  1. Configure NGINX

    sudo ./configure-nginx.sh -s <serverName> -j <jobsIpAndPort> -c <configIpAndPort>

NOTE:

jobsIPAndPort is the IP and port where the job-manager is deployed. configIpAndPort is the IP and port where the config-manager is deployed.

Configuring the scanner

After everything is deployed, the next step is to configure the scanner.

  1. Authorize an user to have access to the config panel

    Access the database the way you prefer and then create a user collection if it doesn't exist already and create an item with the property name set to the user (github user) you want to give access, manually.

    {
        "name": "githubusername"
    }
  2. Create the OAuth App in github.

    Go to github => Settings => Developer settings

    The Authorization callback URL will be something like: https://yourip/admin/auth/github/callback

  3. Add a configuration

    Once you access to the configuration panel (https://youip/admin) the next step is to add the configuration we want to use in the scanner.

    The scanner configuration is an array of hint configuration.

    To add the scanner configuration go to the admin panel => Configuration.

Code of Conduct

This project adheres to the JS Foundation's code of conduct.

By participating in this project you agree to abide by its terms.

License

The code is available under the Apache 2.0 license.

FOSSA Status

online-service's People

Contributors

alrra avatar antross avatar azure-pipelines[bot] avatar ckd avatar dependabot-preview[bot] avatar dependabot-support avatar dependabot[bot] avatar greenkeeper[bot] avatar molant avatar qczhou avatar sarvaje avatar utsavized 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

Watchers

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

online-service's Issues

An in-range update of typescript-eslint-parser is breaking the build 🚨

The devDependency typescript-eslint-parser was updated from 20.0.0 to 20.1.0.

🚨 View failing branch.

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

typescript-eslint-parser 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 v20.1.0
Commits

The new version differs by 6 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 🌴

An in-range update of @hint/configuration-web-recommended is breaking the build 🚨

The dependency @hint/configuration-web-recommended was updated from 1.1.1 to 1.2.0.

🚨 View failing branch.

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

@hint/configuration-web-recommended 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).

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 🌴

Better logging

Improve the logging information. Right now there are exceptions that we don't know why they are happening.
We could/should also send email notifications.

A more user-friendly version of the timeout error

Hi,

Users of the downloaded CLI can use an error message like this one:

Error executing script 'TIMEOUT'. Please try with another connector.

However, I expect users of the online version will likely confuse this error with the a problem on the webpage they were testing. Moreover, the online version doesn't allow to change said connector.

Example (below "axe" and "no-vulnerable-javascript-libraries"):
https://webhint.io/scanner/28f79593-cd29-427d-9af5-d7178932b212

May I suggest:

The outsourced service for this test didn't respond in the allotted time. Please try again later, or you could report an issue if this problem persists.

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

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.0.1 of proxyquire was just published.

Branch Build failing 🚨
Dependency proxyquire
Current Version 2.0.0
Type devDependency

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

proxyquire 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

Commits

The new version differs by 3 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 🌴

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

The dependency mongoose was updated from 5.2.14 to 5.2.15.

🚨 View failing branch.

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

mongoose 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 26 commits.

  • c4a01ec chore: release 5.2.15
  • 1ba6ca7 fix(model): allow calling Model.init() again after calling dropDatabase()
  • 4108366 test(model): repro #6967
  • 8a178ad docs: add selectPopulatedPaths option
  • 950d223 fix(populate): add selectPopulatedPaths option to opt out of auto-adding populate()-ed fields to select()
  • c0fb363 test(populate): repro #6546
  • 6dd98c8 style: fix lint
  • 8840ffd chore: peg chalk version
  • bdd7432 docs(webpack): make webpack docs use es2015 preset for correct libs and use acorn to test output is valid ES5
  • 25c305d docs(model): add blog post link and example to syncIndexes() docs
  • 2d928b4 style: fix lint
  • dcfb894 fix(populate): handle virtual justOne correctly if it isn't set
  • 0bff408 test(populate): repro #6988
  • a01b827 fix(populate): find connect justOne when double-populating underneath an array
  • b5841c2 test(populate): repro #6798

There are 26 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 🌴

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

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 🌴

Notify if a job is new

When an user request an url that it is already in the database and it has not expired yet.

An in-range update of azure-storage is breaking the build 🚨

The dependency azure-storage was updated from 2.10.1 to 2.10.2.

🚨 View failing branch.

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

azure-storage 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).

Release Notes for Storage Client Library 2.10.2

2018.10 Version 2.10.2

ALL

  • Upgrade xmlbuilder to 9.0.7 and extend to 3.0.2 to avoid vulnerabilities.
  • Removed deprecated Buffer constructor calls in favor of static methods Buffer.from and Buffer.alloc.
  • Added JSv10 link and docs.microsoft.com link.
  • Improved documents.

BLOB

  • Added typescript declarations to listBlobDirectoriesSegmented and listBlobDirectoriesSegmentedWithPrefix.

FILE

  • Fixed an issue that empty text isn’t supported in createFileFromText.

TABLE

  • Fixed an issue that uncaught TypeError could be thrown from createTable when request is not sent properly.
Commits

The new version differs by 19 commits.

  • 0557d02 Merge pull request #535 from jiacfan/dev
  • 47714c2 Optimize ts declarisions.
  • 1600bf2 Upgrade version to 2.10.2.
  • 34bf245 Update recordings for mock test.
  • 1027077 Use Buffer.alloc in HmacSha256Sign.
  • 23d961f Change code to use xmlbuilder ^9.0.7 and extend ^3.0.2.
  • 4fd4a2f Support empty text in API createFileFromText.
  • 4be9714 Upgrade extend to 3.0.2.
  • e9620f7 Upgrade xmlbuilder to 9.0.7.
  • 0013a55 Browser sample fixes
  • 60ae42a Address uncaught TypeError in table service
  • fd1e656 Remove deprecated Buffer constructor calls
  • 3dd857b Fix spelling in README.md
  • 327dbac Update BreakingChanges.md
  • 7e16451 Fixed the heading Project Setup

There are 19 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 🌴

Write script to automatically open issue for scan fails

We will try to improve the reliability of webhint by automatically scanning sites, and opening issues if something fails with webhint so we know where the problems are.


The plan is to have workers scan lots of websites periodically with webhint and if sometime timeouts/fails/etc., have a script open issues so that we can look into the problems.

The issues will have the following form:

Title: [<issue reason>] <url>

Body: <error message (if applicable)>

issue reason can be one of: crash, error, timeout (other?)

Issues will also have tags such as the issue reason and the scan number. To be able to scale up, we will use the issue reason, scan number in combination with the URL to close issues open in previous scans and now seen in the current scan.

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

The dependency applicationinsights was updated from 1.0.5 to 1.0.6.

🚨 View failing branch.

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

applicationinsights 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).

Release Notes for 1.0.6
  • #438 Fix spawned PowerShell processes hanging on Windows 7
  • #437 Fix infinite ACL related PowerShell processes spawning if one hangs
  • #371, #428 Fix nested custom properties report as [object Object], null/undefined property values are dropped
Commits

The new version differs by 9 commits.

  • de8679a Merge pull request #442 from Microsoft/develop
  • 818332f Bump package.json for 1.0.6 (#441)
  • d802bfc Fix timezone specific unit tests (#440)
  • da57f56 Fix powershell related bugs in Windows 7 (#439)
  • 773958d Merge pull request #428 from willmorgan/patch-1
  • c0d5e5b Skip functions from trace properties
  • 0b69674 Better handle trace obj/arr/err; allow toJSON
  • 95dabb8 Update tests to convert null/undefined to ""
  • e14b0ba Convert null, undefined props to empty strings

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 hint is breaking the build 🚨

Version 3.4.0 of hint was just published.

Branch Build failing 🚨
Dependency hint
Current Version 3.3.2
Type dependency

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

hint 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).

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 🌴

sync service too slow in production

The sync service is processing messages too slow in production. The reason is the lock we have at the job ID level and the amount of messages related to a job.
After talking with @sarvaje there are 2 things we can do to improve this:

  • Process several messages at the same time. The sync job will get n number of messages, group the results by job Id and just do one insert for those. Worst case scenario we don't improve the speed, best case, we improve it by n.
  • With the changes on #31, we are now sending one message per rule result. That means about 20 message per scan, all related to the same ID. This is the biggest thing slowing down the process. We should only split the results if the message is too big (max Service Bus size is 256kB, we'll say that a too big message is about 220kB)

@sonarwhal/core FYI, @sarvaje and myself are working on this already.

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

The dependency lodash was updated from 4.17.10 to 4.17.11.

🚨 View failing branch.

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

lodash 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).

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 connect-mongo is breaking the build 🚨

The dependency connect-mongo was updated from 2.0.2 to 2.0.3.

🚨 View failing branch.

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

connect-mongo 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).

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 🌴

Issue deploying AKS

When we try to deploy AKS using the deployment script, we get this error:

Deployment failed. Correlation ID: d2e47ad2-8acb-4085-bce4-ca29fdd4d256.
{
  "status": "Failed",
  "error": {
    "code": "ResourceDeploymentFailure",
    "message": "The resource operation completed with terminal provisioning state 'Failed'.",
    "details": [
      {
        "code": "DeploymentFailed",
        "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.",
        "details": [
          {
            "code": "BadRequest",
            "message": "{\r\n  \"error\": {\r\n    \"code\": \"RoleAssignmentUpdateNotPermitted\",\r\n    \"message\": \"Tenant ID, application ID, principal ID, and scope are not allowed to be updated.\"\r\n  }\r\n}"
          }
        ]
      }
    ]
  }
}

I have been trying different solutions, but nothing worked.

Maybe we need to split the template.json for aks and deploy everything one by one, instead of having a template with multiple things.

Ensure the time is set

In some cases, the time services fails, in those cases, we should do:

  1. Retry more times.
  2. Set the time of the machine (ensuring that is always greatest or equal to the previous time) e.g. started >= queued, finished >= started.

An in-range update of @types/lodash is breaking the build 🚨

The devDependency @types/lodash was updated from 4.14.116 to 4.14.117.

🚨 View failing branch.

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

@types/lodash 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).

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 🌴

Send multiple messages if results size is too big

Service Bus has a limitation of 256kB per message and some sites have quite a lot of errors (and this will just become worse in the future by adding more rules).
Before sending the results the worker should check the size of the messages and if need it, split it into multiple messages to avoid this problem.


Original text

The status of the job remains as "started" and the scan never ends. Scanning of the same url works running sonar locally.

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

Version 4.4.6 of tar was just published.

Branch Build failing 🚨
Dependency tar
Current Version 4.4.5
Type dependency

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

tar 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 1 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 🌴

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

Version 3.1.0 of hint was just published.

Branch Build failing 🚨
Dependency hint
Current Version 3.0.1
Type dependency

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

hint 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 @types/node is breaking the build 🚨

The devDependency @types/node was updated from 10.9.4 to 10.10.0.

🚨 View failing branch.

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

@types/node 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 could not complete due to an error (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 🌴

Recomend to use the cli when timeout

If we kill a process because of a timeout, I think we shouldn't set the status to error, but we should recommend the users to use @sonarwhal/sonar instead.

For example, the site www.as.com has a couple of timeouts, because the scan takes too much time.

@sonarwhal/core thoughts?

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 we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

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

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, 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 integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

Migrate to kubernetes

  • Deploy the ARM template
  • Install nginx in one of the machines
    • Script to automate this
  • Link to current DB
  • Redirect to the new endpoint (@molant)

Permanently delete url generated from webhint online scanner

We have used online webhint scanner to generate report for our website.

I would like to know if it is possible to permanently delete footprints of our website, or the url which was given to us by online webhint scanner. I would like to permanently delete that URL or delete any data specific to our website. Let me know if it is possible.

An in-range update of @hint/hint-no-broken-links is breaking the build 🚨

The dependency @hint/hint-no-broken-links was updated from 1.0.6 to 1.0.7.

🚨 View failing branch.

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

@hint/hint-no-broken-links 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).

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 @types/sinon is breaking the build 🚨

The devDependency @types/sinon was updated from 5.0.5 to 5.0.6.

🚨 View failing branch.

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

@types/sinon 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).

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 sinon is breaking the build 🚨

Version 5.0.10 of sinon was just published.

Branch Build failing 🚨
Dependency sinon
Current Version 5.0.9
Type devDependency

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

sinon 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 could not complete due to an error Details

Commits

The new version differs by 9 commits.

  • 4313d2d Update docs/changelog.md and set new release id in docs/_config.yml
  • e21c92a Add release documentation for v5.0.10
  • 41d0dcb 5.0.10
  • 928379c Update History.md and AUTHORS for new release
  • 5ca48d3 Merge pull request #1802 from ifrost/feature/restore-default-sandbox-fake-timers
  • 087bc1c Cache reverse function
  • d19a4c0 Add issue number
  • 6799e1c Use fakeTimers in the default sandbox
  • 8b6f8a8 Revert spied fakeTimers to original state

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 multiparty is breaking the build 🚨

Version 4.2.0 of multiparty was just published.

Branch Build failing 🚨
Dependency multiparty
Current Version 4.1.4
Type dependency

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

multiparty 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 9 commits.

  • cc4c08c Release 4.2.0
  • e85b38c Fix placement of random-bytes dependency
  • 17e6f7d lint: place commas last
  • ae1e2eb build: use yaml eslint configuration
  • a9e96c6 perf: remove parameter reassignment
  • b153e03 Use http-errors for raised errors
  • 1746d72 Use random-bytes module for polyfill
  • f2296df lint: remove dangling commas
  • 536bad9 examples: update placement of response in azureblobstorage

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 @hint/hint-no-p3p is breaking the build 🚨

The dependency @hint/hint-no-p3p was updated from 1.0.3 to 1.0.4.

🚨 View failing branch.

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

@hint/hint-no-p3p 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).

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 🌴

Admin page

Add an admin page so it's easier to update the configuration, check the status of the queue, how many scans so far, etc.

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.