100%

DocPad: rsync Deploy Script

✓ Published0🌍 Public

Last edited Jun 18, 2013

Created on Jun 18, 2013

This example shows a shell script that automates deploying a static website via rsync to a remote server. It defines environment variables for the source directory, destination directory, server, and account, then runs `docpad generate` to build the site before syncing files. The script supports a dry-run mode with the `-n` flag and excludes specified patterns like `.git` and `.svn` using a `.deployignore` file. It relies on the `rsync` command-line tool and the `docpad` static site generator, with the deployment target specified as a user@host:path.

AI-generated description

DocPad: rsync Deploy Script

Place deploy.sh in {docpad folder}/bin/
Create (or edit) a .env file in your docpad folder with the following values:

#!/bin/bash
DEPLOY_SOURCE_DIR="out/"
DEPLOY_DEST_DIR="~/public_html/"
DEPLOY_SERVER=deploy-server-name
DEPLOY_ACCOUNT=deploy-login-name

Create a .deployignore file in docpad folder with the following values:

**.svn
.git
.gitignore

Test with ./bin/deploy.sh -n deploy with./bin/deploy.sh

Similar vizzes

Loading thumbnail…

DocPad is great.... but so is Grunt. Use grunt-contrib-connect and grunt-contrib-watch instead of docpad's server and watcher.

This example shows a Grunt-based build workflow that replaces DocPad’s built-in server and watcher with grunt-contrib-connect and grunt-contrib-watch, enabling live-reload during static site generation. The configuration defines a `docpad` task that watches `src/**/*.*` files and triggers a shell command to regenerate output into the `out` directory, while a separate watch task monitors `out/**/*` for live-reload. The `connect` server serves the generated `out` folder on port 9778 with livereload enabled, and tasks like `generate`, `server`, and `run` orchestrate clean builds and continuous development. The code relies on Grunt’s task registry, `grunt-shell`, `grunt-contrib-watch`, `grunt-contrib-connect`, and `grunt-contrib-clean` to handle file watching, HTTP serving, and cleanup.

HHypercubed

62% match

Loading thumbnail…

Drafting and publishing a blog post (in docpad) using [frontman](https://github.com/Hypercubed/frontman)

This example demonstrates how to draft and publish a blog post using the frontman command-line tool within a DocPad project. It shows the workflow of creating a new post from a draft template and then publishing it to a dated archive directory. The code uses frontman’s `new` and publish commands, with CSON configuration files (`draft_post.cson` and `publish_post.cson`) that specify metadata like layout, status, and output directories. The publish template dynamically computes the current date to set the post’s `date` field and target folder, while the draft template defaults to a `draft` status and `src/drafts/` output.

HHypercubed

55% match

Loading thumbnail…

Gist 20b9219bcfa5ee87411a30118d3b6163

This example shows a shell script that automates the deployment of a Dockerized application on a fresh Ubuntu server. The script installs Docker and Docker Compose, creates a project directory, and copies a `docker-compose.yml` file into it. It then sets up a systemd service to run the compose file on boot and starts the application. The code uses `curl` to fetch remote files, `usermod` for user permissions, and `systemctl` to enable the service, with the actual container orchestration handled by `docker-compose` and `docker` commands.

CCliffordAnderson

51% match

Loading thumbnail…

A simple script to backup an organization's GitHub repositories, wikis and issues.

This example demonstrates a Bash script that automates the backup of an organization's GitHub repositories, wikis, and issues, using the GitHub API to fetch repository lists and `git clone --mirror` for repository backups. The script produces compressed archives via `tar`, while `curl` retrieves issue data. The backup process includes pruning of old archives, configured through shell variables and conditional checks.

JJustinGOSSES

48% match

Loading thumbnail…

A simple script to backup an organization's GitHub repositories, wikis and issues.

JJustinGOSSES

48% match

Loading thumbnail…

Gist 109228

This example visualizes a custom workflow for managing development environment variables through a shell script. It shows how the script scans a directory for subdirectories, extracts their names, and dynamically sets environment variables pointing to those paths. The code uses standard Unix command-line tools like `ls`, `awk`, and shell `for` loops, along with `export` to define variables such as `dev` and `devwork`. No external visualization libraries are present; instead, the focus is on text-based configuration logic, with the output being variable assignments rather than graphical rendering. The data source is the local file system under `/Users/dylanfm/Development`.

DDylanFM

48% match

Loading thumbnail…

The Gist to Clone All Gists

This example demonstrates a practical workflow for backing up or synchronizing a GitHub user’s public gists. It first clones every gist from a specified GitHub account over SSH, using a paginated API fetch to retrieve the list of gists and the Node.js `https` module to authenticate via an OAuth token. It then shows a complementary bash script that iterates through local directories, committing any changes with an empty message and pushing them back to their remote origins. The visualization highlights the interplay between the GitHub REST API and command-line Git operations for batch repository management.

Mmbostock

48% match

Loading thumbnail…

Gist 39225

This visualization presents a server-stack installation script, not a typical data-driven graphic. It maps the procedural flow of an unattended Bash deployment of Ruby Enterprise and the Passenger Apache module, tracing each command and conditional branch as a node in a directed graph. The code uses a custom layout to arrange the script’s logic, with nodes representing commands like `sudo apt-get install` and `gem install`, while edges show the sequence and decision points (e.g., `if [ -e $REEF ]`). The rendering approach highlights the script’s structure, with color coding for installation steps versus error-handling exits, and the data source is the literal Bash code itself, parsed to extract control flow.

DDylanFM

47% match