Reinis Lejnieks reinislejnieks

## vue_ionic_capacitor_electron_config.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                reinislejnieks
                / vue_ionic_capacitor_electron_config.md
            
            
              Created
              June 1, 2022 19:52
                — forked from dorajistyle/vue_ionic_capacitor_electron_config.md
            
              
                Vue-Ionic-Capacitor-Electron-Config
              
          
    Predecessors

Install yarn

curl --compressed -o- -L https://yarnpkg.com/install.sh | bash
Install vue-cli

Tested @vue/cli version is 4.4.6.


## WooCommerce, Delete all products from DB
# Delete Product term relationships
DELETE
    term_relationships.*,
    term_taxonomy.*,
    terms.*
FROM wp_term_relationships AS term_relationships
INNER JOIN wp_term_taxonomy AS term_taxonomy
    ON term_relationships.term_taxonomy_id=term_taxonomy.term_taxonomy_id
INNER JOIN wp_terms AS terms
    ON term_taxonomy.term_id=terms.term_id

## git-deployment.md

      
              2 files
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                reinislejnieks
                / git-deployment.md
            
            
              Created
              February 22, 2021 19:21
                — forked from noelboss/git-deployment.md
            
              
                Simple automated GIT Deployment using Hooks
              
          
    Simple automated GIT Deployment using GIT Hooks

Here are the simple steps needed to create a deployment from your local GIT repository to a server based on this in-depth
tutorial.
How it works

You are developing in a working-copy on your local machine, lets say on the master branch. Most of the time, people would push code to a remote
server like github.com or gitlab.com and pull or export it to a production server. Or you use a service like deepl.io to act upon a Web-Hook that's triggered that service.

  
## iterm2-solarized.md

      
              2 files
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                reinislejnieks
                / iterm2-solarized.md
            
            
              Created
              January 22, 2019 17:33
                — forked from kevin-smets/iterm2-solarized.md
            
              
                iTerm2 + Oh My Zsh + Solarized color scheme + Meslo powerline font + [Powerlevel9k] - (macOS)
              
          
    Default


Powerlevel9k


## .gitconfig
[user]
	name = Pavan Kumar Sunkara
	email = pavan.sss1991@gmail.com
	username = pksunkara
[core]
	editor = vim
	whitespace = fix,-indent-with-non-tab,trailing-space,cr-at-eol
	excludesfile = ~/.gitignore
[sendemail]
	smtpencryption = tls

## .env.gitlab
APP_ENV=testing
APP_KEY=base64:DimZ0aVNA8ZWtWxTB4fDxFc6lL1wM2C7evETA4QK3+c=
APP_DEBUG=true
APP_LOG_LEVEL=debug
APP_URL=http://localhost:8081

DB_CONNECTION=mysql
DB_HOST=mysql
DB_PORT=3306
DB_DATABASE=secca_testing

## Envoy.blade.php
{{-- Define all our servers --}}
@servers(['staging' => '', 'production' => ''])

@setup
	{{-- The timezone your servers run in --}}
	$timezone = 'Europe/Amsterdam';

	{{-- The base path where your deployments are sitting --}}
	$path = '/var/www/site.com/htdocs';

## js.php
<?php

$js = <<<JS
  console.log('Hei!');
  let foo  = 'bar';
JS;

$sql = <<<SQL
  USE somedb;
  SELECT `foo`.*

## tips.js
// to log better
const a = {};
const b = {};
const c = {};

console.log('%c Something', 'color:orange; font-weight:bold;');
console.log({a, b, c});

// to log array of obj with the same props
console.table([a, b, c]);

## Working on a branch with a dependence on another branch that is being reviewed.txt
Git is very flexible. Here's one way you can do it.

Your first branch featureA is up for review.

Your second branch featureB is in development and depends on the code in the featureA branch.

Merge the featureA branch into the featureB branch.

If you make changes to the featureA branch then you should merge the featureA branch into the featureB branch again to incorporate the changes.
	[user]
	name = Pavan Kumar Sunkara
	email = pavan.sss1991@gmail.com
	username = pksunkara
	[core]
	editor = vim
	whitespace = fix,-indent-with-non-tab,trailing-space,cr-at-eol
	excludesfile = ~/.gitignore
	[sendemail]
	smtpencryption = tls
	APP_ENV=testing
	APP_KEY=base64:DimZ0aVNA8ZWtWxTB4fDxFc6lL1wM2C7evETA4QK3+c=
	APP_DEBUG=true
	APP_LOG_LEVEL=debug
	APP_URL=http://localhost:8081

	DB_CONNECTION=mysql
	DB_HOST=mysql
	DB_PORT=3306
	DB_DATABASE=secca_testing
	{{-- Define all our servers --}}
	@servers(['staging' => '', 'production' => ''])

	@setup
	{{-- The timezone your servers run in --}}
	$timezone = 'Europe/Amsterdam';

	{{-- The base path where your deployments are sitting --}}
	$path = '/var/www/site.com/htdocs';
	<?php

	$js = <<<JS
	console.log('Hei!');
	let foo = 'bar';
	JS;

	$sql = <<<SQL
	USE somedb;
	SELECT `foo`.*
	// to log better
	const a = {};
	const b = {};
	const c = {};

	console.log('%c Something', 'color:orange; font-weight:bold;');
	console.log({a, b, c});

	// to log array of obj with the same props
	console.table([a, b, c]);
	Git is very flexible. Here's one way you can do it.

	Your first branch featureA is up for review.

	Your second branch featureB is in development and depends on the code in the featureA branch.

	Merge the featureA branch into the featureB branch.

	If you make changes to the featureA branch then you should merge the featureA branch into the featureB branch again to incorporate the changes.