npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

study-egg-hot-deploy

v1.0.1

Published

hot-reload egg.js application

Downloads

2

Readme

egg-deploy

hot-deploy tool for egg project

Install

$ npm i study-egg-hot-deploy --save

Usage

1. add .deploy.yml config file in project root directory

  • Config arguments

    • instances - application instance array, example: [{ port: 7008, title: 'egg-node-server' }]

    • startCommand - nginx start command, default: service nginx start

    • reloadCommand - nginx config reload, default: nginx -s reload

    • waitStopTime - waited time to stop application, default: 5000

    • nginxconcpath - nginx config file path, it is a relative path and also can a absolute path, for example vre-node.conf, but you must contain vre.conf file in nginx config file and reload nginx

    • # vre-node.conf
      upstream vre-node {
        server localhost:7007;
        server localhost:7008;
      }

finally .deploy.yml like this, Example:

instances:
 - 
  port: 7005
  title: egg-server-weekly-node-ts-2
 - 
  port: 7006
  title: egg-server-weekly-node-ts
nginxConfPath: /etc/nginx/upstream/weekly.conf
startCommand: service nginx start
reloadCommand: nginx -s reload
nginxConfPath: nginx.conf
waitStopTime: 5000

2. add egg-deploy to package.json to scripts

{
  "scripts": {
    "deploy": "egg-deploy start --env=prod --workers=2 --daemon",
    "stop": "egg-deploy stop"
  }
}

additional: egg-deploy is based on egg-scripts, also have start and stop command,and has same arguments, but title and port is in .deploy.yml file, so don't repeat to write.