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

flywheel-deploy-client

v0.0.1

Published

A client for deployling wordpress sites with FlyWheel. Useful in build tools and e.g. bitbucket pipelines.

Downloads

3

Readme

flywheel-deploy-client

A small client library for deploying a WordPress site to FlyWheel.

Usage

Be sure the following environment variables are set when using the client.

  • DEPLOY_SFTP_USERNAME: FlyWheel SFTP username
  • DEPLOY_SFTP_PASSWORD: FlyWheel SFTP password
  • DEPLOY_WP_ROOT_PATH: FlyWheel SFTP remote directory (e.g. /org-your-org/your-site_staging)

Then in your build script...

const DeployClient = require('flywheel-deploy-client'),
  client = new DeployClient('/path/to/loca/wordpress');
 
 client.deploy();

Process

Currently, this client doesn't look at git or any other version control for your project. It simply recursively deletes the following remote directories:

  • wp-content/plugins
  • wp-content/mu-plugins
  • wp-content/themes

And then uploads the corresponding directories from your local project in their places.

Note: This client uses console.log( . . . ) to output it's progress.

TODO

  • [ ] Use a config object passed to the constructor instead of env variables.
  • [ ] Report progress, failures, and completion using Promises or EventEmitter

License

ISC