This is a Bill Of Materials to build your PaaS
Slides from the talk: https://www.slideshare.net/racktear/diy-paas-with-docker-consul-and-python
| #!/usr/bin/env bash | |
| # https://developers.supportbee.com/blog/setting-up-cucumber-to-run-with-Chrome-on-Linux/ | |
| # https://gist.github.com/curtismcmullan/7be1a8c1c841a9d8db2c | |
| # https://stackoverflow.com/questions/10792403/how-do-i-get-chrome-working-with-selenium-using-php-webdriver | |
| # https://stackoverflow.com/questions/26133486/how-to-specify-binary-path-for-remote-chromedriver-in-codeception | |
| # https://stackoverflow.com/questions/40262682/how-to-run-selenium-3-x-with-chrome-driver-through-terminal | |
| # https://askubuntu.com/questions/760085/how-do-you-install-google-chrome-on-ubuntu-16-04 | |
| # Versions | |
| CHROME_DRIVER_VERSION=`curl -sS https://chromedriver.storage.googleapis.com/LATEST_RELEASE` |
This is a Bill Of Materials to build your PaaS
Slides from the talk: https://www.slideshare.net/racktear/diy-paas-with-docker-consul-and-python
My friend Michael Jackson turned off github issues on one of his smaller projects. It got me thinking...
Maintainers getting burned out is a problem. Not just for the users of a project but the mental health of the maintainer. It's a big deal for both parties. Consumers want great tools, maintainers want to create them, but maintainers don't want to be L1 tech support, that's why they
Install latest Ansible via pip + dependencies via a shell script
This file is used to install ansible in test kitchen when you set in the kitchen.yaml file
The Modern.ie Virtual Machine Images – VMs used for testing several versions of IE – are now also available as vagrant boxes. Here’s the list:
PdfLatex is a tool that converts Latex sources into PDF. This is specifically very important for researchers, as they use it to publish their findings. It could be installed very easily using Linux terminal, though this seems an annoying task on Windows. Installation commands are given below.
sudo apt-get install texlive-latex-base
Есть CSS/SASS/LESS код с KSS-комеентариями. KSS-комментарий — это блок комментариев, заканчивающийся строкой "Styleguide n", где n — номер параграфа (1, 2.5, 334.5.7.1). Блоком KSS разметки может быть как многострочный комментарий, так и группа инлайновых комментариев, идуших друг за другом. Блок KSS-разметки документирует код, следующий за ним. Все комментарии, которые не являются KSS-блоками, относятся к коду и должны быть включены в него. Может быть код без документации (в начале файла). И может быть документация без кода, если 2 блока KSS-разметки идут друг за другом, и между ними нет кода. Задача: распарсить документ на массив пар kss - код.
На данный момент есть 2 незаконченных решения.
| #!/bin/bash | |
| # Create tmp dir | |
| echo "Creating temporal dir..." | |
| mkdir ~/installation-dev | |
| cd ~/installation-dev | |
| # Add Google Chrome to APT | |
| echo "Adding Google Chrome to APT..." | |
| wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add - |