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

pi-up

v0.0.1

Published

Update a Raspberry Pi remotely using a custom script on a desired schedule

Downloads

2

Readme

pi-up

The goal of this project is to execute a custom update script on a Raspberry Pi according to a desired schedule and be notified of the results.

Background

Truthfully, this project could be used to execute any custom script on a Raspberry Pi according to a desired schedule.

The primary focus with this project though, is to update a Raspberry Pi. Also, this project currently assumes the Raspberry Pi is running Pi-hole and will attempt to update that as well.

Usage

Prerequisites

  • Must have SSH access to Raspberry Pi
  • Must know the IP address of your Raspberry Pi
  • Git must be installed: apt-get install git
  • Node.js must be installed on Raspberry Pi
  • Must have sendmail package installed: apt-get install sendmail

Configuration

To get started you will want to update the config.json file in this repo. Below is a sample configuration:

{
    "scheduleCron": "0 0 18 * * *",
    "runOnInit": true,
    "scriptPath": "/home/pi/pi-up/custom-update.sh",
    "email": "[email protected]"
}
  • scheduleCron - crontab describing schedule of which to run update script. 6 fields supported, finest granularity being 1 second.
  • runOnInit - Whether or not the update script should be ran on initialization of schedule or not. When false, first run will happen on next scheduled occurrence.
  • scriptPath - Path to custom script containing update routine. It's much safer to use the exact path, instead of a relative path to the script.
  • email - Optional field for email address, email is sent to this address with results of update routine. Simply leave empty to not send an email.
  • name - Optional field to identify your Raspberry Pi, this will be included in the subject of the email sent to you.

Starting scheduled update

  1. SSH into Raspberry Pi
    ssh pi@<your-pi-ip-address>
  2. Git clone this repo (on Raspberry Pi):
    git clone https://github.com/rcasto/pi-up
  3. Change directory into repository folder:
    cd pi-up
  4. Install npm package dependencies:
    npm install
  5. Adjust configuration and script to your liking
  6. Start update schedule:
    npm start

Running on Raspberry Pi bootup

Edit /etc/rc.local, adding:

node /home/pi/pi-up/index.js &

Note: You will want to have changed your scriptPath in the configuration to use an exact path.

Resources