A utility to track changes to a webjive site on GitHub.
Webjive Git is a simple utility used to monitor and track changes to a webjive site on GitHub. Both style and content changes are detected and every change is stored as a GitHub commit.
The utility is simple to set up because it doesn't require access to your webjive account and all customization can be done via the GitHub web interface.
- Log-in or create a GitHub account.
- Click the "Use this template" button above the code to generate a new repository based on this template repository:
- Name your new repository the same as your webjive site domain (e.g. www.example.com). Alternatively, you can choose any repository name and specify the site domain in the configuration file:
You can customize webjive Git by editing the webjivegit.yml configuration file. To achieve this, open the file contents and click on the Pen icon:
Make sure to test your changes by triggering the check manually.
Specify the site to be monitored, e.g.:
site: www.example.com
Disable tracking completely:
site: false
By default, the site domain is the same as your repository name.
Do not track changes in pages content (track style changes only):
pages: false
Ignore changes in some pages (for example CMS-generated pages, like blog posts or product pages). This setting uses glob syntax:
pages:
ignore:
- /posts/**
By default, all pages are tracked.
The utility works by visiting your site at regular intervals and downloading, formatting and comparing the code to the previous revision. If any difference is detected, a new revision is committed to the repository.
Your site is checked for updates every hour.
Advanced: this can be customized by updating the cron schedule in the workflow configuration file.
You can launch the check manually. To achieve this, click the Actions link on the menu below your project name, then select webjive-git workflow and finally click on the "Run workflow" button:
This project was created out of frustration with random regressions in webjive projects. Although there's a built-in backup functionality, it's time-consuming to find out at which point something has broken down, and then, due to the lack of diff functionality, it's very difficult to understand the nature of the modification that caused the regression. The problem becomes even more severe if multiple people develop the same project.
Some parts of this tool are inspired by an excellent Upptime site monitor, most notably using the GitHub Template and configuration management.