Difference between revisions of "CompostUs/DevTools"

OurWork

What (summary)

Get till working as a development server that we can use as part of our DevelopmentStagingProcess.

• This project and the DevelopmentStagingProcess do not apply to "hot fixes" or minor tweaks

Why this is important

We need a place where users can try out new features before they get deployed on the live site. This is important for quality control and better communication between the DevelopmentTeam and their customers.

DoneDone

• Each task is staged (with its own branch) on the development box before it gets added to the live repository
• Easy branch creation script exists
  • Create the branch in the repository on nimbus
  • Prep a branch for serving from aboutustest.org
    • Has its own database wiki_branch_name that is populated with user accounts and dev content
    • To update on till we ssh onto till and run a git pull ... all changes should show up
    • Also needs a full dedicated compost running for the branch
    • Available from branchname.till within the Portland office
• Instructions for Lahore to set up similar

Branch ... shared repository on nimbus and running instance on till in Portland and Lahore dev machine

Steps to get to DoneDone

• Figure out how to detect the operating system uname
• figure out how to quit when there isn't an argument specified test string
• Branch the aboutusbot databases too
• Clean up the scripts so that the stages are more transparent (echos) and we can do one step at a time
• Change the locations to make more sense (/www/htdocs/branches and www/conf/branches)
• Put apache2.conf and branchtemplate.conf under version control (in the dev_tools repo)
• Make all of the commands accessible from the uber branch command
• Start using branches and cp -r rather than complete repositories
• Get it working to stage the live branch on Brandon's local machine
• stop the old apache, start the new one under /www
• make the new apache start by default
• explore /www and answer: where do sites live? where are the configurations files? How do we start/stop the server? How do we inspect php settings?
• make apache run the index.php file instead of showing its source
• make the localhost:phpmyadmin work
• inspect the database a new branch uses

A List of Current Problems

• auto load the site, via index.php
• "whosonline" template tag doesn't work correctly. It generates a database error.
  • the same goes for "shortrecentchanges" and "shortnewchanges" tags, sans db error.
• ImageMagick is not activated.

errors specific to railroad

• The skin won't save as default. LocalSettings? extensions/AboutUsSkin?
  • This is probably our skin resetter extension.
• The Search function doesn't seem to work correctly. Could be for all of till, not just railroad.
  • Search won't work without significant effort. Probably not worth is. 75.164.220.31 16:01, 4 September 2007 (PDT)