jonaskello

# Make sure you have enabled "Expose hardware assisted virtualization to the guest OS" for the VMWare CPU

Write-Host "##############################`nInstalling features: Containers, Hyper-V, Hyper-V-PowerShell`n##############################`n"
Install-WindowsFeature Containers
Install-WindowsFeature Hyper-V
Install-WindowsFeature Hyper-V-PowerShell

Write-Host "##############################`nDisabling firewall`n##############################`n"
Set-NetFirewallProfile -Profile Domain,Public,Private -Enabled False

ssplatt

#########
# setup
########

curl -sSk https://192.168.50.2:8000/hook/pxe_setup \
    -H 'Content-type: application/json' \
    -H 'X-Salt-API-Key: testsecret' \
    -d '{
    "id": "myhost01",
    "dc_id": "vagrant",

alekseykulikov

Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.

My 3 developers team has just developed React.js application with 7668 lines of CSS (and just 2 !important). During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.

Here are main principles we use to write CSS for modern (IE11+) browsers:

• SUIT CSS naming conventions + SUIT CSS design principles;
• PostCSS + CSSNext. Future CSS syntax like variables, nesting, and autoprefixer are good enough;
• Flexbox is awesome. No need for grid framework;
• Normalize.css, base styles and variables are solid foundation for all components;

pipitone

---
- name: YP
  hosts: nis_slave:nis_client
  sudo: yes
  vars: 
    - min_uid: 1000
    - min_gid: 1000
    - nis_master: "{{groups['nis_master'][0]}}"
  tasks:
    # Basic idea here is we do things in two steps: