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

atosone-cli

v1.4.3

Published

A CLI tool for atosone.com, deploy your full-stack apps to the cloud

Downloads

16

Readme

atosone-cli

A CLI tool for atosone.com, deploy your full-stack apps to the cloud

Installation

Install with npm install -g atosone-cli

Commands

Usage : atosone-cli command

Options list :

-a [APPID]

Input your appId directly in the command line instead of using init.

-t [TOKEN]

Input your token directly in the command line instead of using login.

-i [SUFFIX]

(fs pull specific) Only pulls files with the specified suffix.

-e [SUFFIX]

(fs pull specific) Exclude files with the specified suffix from bein pulled.

--skip-existing-files

(fs pull specific) Skip files already existing in your filesystem.

Available commands :

Setup

login Login to our service

init <app-id> Link folder with your app-id

Filesystem

fs pull <source-folder> Pull folder from SERVER to LOCAL

fs push <folder-to-push> <opt: dest> Push folder from LOCAL to SERVER

Database - CloudBackend

db pull Retrieves .sql file of your database from SERVER to LOCAL

db push <sql-file> Restore the database on SERVER from the LOCAL .sql backup provided

Api - CloudBackend

api pull <opt: function_id> Pull all (or one) function(s) of your CloudBackend to LOCAL

api push <opt: function_id> Push all (or one) function(s) from LOCAL to your CloudBackend

Export

export <path> Export your project to the specified folder

Help

help Displays this help text

Usage examples

After logging-in through our login command or using the -t flag, and setting up your appId with -a or with init. You will be able to use the CLI. Here are some examples to help you through the process.

Pulling only files ending by ".js" in the root folder of your appdrag app.

atosone-cli fs pull -i .js.

Pulling specific functions using a Function Id

atosone-cli api pull FUNCTION_ID

To be able to find your function ID you simply need to visit the specific function in your cloudbackend and look at the URL. It will look like this : www.atosone.com/cloudbackend.html?appId=YOUR_APP_ID#FUNCTION_ID Simply copy the function ID after the '#', and paste it into your command.

Pushing specific folder from your local files into your project

atosone-cli fs push YOUR_FOLDER

Our CLI will create a zip of our folder and push it to the root of your appdrag project.

Pushing specific folder from your local files into a specific folder in your project

atosone-cli fs push YOUR_FOLDER DESTINATION_FOLDER

Setting up continuous delivery from development project A to production project B

Import API Functions from project A:

atosone-cli -a dev-project-a -t USER_API_TOKEN api pull

Push API Functions to production project B:

atosone-cli -a prod-project-b -t USER_API_TOKEN api push

Up to date functions on the production project won't be updated if their last update date are greater or equal to the ones on the dev project on AppDrag. If you do changes locally, don't forget to push it on the dev project before pushing to the production, if not, updates will be skipped.