wiki:pushing_changes_to_red

What is Red

Red is a server management web interface written by Jamie McClelland. It allows privileged users the ability to modify many settings through a web UI, including apache server configurations, domain names, installing Drupal, email accounts, etc. Red seeks to increase configuration flexibility while reducing the complexity of server management by creating an easy-to-use and -understand interface.

It provides the code behind https://members.mayfirst.org/cp , and many of the other systems that hook into it.

The Red Repository

The canonical location for red's source code is an SVN repository, accessible at mfpl@svn.mayfirst.org/trunk/red

Using git-svn

If you prefer to use git for local revision control tracking, you can still talk to the SVN repo using git-svn

  • Clone the svn repository to a git-svn branch:
    git svn clone svn+ssh://mfpl@svn.mayfirst.org/trunk/red
    
  • Update your local git repo's view of the svn repository:
    git svn fetch
    
  • If you have made edits, and the canonical svn repository has changed in the meantime, merge your edits with the current SVN head:
    git svn rebase
    
  • Committing Changes: In order to commit changes using git-svn:
    1. start with a standard:
      git commit
      
    2. push your changes to the canonical svn repository:
      git svn dcommit
      

Making Changes Live

There are two steps to take for making changes live.

Tag the committed changes

In order to tag changes to red, you must be in the top level red directory and issue the following command:

./svn-create-next-tag

Updating the live Control Panel

After tagging the committed changes cd into the mfpl-servers repository to mfpl-servers/admin/scripts and issue the following command:

./execute-directive harry ../directives/red-update/

Assuming no error messages, your changes should be live.

Last modified 9 years ago Last modified on Dec 15, 2010, 4:05:35 PM