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

myos

v1.0.3

Published

A fully dockerized development environment

Downloads

9

Readme

MyOS - develop and share command line environments

If you like the project, please remember to star it so we can grow the community!

Blog post about MyOS

Dockerhub

If you want your environment listed in the showcase, please submit a PR

High Level

Uses Docker + Docker Compose to provide a consistent and reproducible build environment. Base image assumes the minimum while still being useful out of the box.

Usage

Assumptions

Everything depends on myos base Docker image. This image is available on Dockerhub, but you may also build it using the included Dockerfile.

The default docker-compose.yml mounts your hosts ~/.ssh/authorized_keys file into the running container. This is what allows the openSSH server to authenticate you when you connect. This means you will need an authorized_keys file in the correct location with any keys you want to be able to use.

OSX Users: For display forwarding to work, you'll need to have X11 Quartz. It's crappy and I'd love to find an alternative.

Ctrl-D is the most sure fire way of getting out of the container

Setup

  1. Install the CLI
$ npm install -g myos
  1. Create a new template project
$ myos init ./template
$ cd template
  1. Start the container
$ myos create fooName
  1. Connect to the container
$ myos connect

Advanced usage

Assuming you've already installed the tool, my personal configuration can be used to test out MyOS.

  1. Clone my personal MyOS config
$ git clone https://github.com/rylandg/rylandg-myosfiles
  1. Create a MyOS based on my setup
$ cd rylandg-myosfiles
$ myos create rysetup
$ myos connect rysetup

API

Init

myos init <dir>

Creates the initial templates that the default docker-compose.yml expects. These are...

# vim
vim/binds.vim
vim/helpers.vim
vim/plugins.vim
vim/vimrc
# zsh
zsh/.zlogin
zsh/.zprofile
zsh/.zshenv
zsh/.zshrc
# tmux
tmux/tmux_saves
tmux/install_tmux.sh
tmux/tmux.conf

These files are empty (for the most part). You're expected to add your environment specific settings.

Create

myos create <name>

Runs docker-compose up -d from the current directory

Connect

myos connect

Connects to a previously created MyOS environment

Restart

myos restart <name>

Restart a previously created MyOS environment

Remove

myos remove <name>

Remove a running MyOS environment

Features

  • Configuring locale and colors
  • Creating a non-root user and setting necessary permissions
  • Setups OpenSSH for password-less login
  • Enabling X11 Display server
  • Super light, highly optimized base Ubuntu image
  • Mechanism to "safely" run multiple processes
  • Init for running your user process as PID > 1
  • OpenSSH server out of the box
  • ZSH
  • HTop
  • Vim8 with clipboard support
  • Latest Tmux built from source
  • XAuth and XDisplay packages for clipboard support

Issues/planned changes

  • Very vim focused, would like to see if its possible to support other editors (definitely Emacs)
  • Needs CLI command that allows you to copy another users MyOS environment
  • Multiple MyOS environments should be able to run simelataneously
  • SSH key for authorized_keys could be autogenerated
  • Potentially move away from NodeJS for CLI