
Security News
GitHub Actions Supply Chain Attack Puts Thousands of Projects at Risk
A compromised GitHub Action exposed secrets in CI/CD logs, putting thousands of projects at risk and forcing developers to urgently secure their workflows.
If you like the project, please remember to star it so we can grow the community!
If you want your environment listed in the showcase, please submit a PR
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.
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
$ npm install -g myos
$ myos init ./template
$ cd template
$ myos create fooName
$ myos connect
Assuming you've already installed the tool, my personal configuration can be used to test out MyOS.
$ git clone https://github.com/rylandg/rylandg-myosfiles
$ cd rylandg-myosfiles
$ myos create rysetup
$ myos connect rysetup
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.
myos create <name>
Runs docker-compose up -d
from the current directory
myos connect
Connects to a previously created MyOS environment
myos restart <name>
Restart a previously created MyOS environment
myos remove <name>
Remove a running MyOS environment
FAQs
A fully dockerized development environment
The npm package myos receives a total of 0 weekly downloads. As such, myos popularity was classified as not popular.
We found that myos demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
A compromised GitHub Action exposed secrets in CI/CD logs, putting thousands of projects at risk and forcing developers to urgently secure their workflows.
Research
Security News
A malicious Maven package typosquatting a popular library is secretly stealing OAuth credentials on the 15th of each month, putting Java developers at risk.
Security News
Socket and Seal Security collaborate to fix a critical npm overrides bug, resolving a three-year security issue in the JavaScript ecosystem's most popular package manager.