Skip to content

Latest commit

 

History

History

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

gpm

A package manager built on top of Dat. For fun. THIS IS JUST A DEMO/TOY PROJECT. 🧸

oclif License

gpm components


See it in action

gpm in action

Usage

There are 2 things that you should do before start using gpm as your funny package manager.

First is to run your own registry, so, on one machine you should run

$ gpm registry

That will create a registry and start the registry endpoint on the current directory. You run this only once

The other task that everyone should run is the daemon. Looks like this:

$ gpm daemon

This will sync with the registry and keep seeding your local copy of it.

NOTE: before run the daemon be sure to set it up with the public key provided by the registry command. Take a look to the conf command

Boom 💥 ! You are ready to run your publish (newdep) or installs. 🆒

Commands

gpm conf [KEY] [VALUE]

Configuration for gpm.

USAGE
  $ gpm conf [KEY] [VALUE]

ARGUMENTS
  KEY    Key configuration.
  VALUE  Value configuration.

See code: src/commands/conf.js

gpm daemon [PORT] [REGISTRYID]

Fetch a package from the dat based registry

USAGE
  $ gpm daemon [PORT] [REGISTRYID]

ARGUMENTS
  PORT        [default: 9998] Starts the dat-rpc daemon on the selected port.
  REGISTRYID  [default: geut] Registry to use in gpm.

See code: src/commands/daemon.js

gpm help [COMMAND]

display help for gpm

USAGE
  $ gpm help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

gpm install [PACKAGE]

Fetch a package from the dat based registry

USAGE
  $ gpm install [PACKAGE]

ARGUMENTS
  PACKAGE  Download selected <package> from the dat based registry

OPTIONS
  -v, --version=version  Specific version to retrieve from the dat based registry

See code: src/commands/install.js

gpm newdep [PACKAGE] [REGISTRYID]

Add a new dependency to the registry

USAGE
  $ gpm newdep [PACKAGE] [REGISTRYID]

ARGUMENTS
  PACKAGE     [default: .] Path to the new dependencys package.json file.
  REGISTRYID  [default: geut] Registry to use in gpm.

DESCRIPTION
  ...
  This will add a new entry to the gpm registry.

See code: src/commands/newdep.js

gpm registry [DIRECTORY]

Run your own registry.

USAGE
  $ gpm registry [DIRECTORY]

ARGUMENTS
  DIRECTORY  [default: /Users/deka/Projects/talks/builing-up-on-dat/packages/gpm] Directory where to store the modules.

See code: src/commands/registry.js