bast

sudo pacman -S ruby ruby-rdoc gcc make

gem update --user-install
gem install jekyll --user-install

# finally add $HOME/.gem/ruby/2.7.0/bin to your PATH variable

subfuzion

Common Options

-#, --progress-bar Make curl display a simple progress bar instead of the more informational standard meter.

-b, --cookie <name=data> Supply cookie with request. If no =, then specifies the cookie file to use (see -c).

-c, --cookie-jar <file name> File to save response cookies to.

ertseyhan

#!/bin/bash

sudo mount -o remount,size=10G,noatime /tmp
echo "Done. Please use 'df -h' to make sure folder size is increased."

PurpleBooth

Contributing

When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.

Please note we have a code of conduct, please follow it in all your interactions with the project.

Pull Request Process

1. Ensure any install or build dependencies are removed before the end of the layer when doing a

pdarragh

Jekyll NavBar

In building a site powered by Jekyll and hosted by GitHub, I wanted the ability to highlight the current page's tab in the bar. I also wanted the bar to support second-level items (i.e. a dropdown), which proved somewhat tricky. This is the solution I arrived at after a few hours of fiddling around.

Construction

The contents of the navigation bar are contained in a data file located at _data/navigation.yml. This makes it accessible via the site-wide Liquid element {{ site.data.navigation}}. You can see the file for the formatting I used.

How it Works

jonashackt

java -Xdebug -Xrunjdwp:server=y,transport=dt_socket,address=8000,suspend=n -jar target/myproject-0.0.1-SNAPSHOT.jar

PurpleBooth

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Prerequisites

pololee

/* Change the color of individual Social Icons */
a.icon-feed             {color:#DC622C;}    /* Change to desired color */
a.icon-twitter          {color:#00B6F1;}    /* Change to desired color */
a.icon-facebook         {color:#3B5998;}    /* Change to desired color */
a.icon-google           {color:#C20806;}    /* Change to desired color */
a.icon-instagram        {color:#2C6A93;}    /* Change to desired color */
a.icon-wordpress        {color:#04769C;}    /* Change to desired color */
a.icon-youtube          {color:#C31A1E;}    /* Change to desired color */
a.icon-pinterest        {color:#C91517;}    /* Change to desired color */
a.icon-github           {color:#040204;}    /* Change to desired color */

austinhyde

Observables

You don't really need a framework or fancy cutting-edge JavaScript features to do two-way data binding. Let's start basic - first and foremost, you need a way to tell when data changes. Traditionally, this is done via an Observer pattern, but a full-blown implementation of that is a little clunky for nice, lightweight JavaScript. So, if native getters/setters are out, the only mechanism we have are accessors:

var n = 5;
function getN() { return n; }
function setN(newN) { n = newN; }

console.log(getN()); // 5

setN(10);

imranismail

//SearchController.php
public function autocomplete(){
	$term = Input::get('term');
	
	$results = array();
	
	$queries = DB::table('users')
		->where('first_name', 'LIKE', '%'.$term.'%')
		->orWhere('last_name', 'LIKE', '%'.$term.'%')
		->take(5)->get();