Florian Kromer fkromer

Reference: RFC 2616 - HTTP Status Code Definitions

General

400 BAD REQUEST: The request was invalid or cannot be otherwise served. An accompanying error message will explain further. For security reasons, requests without authentication are considered invalid and will yield this response.
401 UNAUTHORIZED: The authentication credentials are missing, or if supplied are not valid or not sufficient to access the resource.
403 FORBIDDEN: The request has been refused. See the accompanying message for the specific reason (most likely for exceeding rate limit).
404 NOT FOUND: The URI requested is invalid or the resource requested does not exists.
406 NOT ACCEPTABLE: The request specified an invalid format.

Usage

(Create a symlink pytest for py.test)

pytest [options] [file_or_dir] [file_or_dir] ...

Help:

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

The 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.

Translations: (No guarantee that the translations are up-to-date)

🇫🇷 Cette liste en français

Theory:

your git repository can have more than one remote server; In this case we want to have two:

one for our private repository on gitlab (will be the default one, called origin)
one to be connected to the source repo on github, to be able to pull new changes (will be called upstream)

How to make a private fork from github to gitlab

	#!/bin/bash

	# Here short description of this script
	# This is just a template to be used for writing new bash scripts

	###
	# Based on Google Style Guide: https://google.github.io/styleguide/shell.xml
	# General remarks
	# * Executables should have no extension (strongly preferred) or a .sh extension.
	# * Libraries must have a .sh extension and should not be executable

	#!/bin/sh
	# Fresh install for CUDA 6.5 on Jetson TK1 for Linux for Tegra (L4T) 21.1
	# CUDA 6.5 REQUIRES L4T 21.1 !!!
	sudo apt-add-repository universe
	sudo apt-get update
	# This is for L4T r21.1 ; Update for your L4T i.e. r21.3
	wget http://developer.download.nvidia.com/compute/cuda/6_5/rel/installers/cuda-repo-l4t-r21.1-6-5-prod_6.5-14_armhf.deb

	# Install the CUDA repo metadata that you downloaded
	# This is for L4T 21.1 ; Update for your L4T i.e. 21.3


	#user nobody;
	#Defines which Linux system user will own and run the Nginx server

	worker_processes 1;
	#Referes to single threaded process. Generally set to be equal to the number of CPUs or cores.

	#error_log logs/error.log; #error_log logs/error.log notice;
	#Specifies the file where server logs.

	# derived from http://wiki.ros.org/ROSberryPi/Installing%20ROS%20Indigo%20on%20Raspberry%20Pi


	sudo sh -c 'echo "deb http://packages.ros.org/ros/ubuntu jessie main" > /etc/apt/sources.list.d/ros-latest.list'
	wget https://raw.githubusercontent.com/ros/rosdistro/master/ros.key -O - \| sudo apt-key add -


	sudo apt-get update
	sudo apt-get upgrade

	#!/usr/bin/env python
	# -- coding: utf-8 --
	'''
	A lint tool for robotframework cases.

	Robotframework best practices:
	TODO

	Supported checking points:

	FROM ros:indigo-ros-base
	# install ros tutorials packages
	RUN apt-get update && apt-get install -y \
	ros-indigo-ros-tutorials \
	ros-indigo-common-tutorials \
	&& rm -rf /var/lib/apt/lists/