Steve Todorov steve-todorov

Get the details to connect to your Nexus-managed npm repository

Note: Nexus group repositories (good example in this StackOverflow question) are out of this tutorial's scope. In any case, deployment to group repositories is currently still an open issue for Nexus 3 (and not intended ever to be implemented in Nexus 2). Thus, it is assumed that we'll push & pull to/from the same repository, and ignore the idea of groups hereon in.

Ask your sysadmin for a username & password allowing you to log into your organistation's Nexus Repository Manager.
Test the login credentials on the Nexus Repository manager at: http://localhost:8081/nexus/#view-repositories (localhost in our case is replaced by a static IP, and can only be connected to over VPN). If your organisation requires a VPN to connect to it, connect to that VPN before proceeding with this tutori

1 - install GPG tools : https://gpgtools.org/

2 - Create new key for your github email

3 - Add key to git on your local machine: git config --global user.signingkey YOURKEY

4 - configure git to sign all commits: git config --global commit.gpgsign true

5 - add to the bottom of ~/.gnupg/gpg.conf:

Running docker-compose as a systemd service

Files

File	Purpose
`/etc/compose/docker-compose.yml`	Compose file describing what to deploy
`/etc/systemd/system/docker-compose.service`	Service unit to start and manage docker compose
`/etc/systemd/system/docker-compose-reload.service`	Executing unit to trigger reload on `docker-compose.service`
`/etc/systemd/system/docker-compose-reload.timer`	Timer unit to plan the reloads

Markdown License badges

Collection of License badges for your Project's README file.
This list includes the most common open source and open data licenses.
Easily copy and paste the code under the badges into your Markdown files.

Notes

Badges are made with Shields.io.
This badges do not fully replace the license informations for your projects, they are only emblems for the README, that the user can see the License at first glance.
🇫🇷 Cette liste en français
Github has a new autodetection of the LICENSE file, which shows up the license at the repo overview

Protractor API

http://angular.github.io/protractor/#/api

Note: Most commands return promises, so you only resolve their values through using jasmine expect API or using .then(function()) structure

Based on this post: https://spagettikoodi.wordpress.com/2015/01/14/angular-testing-cheat-sheet/ by @crystoll

Control browser

browser.get('yoururl'); // Load address, can also use '#yourpage'

Testing An Angular CLI Project in a Headless Environment

I recently started a new project and we used [Angular CLI][4] to get started. Angular CLI, as in the name, is a command line utility for creating and managing Angular 2 projects. Using Angular CLI to create a project is very easy and it gives you a great starting point for new Angular 2 projects. The only draw back I found was that in my mind it wasn't CI ready.

Angular CLI out of the box gives you a few unit tests and an end to end (e2e) test. This is great because you can generate a project and set up your build server to build the artefacts. This is where I ran into problems.

Having everything generated for you is great until something you want to do does not work; and this is where I was. I wanted to build and test my angular application on a headless build agent. The generated code from Angular CLI runs tests using Google Chrome by default. Which is fine, but running Google Chrome on a bui

npm v3.10 - ◾

⚠️ This tutorial is outdated, but most of the commands are still relevant.

Update npm itself

npm install -g npm
# Downgrade to a specific version
npm install -g npm@2

Introduction

Searching for artifacts should be easy and consistent across all layouts. This is where Artifact Query Language (or AQL for short) comes into play. It needs to be able to provide a way for the end user to easily find what they are looking for.

Artifact Query Language

Search queries are constructed using Tokens where each token is a pair of <key>:<value> separated with :.

	<html xmlns:o="urn:schemas-microsoft-com:office:office"
	xmlns:w="urn:schemas-microsoft-com:office:word"
	xmlns:m="http://schemas.microsoft.com/office/2004/12/omml"
	xmlns="http://www.w3.org/TR/REC-html40">

	<head>
	<meta name=Title content="">
	<meta name=Keywords content="">
	<meta http-equiv=Content-Type content="text/html; charset=utf-8">
	<meta name=ProgId content=Word.Document>

	#!/bin/bash

	# input folders:
	# version : contains a file called number with the current version
	# source-code : contains the source code

	# output folders:
	# build: contains the built jar

	set -ex