[DEPRECATED, see blogc] A simple login shell/git hook to deploy blogc websites.
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
build-aux
m4
squareball @ e2639b0
.gitignore
.gitmodules
.travis.yml
LICENSE
Makefile.am
README.md
autogen.sh
blogc-git-receiver.c
blogc-git-receiver.spec.in
configure.ac

README.md

blogc-git-receiver

Build Status

A simple login shell/git hook to deploy blogc websites.

blogc-git-receiver provides a PaaS-like way to deploy your blogc websites. When used as a login shell, it will accept git payloads, creating bare repositories as needed, and installing a hook, that will take care of building your website each time you push something to the master branch.

The git repository must provide a Makefile (or a GNUMakefile), that should accept the OUTPUT_DIR variable, and install built files in the directory pointed by this variable.

blogc-git-receiver is part of blogc project, but isn't tied to blogc. Any repository with Makefile that builds content and install it to OUTPUT_DIR should works with blogc-git-receiver.

Example setup

Download a release tarball, extract it and enter its directory, after that run the following commands:

$ ./configure
$ make
# make install

If you ran ./configure without --prefix, your binary will be installed to /usr/local/bin/blogc-git-receiver. Now you must create a new user, using this shell.

# useradd -m -s /usr/local/bin/blogc-git-receiver blogc

Users installing blogc-git-receiver from distribution packages must use the following command, because the binary is installed directly in /usr/bin:

# useradd -m -s /usr/bin/blogc-git-receiver blogc

Now you can add your ssh keys to /home/blogc/.ssh/authorized_keys. Also, make sure to install all the dependencies required by your websites, including a web server. blogc-git-receiver won't handle your web server virtual hosts, at least for now.

To deploy a website (e.g. our example repository):

$ git clone https://github.com/blogc/blogc-example.git
$ cd blogc-example
$ git remote add blogc blogc@${SERVER_IP}:blogs/blogc-example.git
$ git push blogc master

This will deploy the example to the remote server, creating a symlink to your built content in /home/blogc/repos/blogs/blogc-example.git/htdocs, you just need to point the web server to this symlink, configure your rewrite rules, if needed, and you're done.

How to install on Fedora 22/23, with packages from Copr and SELinux enabled

Supposing that you'll use nginx as your webserver, running with the nginx user:

# dnf copr enable -y rafaelmartins/blogc
# dnf install -y blogc blogc-git-receiver nginx policycoreutils-python-utils
# useradd -m -s /usr/bin/blogc-git-receiver blogc
# gpasswd -a nginx blogc
# chmod -R g+rx /home/blogc
# su -c "mkdir /home/blogc/{builds,repos}" -s /bin/sh blogc
# semanage fcontext -a -t httpd_sys_content_t "/home/blogc/(builds|repos)(/.*)?"
# restorecon -R -v /home/blogc
# systemctl restart nginx

Now feel free to install an editor, fix nginx settings and start pushing your blogs!

Repository mirroring

Users can rely on blogc-git-receiver to mirror their repositories to a remote Git repository (e.g. a free Bitbucket private repository). This feature just requires adding a remote called mirror to the bare repository in your server. If such remote exists, blogc-git-receiver will git push --mirror to it. Please note that the blogc user must be able to push to the remote repository, and that any content manually pushed to the remote repository is overwritten by blogc-git-receiver.

Some reasonable ways to allow the blogc user to push to the remote repository are:

  • Create a password-less SSH key. The key must be password-less, because the push is automatic, and remote git hooks can't be interactive.
  • Create an oauth token in the hosting service (if it supports oauth authentication in git, e.g. GitHub) and add it to the git URL.

The mirroring feature wont't block a git push, it will just raise warnings. That means that if an error happens when mirroring the repository, your deploy will still succeed. Please pay attention to the git hook logs, to avoid losing data because your repositories are not being mirrored. ;)

To add the remote, run the following commands inside the blog bare repository in the server:

# su -s /bin/bash - blogc
$ git remote add --mirror=push mirror $YOUR_GIT_MIRROR_URL

Caveats of repository mirroring with SSH

As said before, the authentication must be done with a password-less SSH key created by the blogc user when mirroring the repository with SSH.

As the git push --mirror call is automated, you must disable SSH strict host checking in SSH ~/.ssh/config file:

Host bitbucket.org
    StrictHostKeyChecking no

Please replace bitbucket.org with the Git base URL of your hosting provider.

To change this file, you must login with /bin/bash or any other "real" shell, as root:

# su -s /bin/bash - blogc

Running specific code when deploying with blogc-git-receiver

This tool will export an environment variable called BLOGC_GIT_RECEIVER when calling gmake to build your site. You can use it to enable building of content that should only be built when running in production environment.


If some unexpected error happened, please file an issue.

-- Rafael G. Martins rafael@rafaelmartins.eng.br