sharadhr

$HOME, Not So Sweet $HOME

• Preface
• 1 What is $HOME to you?
• 2 Setup
  • 2.1 Linux
    • 2.1.1 $HOME
    • 2.1.2 Dot-files and dot-directories
    • 2.1.3 XDG Base Directories
• 2.1.4 xdg-user-dirs

elminson

Commands to deploy Laravel API App in GCP

in the console after deploy LAMP Certified by Bitnami

Install the project

cd /opt/bitnami/apache2/htdocs

sudo git clone https://github.com/elminson/gc_lamp_laravel.git todo

cd todo

sudo composer install

un-versed

const { ServiceProvider } = require('@adonisjs/fold')
const path = require('path')
const fs = require('fs')
const Drive = use('Drive')
const Helpers = use('Helpers')

class FileUpload extends ServiceProvider {
  register () { }

  boot () { }

abhaywawale

<template>
  <v-container fluid>
    <v-layout align-start justify-center>
      <v-flex xs4 class="elevation-2 ma-2">
        <v-tabs v-model="model" color="cyan" dark slider-color="yellow">
          <draggable v-model="tabs" class="v-tabs__container" @update="tabUpdate">
            <v-tab v-for="(tab, index) in tabs" :key="index" :href="`#tab-${index}`">
              {{ tab.name }}
            </v-tab>
          </draggable>

EmadAdly

1. Add eslint and eslint-loader and eslint-plugin-vue to your projects package.json file

npm i eslint eslint-loader eslint-plugin-vue --save-dev

2. Create a base configuration by --init

ustun

;;; runs eslint --fix on the current file after save
;;; alpha quality -- use at your own risk

(defun eslint-fix-file ()
  (interactive)
  (message "eslint --fixing the file" (buffer-file-name))
  (shell-command (concat "eslint --fix " (buffer-file-name))))

(defun eslint-fix-file-and-revert ()
  (interactive)

blackfalcon

Git-workflow vs feature branching

When working with Git, there are two prevailing workflows are Git workflow and feature branches. IMHO, being more of a subscriber to continuous integration, I feel that the feature branch workflow is better suited, and the focus of this article.

If you are new to Git and Git-workflows, I suggest reading the atlassian.com Git Workflow article in addition to this as there is more detail there than presented here.

I admit, using Bash in the command line with the standard configuration leaves a bit to be desired when it comes to awareness of state. A tool that I suggest using follows these instructions on setting up GIT Bash autocompletion. This tool will assist you to better visualize the state of a branc

CristinaSolana

1. Clone your fork:

git clone git@github.com:YOUR-USERNAME/YOUR-FORKED-REPO.git

2. Add remote from original repository in your forked repository:

cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream