octopress 3.0.8 → 3.0.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/CHANGELOG.md +4 -1
- data/README.md +30 -41
- data/lib/octopress/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 8a5d0577a968b736c201077dd3281c29361321ff
|
4
|
+
data.tar.gz: 3b5cec2f08534bfd66241977774ec3a3417af2c7
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 694d83bed6d87a03ac481e5bbd7c9ac1fce8e27f8c168dafe2735ebf1b25a246d806dfcace2fa1aed3bf4abe80a95f9633b2067bad23089abcbc6ccadeacf6aa
|
7
|
+
data.tar.gz: 2ff09c7cc7bcd5c66f9797392b3c80421cab42965cad8adcb4dc51600a6482f2b88e2220c044d9a6501ddd364cd9c9663a6339fbec36189255c119eb0e1f9331
|
data/CHANGELOG.md
CHANGED
data/README.md
CHANGED
@@ -184,7 +184,7 @@ $ octopress unpublish some post
|
|
184
184
|
Just like the publish command, you can either pass a path or a search string to match the file name. If more than one match is found, you
|
185
185
|
will be prompted to select from a menu of posts.
|
186
186
|
|
187
|
-
|
187
|
+
#### Templates for Posts and pages
|
188
188
|
|
189
189
|
Octopress post and page templates look like this.
|
190
190
|
|
@@ -245,10 +245,20 @@ $ octopress isolate kittens # Move post matching search
|
|
245
245
|
|
246
246
|
In the third example, if multiple posts match the search a prompt will ask you to select a post from a menu.
|
247
247
|
|
248
|
-
###
|
248
|
+
### Deploying your site
|
249
249
|
|
250
250
|
The Octopress gem comes with [octopress-deploy](https://github.com/octopress/deploy) which allows you to easily deploy your site with Rsync, on S3 or Cloudfront, to GitHub pages, or other Git based deployment hosting platforms.
|
251
251
|
|
252
|
+
Once you've built your site (with `jekyll build`) you can deploy it like this:
|
253
|
+
|
254
|
+
```
|
255
|
+
$ octopress deploy
|
256
|
+
```
|
257
|
+
|
258
|
+
This reads a `_deploy.yml` configuration and deploys your site. Read below to learn how Octopress can generate a deployment configuration file for you.
|
259
|
+
|
260
|
+
Deploy has a few commands you should know.
|
261
|
+
|
252
262
|
| Commands | Description |
|
253
263
|
|:-------------------------------------------|:-------------------------------------------------------------------|
|
254
264
|
| `octopress deploy` | Deploy your site (based on the `_deploy.yml` configuration) |
|
@@ -256,20 +266,22 @@ The Octopress gem comes with [octopress-deploy](https://github.com/octopress/dep
|
|
256
266
|
| `octopress deploy pull [DIR]` | Pull down your site into a local directory. |
|
257
267
|
| `octopress deploy add-bucket <NAME>` | (S3 only) Add a bucket using your configured S3 credentials. |
|
258
268
|
|
259
|
-
#### Deploy configuration
|
260
269
|
|
261
|
-
|
270
|
+
#### Generate Deployment configuration
|
271
|
+
|
272
|
+
**Remember to add your configuration to `.gitignore` to be sure
|
273
|
+
you never commit sensitive information to your repository.**
|
274
|
+
|
275
|
+
|
276
|
+
Octopress can generate a deployment configuration file for you using the `octopress deploy init` command.
|
262
277
|
|
263
278
|
```
|
264
|
-
$ octopress deploy init git git@github.com:user/project
|
265
279
|
$ octopress deploy init s3
|
266
280
|
$ octopress deploy init rsync
|
281
|
+
$ octopress deploy init git git@github.com:user/project
|
267
282
|
```
|
268
283
|
|
269
|
-
This will generate a `_deploy.yml` file in your current
|
270
|
-
directory which you can edit to add any necessary configuration.
|
271
|
-
**Remember to add your configuration to `.gitignore` to be sure
|
272
|
-
you never commit sensitive information to your repository.**
|
284
|
+
This will generate a `_deploy.yml` file in your current directory which you can edit to add any necessary configuration.
|
273
285
|
|
274
286
|
If you like, you can pass configurations as command line options. To see specific options for any method, add the `--help` flag.
|
275
287
|
For example to see the options for configuring S3:
|
@@ -278,33 +290,19 @@ For example to see the options for configuring S3:
|
|
278
290
|
$ octopress deploy init s3 --help
|
279
291
|
```
|
280
292
|
|
281
|
-
|
282
|
-
|
283
|
-
Change the deployment configuration however you like, then build and deploy your site.
|
293
|
+
If you want to publish your site to a staging server, you can create a second configuration. For example, to setup rsync for a staging site, you'd do this.
|
284
294
|
|
285
295
|
```
|
286
|
-
$
|
287
|
-
$ octopress deploy
|
296
|
+
$ octopress deploy init rsync --config _staging.yml
|
288
297
|
```
|
289
298
|
|
290
|
-
|
291
|
-
site. If you like, you can specify a configuration file.
|
299
|
+
After modifying the configuration file, you can deploy your site to it like this:
|
292
300
|
|
293
301
|
```
|
294
302
|
$ octopress deploy --config _staging.yml
|
295
303
|
```
|
296
304
|
|
297
|
-
####
|
298
|
-
|
299
|
-
With the `pull` command, you can pull your site down into a local directory.
|
300
|
-
|
301
|
-
```
|
302
|
-
$ octopress deploy pull [DIR]
|
303
|
-
```
|
304
|
-
|
305
|
-
Mainly you'd do this if you're troubleshooting deployment and you want to see if it's working how you expected.
|
306
|
-
|
307
|
-
##### Git Deployment Configuration
|
305
|
+
#### Git Deployment Configuration
|
308
306
|
|
309
307
|
Only `git_url` is required. Other options will default as shown below.
|
310
308
|
|
@@ -317,7 +315,7 @@ Only `git_url` is required. Other options will default as shown below.
|
|
317
315
|
| `deploy_dir` | Directory where deployment files are staged | .deploy |
|
318
316
|
| `remote` | Name of git remote | deploy |
|
319
317
|
|
320
|
-
|
318
|
+
#### Rsync Deployment Configuration
|
321
319
|
|
322
320
|
| Config | Description | Default
|
323
321
|
|:---------------|:--------------------------------------------------|:---------------|
|
@@ -398,24 +396,15 @@ If you prefer, you can store AWS access credentials in environment variables ins
|
|
398
396
|
|
399
397
|
Note: configurations in `_deploy.yml` will override environment variables so be sure to remove those if you decide to use environment variables.
|
400
398
|
|
401
|
-
|
399
|
+
### Pull down your site
|
402
400
|
|
403
|
-
|
401
|
+
With the `pull` command, you can pull your site down into a local directory.
|
404
402
|
|
405
403
|
```
|
406
|
-
$ octopress deploy
|
404
|
+
$ octopress deploy pull [DIR]
|
407
405
|
```
|
408
406
|
|
409
|
-
|
410
|
-
|
411
|
-
| Option | Description | Default
|
412
|
-
|:--------------|:-------------------------------------------------|:---------------|
|
413
|
-
| `--region` | Override the `region` configuration | |
|
414
|
-
| `--index` | Specify an index page for your site | index.html |
|
415
|
-
| `--error` | Specify an error page for your site | error.html |
|
416
|
-
| `--config` | Use a custom configuration file | _deploy.yml |
|
417
|
-
|
418
|
-
You'll only need to pass options if you want to override settings in your deploy config file.
|
407
|
+
Mainly you'd do this if you're troubleshooting deployment and you want to see if it's working how you expected.
|
419
408
|
|
420
409
|
## Contributing
|
421
410
|
|
data/lib/octopress/version.rb
CHANGED