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

@pistor/rokka-uploader

v2.0.0

Published

Monitors folders for new images and uploads them to Rokka.io.

Downloads

5

Readme

rokka-uploader

Monitors folders for new or changed images, uploads them to rokka.

Installation

To install rokka-uploader, you need to have Node.js installed. rokka-uploader requires Node.js version 10.14 or higher.

We recommend you install the latest LTS release, since that is what rokka-uploader is tested with.

With Node.js installed, run this command in your favourite shell:

npm install -g @pistor/rokka-uploader 

Configuration/usage

rokka-uploader uses dotenv for configuration. That gives you two options for configuration, namely a .env file, or environment variables.

Each is described in more detail below.

Regardless of how you configure rokka-uploader, you will need to configure at least two values, ROKKA_API_KEY and ROKKA_ORGANISATION. All other settings have reasonable defaults.

Using a .env file for configuration

This method involves placing a .env file in the folder where you run rokka-uploader. That could be the folder containing the images you want uploaded, this folder, or any other folder.

As example, we will pick the folder /opt/rokka-uploader. Make a copy of the .env.example file in this repository in the picked folder, rename it to .env and adjust the configuration as necessary.

When that is done, start rokka-uploader like this:

cd /opt/rokka-uploader
rokka-uploader

If you did not set MONITOR_GLOB in your .env file, rokka-uploader will now upload any .gif, .jpg, .jpeg, or .png file it finds in the folder where you started it, in our example /opt/rokka-uploader.

Using environmental variables

There’s a number of ways to set environmental variables, but explaining them all is beyond the scope of this article, so we will just show the simplest example, namely specifying them directly on the command line, by running rokka-uploader like this:

ROKKA_API_KEY=your-key-here ROKKA_ORGANISATION=your-name-here MONITOR_GLOB=/your/images/*.jpg rokka-uploader

In this example, we specify MONITOR_GLOB so rokka-uploader will look in the folder /your/images for .jpg files and upload them.

Like with the .env file method, if you do not specify MONITOR_GLOB, rokka-uploader will upload any .gif, .jpg, .jpeg, or .png file it finds in the folder where you started it.

Refer to .env.example to see what options are available.