nicolaslopezj

/* global $ */
function marcar(amountToTransfer, fecha, bchile) {
  let total = 0
  $('.linea1tablaSB input[type=checkbox]').map(function() {
    const input = $(this)
    const tr = input.parent().parent()
    const fileNameTr = tr.prev().prev()
    const fileName = fileNameTr.find('td:not([align=right]) strong').text()
    const date = fileName.split(' ')[2] + ' ' + fileName.split(' ')[3]
    const cuenta = $(tr.find('td')[5]).find('div:first').text().trim()

joadr

# Conectarse al servidor remoto
$ ssh root@armatubicicleta.cl
# Hago el dump en el sistema remoto
$ mongodump
# Comprimo el archivo en el sistema remoto
$ tar -zcvf armatubicicleta.tgz dump/armatubicicleta/
# Me descargo el archivo a mi sistema local (desde la terminal local)
$ scp root@armatubicicleta.cl:/root/dump/armatubicicleta.tgz /home/joaco/armatubicicleta.tgz
# Descomprimo el archivo
$ tar -zxvf armatubicicleta.tgz

ryanflorence

Folder Structure

Please note

While this gist has been shared and followed for years, I regret not giving more background. It was originally a gist for the engineering org I was in, not a "general suggestion" for any React app.

Typically I avoid folders altogether. Heck, I even avoid new files. If I can build an app with one 2000 line file I will. New files and folders are a pain.

laracasts

var gulp = require('gulp');
var gutil = require('gulp-util');
var notify = require('gulp-notify');
var sass = require('gulp-ruby-sass');
var autoprefix = require('gulp-autoprefixer');
var minifyCSS = require('gulp-minify-css')
var coffee = require('gulp-coffee');
var exec = require('child_process').exec;
var sys = require('sys');

kevin-smets

Default

Powerlevel10k

rrosiek

#! /usr/bin/env bash

###
#
# install_mysql.sh
#
# This script assumes your Vagrantfile has been configured to map the root of
# your application to /vagrant and that your web root is the "public" folder
# (Laravel standard).  Standard and error output is sent to
# /vagrant/vm_build.log during provisioning.

fideloper

#!/usr/bin/env bash

echo ">>> Starting Install Script"

# Update
sudo apt-get update

# Install MySQL without prompt
sudo debconf-set-selections <<< 'mysql-server mysql-server/root_password password root'
sudo debconf-set-selections <<< 'mysql-server mysql-server/root_password_again password root'

possibilities

From Meteor's documentation:

In Meteor, your server code runs in a single thread per request, not in the asynchronous callback style typical of Node. We find the linear execution model a better fit for the typical server code in a Meteor application.

This guide serves as a mini-tour of tools, trix and patterns that can be used to run async code in Meteor.

Basic async

Sometimes we need to run async code in Meteor.methods. For this we create a Future to block until the async code has finished. This pattern can be seen all over Meteor's own codebase:

johnantoni

username: vagrant
password: vagrant

sudo apt-get update
sudo apt-get install build-essential zlib1g-dev git-core sqlite3 libsqlite3-dev
sudo aptitude install mysql-server mysql-client


sudo nano /etc/mysql/my.cnf