Lucas Brum sistematico

Fixing the “GH001: Large files detected. You may want to try Git Large File Storage.”

I just migrated my repositories from BitBucket to GitHub but, suddenly, I received an interesting error when I tried to push a repo with some large files inside.

remote: error: GH001: Large files detected. You may want to try Git Large File Storage — https://git-lfs.github.com.
remote: error: Trace: b5116d865251981c96d4b32cdf7ef464
remote: error: See http://git.io/iEPt8g for more information.
remote: error: File fixtures/11_user_answer.json is 131.37 MB; this exceeds GitHub’s file size limit of 100.00 MB

These are my notes on how I got all the basics working end to end.

Laravel API backend and Vue.js frontend are 2 different servers on different public IP addresses and different domains. I am using pure Vue.js on the front end. Most instructions assume Laravel Vue.js is being used which is structured slightly different with different file names and directories.

Laravel API backend domain name (api.somedomain.com)
Vue.js frontend domain name (client.somedomain.com)

No database is needed for any of this to work using sync queue. That is only needed in production if/when you use a database queue.

Node.js Deployment

Steps to deploy a Node.js app to DigitalOcean using PM2, NGINX as a reverse proxy and an SSL from LetsEncrypt

1. Sign up for Digital Ocean

If you use the referal link below, you get $10 free (1 or 2 months) https://m.do.co/c/5424d440c63a

2. Create a droplet and log in via ssh

I will be using the root user, but would suggest creating a new user

Tailwind CSS best practices

Utility classes

When writing a string of multiple utility classes, always do so in an order with meaning. The "Concentric CSS" approach works well with utility classes (i.e,. 1. positioning/visibility 2. box model 3. borders 4. backgrounds 5. typography 6. other visual adjustments). Once you establish a familiar pattern of ordering, parsing through long strings of utility classes will become much, much faster so a little more effort up front goes a long way!
Always use fewer utility classes when possible. For example, use mx-2 instead of ml-2 mr-2 and don't be afraid to use the simpler p-4 lg:pt-8 instead of the longer, more complicated pt-4 lg:pt-8 pr-4 pb-4 pl-4.
Prefix all utility classes that will only apply at a certain breakpoint with that breakpoint's prefix. For example, use block lg:flex lg:flex-col lg:justify-center instead of block lg:flex flex-col justify-center to make it very clear that the flexbox utilities are only applicable at the

	// Vídeo do código: https://youtu.be/Eeqyi6W4CqY

	const fs = require('fs');
	const path = require('path');

	var raiz = './arquivos';
	var data = {};
	var aux = 0;

	function listarArquivos(base) {


	export { EMoonPhase, EMoonPhaseName, MOON_PHASE_NAMES, moonPhase }


	const { round, trunc: truncate } = Math


	enum EMoonPhase {
	New = 0,
	WaxingCrescent,

	[
	{
	"value": 1,
	"first": "bar",
	"second": "bar",
	"third": "bar"
	},
	{
	"value": 2,
	"first": "grape",

	name: Deploy

	on:
	push:
	branches:
	- production

	jobs:
	deploy:
	runs-on: ubuntu-latest

	import asyncio
	from datetime import datetime
	from functools import partial
	from concurrent.futures import ProcessPoolExecutor

	from youtube_dl import YoutubeDL as YDL

	PPE = ProcessPoolExecutor()

	#!/usr/bin/env bash
	# -- indent-tabs-mode: nil; tab-width: 4 --
	#
	# An ugly way to bind extra mouse buttons under GNOME/Wayland or otherwise.
	#
	# Prerequisites:
	#
	# Effectively unbind extra mouse buttons by modifying udev/hwdb rules:
	# 1. Identify scancodes:
	# sudo evemu-record /dev/input/by-path/*event-mouse \