Nahuel Scotti singuerinc

Publish to private npm registry from your CI pipeline

If you want to publish packages to your private registry, e.g. to jfrog.io/Verdaccio/... you should note some important things:

1) Authenticate on your local machine

To authenticate against the private repository, you've to use the npm cli tool. But first you should get your API access token. That's safer than using your password.

npm adduser --registry https://<registry_url>/<api_path>/ --always-auth

Container Linux (CoreOS), digitalocean and starting docker on boot

Container Linux (CoreOS) doesn't enable the docker systemd service by default. If you start a container with the --restart=always flag, for example, your container will not start up again automatically after a reboot. This may be desirable if you're running a cluster with an orchestration system that will handle this for you, but if you are using Container Linux with a single instance you might want your containers to start up by themselves. Of course you can easily enable to systemd service from the command line, but the best way is to pass an Ignition config file during the droplet creation process.

Under the "Select additional options" section, select "User Data"
In the box, paste the following Ignition config

{
  "ignition": { "version": "2.2.0" },
  "systemd": {
    "units": [{
 "name": "docker.service",

	# on a situation that both publish on npm and gpr are required. the package.json file should stay clean!
	# but other ways to set the registry won't work so there we should change the package.json on bash!
	# there we go:
	jobs:
	publish-gpr:
	runs-on: ubuntu-latest
	steps:
	- uses: actions/checkout@v1
	- uses: actions/setup-node@v1
	with:

	// Simple example, but the idea holds for more complex objects.


	/* 1) Start with OO */

	// user.js
	class User {
	constructor(firstName, lastName, email) {
	this.firstName = firstName
	this.lastName = lastName

	# Assume we are in your home directory
	cd ~/

	# Clone the repo from GitLab using the `--mirror` option
	$ git clone --mirror [email protected]:mario/my-repo.git

	# Change into newly created repo directory
	$ cd ~/my-repo.git

	# Push to GitHub using the `--mirror` option. The `--no-verify` option skips any hooks.

	# There was a day where I have too many color schemes in iTerm2 and I want to remove them all.
	# iTerm2 doesn't have "bulk remove" and it was literally painful to delete them one-by-one.

	# iTerm2 save it's preference in ~/Library/Preferences/com.googlecode.iterm2.plist in a binary format
	# What you need to do is basically copy that somewhere, convert to xml and remove color schemes in the xml files.

	$ cd /tmp/
	$ cp ~/Library/Preferences/com.googlecode.iterm2.plist .
	$ plutil -convert xml1 com.googlecode.iterm2.plist
	$ vi com.googlecode.iterm2.plist

	#!/bin/bash

	# Before running this script, open Disk Utility.
	#
	# Partition USB Stick:
	# * 1 Partition
	# * Options -> GUID Partition Table
	# * Mac OS Extended (Journaled)
	# * Name: Foobar
	#

	# First install tmux
	brew install tmux

	# For mouse support (for switching panes and windows)
	# Only needed if you are using Terminal.app (iTerm has mouse support)
	Install http://www.culater.net/software/SIMBL/SIMBL.php
	Then install https://bitheap.org/mouseterm/

	# More on mouse support http://floriancrouzat.net/2010/07/run-tmux-with-mouse-support-in-mac-os-x-terminal-app/