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

qudb

v1.3.0

Published

____ ____ _____/ / /_ / __ `/ __ / __ \ / /_/ / /_/ / /_/ / \__, /\__,_/_.___/ /_/ quickly start and manage databases

Downloads

25

Readme

qudb

quickly start and manage databases

oclif Version Downloads License

individual command reference

  1. init
  2. start
  3. status / ps
  4. help

installation

QUDB can be installed by npm, or if you don't want to install it, it can be used with npx.

	npm install -g qudb
	qdb --help
	
	# no install
	npx qudb --help # replace qdb with npx qudb

usage

# start up a postgres database
qdb start postgres

# start up a postgres database and see whats happening
qdb start postgres

# see running databases
qudb ps # qdb status also works

# start a database on a specific port
qdb start postgres -p 3000

# start a database on a specific network
qdb start postgres --network amazing

# start a database and save data in a specific dir (defaults to ./qudb/data)
qdb start postgres --data path/to/dir

# start a database with a specific name
qudb start postgres --name fantastic

# kill a database (terminates process, does not mess with data)
qudb stop <name>

# nuke a database (no data saved, db stopped, config stays)
qudb nuke <name>

# start a database with credentials
qudb start postgres -u root -p securityismypassion

# start a database but pass in environment variables
qudb start postgres -e "amazing=true"

why this exists

  • half the projects on the internet assume you have mongo or postgres or mysql or something setup and running
  • legit no one likes to have that on their computer, even less people really want to clean out their databases or keep them up to date or keep them installed

solution

  • use docker to make any db you need, using volumes stored at a consistent location to allow for persistence
  • allow for temporary development sessions, where qudb will save your data until you want to erase it or whatever

qudb File

You can also save credentials in a folder so you don't need to remember a name

qudb.yaml

name: my_db
type: postgres | redis | mysql (file an issue for more types!
username: root
password: password
save: true
store: path to qudb file directory
data: ./.qudb/data # default
exposedPorts:
  - hostPort: 5432
    containerPort: 5432

Now, you can streamline your commands - no more name needed

qudb start
qudb stop
qudb status

wait, isn't this just a wrapper for docker?

yes indeed! I'm just lazy of looking up the right docker command for each db type, and it's getting real frustrating