Rodrigo Maia rodrimaia

## keybase.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                rodrimaia
                / keybase.md
            
            
              Last active
              March 21, 2022 13:10
            
          
    Keybase proof

I hereby claim:

I am rodrimaia on github.
I am rodrigomaia17 (https://keybase.io/rodrigomaia17) on keybase.
I have a public key whose fingerprint is A51D 5E74 E059 A4F5 05AE  2A41 5ADC 6583 42AC AF23

To claim this, I am signing this object:

  
## svg example using vue.js
<html>
  <head>
  </head>
  <body>
    <div id="app">
      <div>
        <label> first vector   </label><input type="number" v-model="vector1" >
        <label> second vector   </label><input type="number" v-model="vector2" >
      </div>
      <svg width="600px" height="600px">

## osx-for-hackers.sh
#!/usr/bin/env bash

# ~/.macos — https://mths.be/macos

# Close any open System Preferences panes, to prevent them from overriding
# settings we’re about to change
osascript -e 'tell application "System Preferences" to quit'

# Ask for the administrator password upfront
sudo -v

## .myAlias
alias myhistory="history | awk '{CMD[\$2]++;count++;}END { for (a in CMD)print CMD[a] \" \" CMD[a]/count*100 \"% \" a;}' | grep -v \"./\" | column -c3 -s \" \" -t | sort -nr | nl |  head -n10"

## gist:637641c4438db9af88b9
history | awk '{CMD[$2]++;count++;}END { for (a in CMD)print CMD[a] " " CMD[a]/count*100 "% " a;}' | grep -v "./" | column -c3 -s " " -t | sort -nr | nl |  head -n10

## gist:ea2e6a4ffef3b4f3a51f
# Git Feature Branch Workflow
This .md was created in order to set a flow when commiting codes. As the team is growing everyday I found it useful to everyone that we had some steps to follow and don't let the code break into a thousand of conflicts that could fade away some parts of code and something else. It is also a complementing to [CONTRIBUTING.md](CONTRIBUTING.md)

So here we have the suggested steps, but feel free to suggest somthing different you didn't agree or thing we could improve.

##When developing a new feature

When a new feature starts to be implemented, you should create a new branch with your name (optional) followed by the feature name you think should be good. But before that, you should keep your ```master``` up-to-date.

So, go to your ```master```branch and synchronize with the remote repository as follow:

## .bash_profile
# USE IF YOU HAVE
#export JAVA15_HOME="/System/Library/Java/JavaVirtualMachines/1.5.0/Contents/Home/"
#export PATH=${JAVA15_HOME}/bin:$PATH
#export JAVA_HOME=$(/usr/libexec/java_home)
#export PATH=${JAVA_HOME}/bin:$PATH
#export MAVEN_OPTS="-Xmx1024m -Xms1024m -XX:MaxPermSize=1162m"
#export M2_HOME=/usr/local/apache-maven-2.2.1
#export M2=$M2_HOME/bin
#export PATH=$M2:$PATH

## gist:8e038c6c42c7afe50424
msbuild Web.csproj /P:DeployIisAppPath="Default Web Site"  /P:Configuration=Release /P:Platform="AnyCPU"   /P:DeployOnBuild=True   /P:DeployTarget=MSDeployPublish   /P:MsDeployServiceUrl=https://xxxx/MsDeploy.axd   /P:AllowUntrustedCertificate=True   /P:MSDeployPublishMethod=WMSvc   /P:CreatePackageOnPublish=True   /P:UserName=xx\xxxx    /P:Password=xxxxx

## gist:0dfe7e95c4c7ec8de1e7
Para armazenar credenciais:
git config credential.helper store


Para remover credenciais:
git config --unset credential.helper

## gist:6353dad5947deef36305
[color]
    diff = auto
    status = auto
[color "diff"]
    meta = yellow bold
    frag = magenta bold
    old = red bold
    new = green bold
[color "status"]
    added = cyan bold
	<html>
	<head>
	</head>
	<body>
	<div id="app">
	<div>
	<label> first vector </label><input type="number" v-model="vector1" >
	<label> second vector </label><input type="number" v-model="vector2" >
	</div>
	<svg width="600px" height="600px">
	#!/usr/bin/env bash

	# ~/.macos — https://mths.be/macos

	# Close any open System Preferences panes, to prevent them from overriding
	# settings we’re about to change
	osascript -e 'tell application "System Preferences" to quit'

	# Ask for the administrator password upfront
	sudo -v
	# Git Feature Branch Workflow
	This .md was created in order to set a flow when commiting codes. As the team is growing everyday I found it useful to everyone that we had some steps to follow and don't let the code break into a thousand of conflicts that could fade away some parts of code and something else. It is also a complementing to [CONTRIBUTING.md](CONTRIBUTING.md)

	So here we have the suggested steps, but feel free to suggest somthing different you didn't agree or thing we could improve.

	##When developing a new feature

	When a new feature starts to be implemented, you should create a new branch with your name (optional) followed by the feature name you think should be good. But before that, you should keep your ```master``` up-to-date.

	So, go to your ```master```branch and synchronize with the remote repository as follow:
	# USE IF YOU HAVE
	#export JAVA15_HOME="/System/Library/Java/JavaVirtualMachines/1.5.0/Contents/Home/"
	#export PATH=${JAVA15_HOME}/bin:$PATH
	#export JAVA_HOME=$(/usr/libexec/java_home)
	#export PATH=${JAVA_HOME}/bin:$PATH
	#export MAVEN_OPTS="-Xmx1024m -Xms1024m -XX:MaxPermSize=1162m"
	#export M2_HOME=/usr/local/apache-maven-2.2.1
	#export M2=$M2_HOME/bin
	#export PATH=$M2:$PATH
	Para armazenar credenciais:
	git config credential.helper store


	Para remover credenciais:
	git config --unset credential.helper
	[color]
	diff = auto
	status = auto
	[color "diff"]
	meta = yellow bold
	frag = magenta bold
	old = red bold
	new = green bold
	[color "status"]
	added = cyan bold