Florian FlorianBouron

## multiple-deploy-keys-multiple-private-repos-github-ssh-config.md

      
              1 file
            
          
              4 forks
            
          
              4 comments
            
          
              14 stars
            
          
                FlorianBouron
                / multiple-deploy-keys-multiple-private-repos-github-ssh-config.md
            
            
              Last active
              April 6, 2023 16:55
            
              
                How to configure multiple deploy keys for different private github repositories on the same computer
              
          
    This is probably a common issue for people who wants to deploy serveral repository on one VPS or VM.
This is not going to be rocket science.
The first step is to generate your first ssh key, for this type the following command line in your terminal:
ssh-keygen -t rsa -b 4096 -C "your@email.com"
When the command CLI is asking you if you want to use a passphrase you might want to press ENTER in order to don't have to type it everytime you will want to pull your repository.
Now copy the content of your public key and add it to Github in your first repository (Settings > Deploy keys).
For example on debian it might be:

  
## .htaccess
<IfModule mod_rewrite.c>

  RewriteEngine On
  RewriteBase /
  RewriteRule ^index\.html$ - [L]
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteCond %{REQUEST_FILENAME} !-l
  RewriteRule . /index.html [L]

## git-deployment.md

      
              2 files
            
          
              306 forks
            
          
              86 comments
            
          
              1183 stars
            
          
                noelboss
                / git-deployment.md
            
            
              Last active
              May 16, 2024 20:41
            
              
                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.

  
## cheatsheet-git.sh
# adding and committing
git add -A                        # stages All
git add .                         # stages new and modified, without deleted
git add -u                        # stages modified and deleted, without new
git commit --amend                # Add staged changes to previous commit. Do not use if commit has been pushed.
git commit --amend --no-edit      # Do so without having to edit the commit message.

# remotes - pushing, pulling, and tracking
git fetch                         # gets remote objects and refs. Needed if new branches were added on the remote.
git remote -v                     # Lists all remotes (verbose)

## gist:2999707
<!doctype html>
<title>Site Maintenance</title>
<style>
  body { text-align: center; padding: 150px; }
  h1 { font-size: 50px; }
  body { font: 20px Helvetica, sans-serif; color: #333; }
  article { display: block; text-align: left; width: 650px; margin: 0 auto; }
  a { color: #dc8100; text-decoration: none; }
  a:hover { color: #333; text-decoration: none; }
</style>
	<IfModule mod_rewrite.c>

	RewriteEngine On
	RewriteBase /
	RewriteRule ^index\.html$ - [L]
	RewriteCond %{REQUEST_FILENAME} !-f
	RewriteCond %{REQUEST_FILENAME} !-d
	RewriteCond %{REQUEST_FILENAME} !-l
	RewriteRule . /index.html [L]
	# adding and committing
	git add -A # stages All
	git add . # stages new and modified, without deleted
	git add -u # stages modified and deleted, without new
	git commit --amend # Add staged changes to previous commit. Do not use if commit has been pushed.
	git commit --amend --no-edit # Do so without having to edit the commit message.

	# remotes - pushing, pulling, and tracking
	git fetch # gets remote objects and refs. Needed if new branches were added on the remote.
	git remote -v # Lists all remotes (verbose)
	<!doctype html>
	<title>Site Maintenance</title>
	<style>
	body { text-align: center; padding: 150px; }
	h1 { font-size: 50px; }
	body { font: 20px Helvetica, sans-serif; color: #333; }
	article { display: block; text-align: left; width: 650px; margin: 0 auto; }
	a { color: #dc8100; text-decoration: none; }
	a:hover { color: #333; text-decoration: none; }
	</style>