Git Deployment - Revision history

Admin at 08:34, 29 April 2018

2018-04-29T08:34:52Z

← Older revision		Revision as of 08:34, 29 April 2018
Line 35:		Line 35:
	</pre>		</pre>

			==Webhooks==

			You can add these to webhook scripts, as with Captain Hook.

			* Captain Hook documentation: https://pages.charlesreid1.com/b-captain-hook
			* Captain Hook source code: https://git.charlesreid1.com/bots/b-captain-hook

			==Flags==

	[[Category:Git]]		[[Category:Git]]

Admin at 08:33, 29 April 2018

2018-04-29T08:33:48Z

← Older revision		Revision as of 08:33, 29 April 2018
Line 3:		Line 3:
	* Use the <code>gh-pages</code> branch to hold all of the web content		* Use the <code>gh-pages</code> branch to hold all of the web content
	* Use the <code>master</code> or <code>source</code> branch to hold the files needed to generate the static content		* Use the <code>master</code> or <code>source</code> branch to hold the files needed to generate the static content

			==New Deployment==

	When you have content on your <code>gh-pages</code> branch, deploy it on your live machine using the following git clone command:		When you have content on your <code>gh-pages</code> branch, deploy it on your live machine using the following git clone command:
Line 24:		Line 26:

	I also like to clone a copy of the source next to htdocs and git, so that <code>/www/example.com/example.com-src</code> is a copy of the master or source branch.		I also like to clone a copy of the source next to htdocs and git, so that <code>/www/example.com/example.com-src</code> is a copy of the master or source branch.

			==Pulling Existing Deployment==

			Once you've updated content on the <code>gh-pages</code> branch, you can run git pull in the same manner as the git clone command above (that is, specifying a different git and working directory). However, the syntax looks different:

			<pre>
			git -C /www/example.com --git-dir=git --work-tree=htdocs pull origin gh-pages
			</pre>


	[[Category:Git]]		[[Category:Git]]

Admin: Created page with "To use git for static content deployment: * Use the `gh-pages` branch to hold all of the web content * Use the `master` or `source` branch to..."

2018-04-26T12:54:04Z

Created page with "To use git for static content deployment: * Use the <code>gh-pages</code> branch to hold all of the web content * Use the <code>master</code> or <code>source</code> branch to..."

New page

To use git for static content deployment:

* Use the <code>gh-pages</code> branch to hold all of the web content
* Use the <code>master</code> or <code>source</code> branch to hold the files needed to generate the static content

When you have content on your <code>gh-pages</code> branch, deploy it on your live machine using the following git clone command:

<pre>
git -C /www/example.com clone --separate-git-dir=git -b gh-pages <git-repo-url> htdocs
</pre>

This will create the following directory structure:

<pre>
/www/example.com/
htdocs/
index.html
...
git/
...
</pre>

This keeps your .git out of your htdocs directory.

I also like to clone a copy of the source next to htdocs and git, so that <code>/www/example.com/example.com-src</code> is a copy of the master or source branch.

[[Category:Git]]
[[Category:Web]]
[[Category:Static Content]]
[[Category:Github]]

Git Deployment - Revision history

Admin at 08:34, 29 April 2018

Admin at 08:33, 29 April 2018

Admin: Created page with "To use git for static content deployment: * Use the gh-pages branch to hold all of the web content * Use the master or source branch to..."

Admin: Created page with "To use git for static content deployment: * Use the `gh-pages` branch to hold all of the web content * Use the `master` or `source` branch to..."