Latest Posts

Run the below command in any directory where files need to be served in a project with a simple directory like a js/** and css/** folders

 

browser-sync start --server --files "js/*.js, css/*.css"

//output

[BS] Access URLs:
--------------------------------------
Local: http://localhost:3000
External: http://192.168.1.109:3000
--------------------------------------
UI: http://localhost:3002
UI External: http://192.168.1.109:3002

 

// if not installed globally already, then

npm install -g browser-sync
 

 

 

Task: a ton of data comes in the form of zipped massive folders require to be decompressed.  

The Problem

Whenever you use a wildcard (*), the shell itself will expand that and pass the results to the program rather than the program handling the expansion itself. That means that our previous command was actually expanded to the following before being executed:

unzip a.zip b.zip c.zip

The Solution

Just because the shell expands out wildcard characters automatically doesn’t mean that programs can’t as well. The simple solution to this problem is to quote the argument to prevent the shell from interpreting it:

unzip '*.zip'

Sass already comes with a lot of power, from nesting html tags to generating mixins, and many more powerful feutures that speed up development of highly scalable cascading stylesheets. 

 

To start to use sass, compass ecc, Ruby must be installed. Osx ships with Ruby out of the box, other operating systems have several options to install like ruby installer. Finally, comes Ruby Bundler to easly build and generate templates for individual projects.

When you try this 

 

sudo gem install sass

 

You may get this error:

 

ERROR:  While executing gem ... (Errno::EPERM)
    Operation not permitted - /usr/bin/sass

 

That is because we need to specify the directory where binary files are located like so:

 

sudo gem install -n /usr/local/bin sass

 

There are many libraries and mixins out there. Here are some of the most famous ones and the commands to install them with Gem: 


sudo ge....... Read More

This example is from github

 

  1. Open Terminal.

  2. Paste the text below, substituting in your GitHub email address.

    ssh-keygen -t rsa -b 4096 -C "your_email@example.com"
    # Creates a new ssh key, using the provided email as a label
    Generating public/private rsa key pair.
    
  3. When you're prompted to "Enter a file in which to save the key," press Enter. This accepts the default file location.

    Enter a file in which to save the key (/Users/you/.ssh/id_rsa): [Press enter]
    
  4. At the prompt, type a secure passphrase. For more information, see "Working with SSH key passphrases".

    Enter passphrase (empty for no passphrase): [Type a passphrase]
    Enter same passphrase again: [Type passphrase again]
Loading