This guide on how to convert an SVN repository to a git repository was mostly taken from John Albin Wilkins post on Converting a Subversion repository to Git.
:
#!/bin/bash | |
version="0.9.4 from 2010-09-13" | |
# Always download the latest version here: http://www.eurosistems.ro/back-res | |
# Thanks or questions: http://www.howtoforge.com/forums/showthread.php?t=41609 | |
# | |
# CHANGELOG: | |
# ----------------------------------------------------------------------------- | |
# version 0.9.4 - 2010-09-13 | |
# -------------------------- | |
# Small fix: - Corrected small bug replaced tar with $TAR in the recovery line |
This guide on how to convert an SVN repository to a git repository was mostly taken from John Albin Wilkins post on Converting a Subversion repository to Git.
:
<?php | |
/* | |
Plugin Name: Disable plugins when doing local dev | |
Description: If the WP_LOCAL_DEV constant is true, disables plugins that you specify | |
Version: 0.1 | |
License: GPL version 2 or any later version | |
Author: Mark Jaquith | |
Author URI: http://coveredwebservices.com/ | |
*/ |
******************************************************************** Set up Django, Nginx and Gunicorn in a Virtualenv controled by Supervisor********************************************************************
Steps with explanations to set up a server using:
# BEGIN WordPress | |
<IfModule mod_rewrite.c> | |
RewriteEngine On | |
#RewriteBase /blog/ | |
RewriteBase /~accountname/ | |
RewriteRule ^index\.php$ - [L] | |
RewriteCond %{REQUEST_FILENAME} !-f | |
RewriteCond %{REQUEST_FILENAME} !-d | |
#RewriteRule . /blog/index.php [L] | |
RewriteRule . /~accountname/index.php [L] |
Collection of License badges for your Project's README file.
This list includes the most common open source and open data licenses.
Easily copy and paste the code under the badges into your Markdown files.
Translations: (No guarantee that the translations are up-to-date)
A clean and handy way to deal with your documentation is to exploit the GitHub Pages, which represents a nice tool to publish software documentation online.
Everything is basically done through the special branch called gh-pages
. The branch must contain at the root level the index.html file pointing to the static documentation (generally generated via doxygen) stored somewhere within the branch itself. Further, the static documentation might be composed of many products (sometimes images), thus it would be worth saving space on the repository by not retaining any history for those files.
First off, we explain how to create the infrastructure for the documentation using git and keep it up-to-date throughout the changes the code undergoes. Then, we will dig into how we can use doxygen to generate the documentation.
Let's start ✨
When setting these options consider the following:
sudo grep max_children /var/log/php?.?-fpm.log.1 /var/log/php?.?-fpm.log