Example FTW
This commit is contained in:
parent
29ef18828a
commit
4abd93567f
|
@ -4,10 +4,10 @@ Feature: Site data
|
||||||
In order to make the site slightly dynamic
|
In order to make the site slightly dynamic
|
||||||
|
|
||||||
Scenario: Use page variable in a page
|
Scenario: Use page variable in a page
|
||||||
Given I have an "contact.html" page with title "Contact" that contains "{{ page.title }}: email@me.com"
|
Given I have an "contact.html" page with title "Contact" that contains "{{ page.title }}: email@example.com"
|
||||||
When I run jekyll
|
When I run jekyll
|
||||||
Then the _site directory should exist
|
Then the _site directory should exist
|
||||||
And I should see "Contact: email@me.com" in "_site/contact.html"
|
And I should see "Contact: email@example.com" in "_site/contact.html"
|
||||||
|
|
||||||
Scenario Outline: Use page.path variable in a page
|
Scenario Outline: Use page.path variable in a page
|
||||||
Given I have a <dir> directory
|
Given I have a <dir> directory
|
||||||
|
@ -95,10 +95,10 @@ Feature: Site data
|
||||||
|
|
||||||
Scenario: Use configuration date in site payload
|
Scenario: Use configuration date in site payload
|
||||||
Given I have an "index.html" page that contains "{{ site.url }}"
|
Given I have an "index.html" page that contains "{{ site.url }}"
|
||||||
And I have a configuration file with "url" set to "http://mysite.com"
|
And I have a configuration file with "url" set to "http://example.com"
|
||||||
When I run jekyll
|
When I run jekyll
|
||||||
Then the _site directory should exist
|
Then the _site directory should exist
|
||||||
And I should see "http://mysite.com" in "_site/index.html"
|
And I should see "http://example.com" in "_site/index.html"
|
||||||
|
|
||||||
Scenario: Access Jekyll version via jekyll.version
|
Scenario: Access Jekyll version via jekyll.version
|
||||||
Given I have an "index.html" page that contains "{{ jekyll.version }}"
|
Given I have an "index.html" page that contains "{{ jekyll.version }}"
|
||||||
|
|
|
@ -37,7 +37,7 @@ this](http://web.archive.org/web/20091223025644/http://www.taknado.com/en/2009/0
|
||||||
To have a remote server handle the deploy for you every time you push changes using Git, you can create a user account which has all the public keys that are authorized to deploy in its `authorized_keys` file. With that in place, setting up the post-receive hook is done as follows:
|
To have a remote server handle the deploy for you every time you push changes using Git, you can create a user account which has all the public keys that are authorized to deploy in its `authorized_keys` file. With that in place, setting up the post-receive hook is done as follows:
|
||||||
|
|
||||||
{% highlight bash %}
|
{% highlight bash %}
|
||||||
laptop$ ssh deployer@myserver.com
|
laptop$ ssh deployer@example.com
|
||||||
server$ mkdir myrepo.git
|
server$ mkdir myrepo.git
|
||||||
server$ cd myrepo.git
|
server$ cd myrepo.git
|
||||||
server$ git --bare init
|
server$ git --bare init
|
||||||
|
@ -63,7 +63,7 @@ Finally, run the following command on any users laptop that needs to be able to
|
||||||
deploy using this hook:
|
deploy using this hook:
|
||||||
|
|
||||||
{% highlight bash %}
|
{% highlight bash %}
|
||||||
laptops$ git remote add deploy deployer@myserver.com:~/myrepo.git
|
laptops$ git remote add deploy deployer@example.com:~/myrepo.git
|
||||||
{% endhighlight %}
|
{% endhighlight %}
|
||||||
|
|
||||||
Deploying is now as easy as telling nginx or Apache to look at
|
Deploying is now as easy as telling nginx or Apache to look at
|
||||||
|
|
Loading…
Reference in New Issue