Wiki

Options

Case Status
Log In

Wiki

Options

 
  • RSS Feed

Last modified on 12/22/2011 2:58 AM by User.

Tags:

Project Overview, Environment Settings & Architecture

 

Web Server Environments (IP: 72.51.43.121)
localhost

Developers local environment should be used for minimal testing only. Once code (each FogBugz case) is ready to be tried or bug-tested, upload to 'dev.ysacentral.com' where primary testing is performed.

THIS DOES NOT MEAN YOU WAIT UNTIL THE PROJECT IS COMPLETE BEFORE SYNC'ING TO DEV!

dev.ysacentral.com

Pre-Alpha & Alpha | Developers upload all latest code revisions to dev environment. Developers perform their primary testing. Code may be broken. Development teams bug testers should be using this environment to do thorough bug testing. New code should only be pushed to staging after development teams bug tester has signed off on all bug fixes. 
root dir:  /var/www/html/dev.ysacentral.com/

staging.ysacentral.com Release Candidate | YSA staff test "final" code before going to production. Should always be in functional state -- should never be broken, unless its a true bug.
root dir:  /var/www/html/staging.ysacentral.com/

 
ysacentral.com Stable | Production Environment - Live users.
root dir:  /var/www/html/ysacentral.com/

 
ysasummit2010.com Stable | Production environment for a special project for an Activity last summer. This is the first version of the "Activity Showcase" and it should be used as a guide an code source for that proj.
root dir:  /var/www/html/ysasummit2010.com/

 

Links to Additional Important Wiki Articles:

Database and Flow Document

YSAcentral-Database-and-Flow-2011-07-20.docx

History of this project Framework

  • This project started out using SocialEngine as the social network platform. 
  • Because it was slow and cumbersome, parts of it was converted to custom code.
  • Then we standardized on CodeIgnitor as the framework and had most of the existing site converted over to CI.
Main Website "config" or Configuration File
Much of the predefined data, usernames and login details are defined in the main website config file located at:
lib/config.php
 
Additional Config Files to be Aware of:
admin/lib/config.php
admin/lib/OpenInviter/config.php
admin1/lib/config.php
admin1/lib/OpenInviter/config.php
lib/OpenInviter/config.php
signup/config/config.php
signup/lib/email_config.php
signup/lib/helpers/OpenInviter/config.php
ysa_home/include/config.php
ysa_project/system/application/config/config.php 
 
PHP Framework
CodeIgnitor
 
JavaScript Framework
jQuery
Pusher (http://pusher.com

Global Session Timeout (Login) 

Users session should last for 2 weeks. (sitewide)

User Session Database Driven
User session should be stored in the database (we will need this in the future when we do load balancing across multiple servers)

'console.log' Statements
Remove all JavaScript (FireBug) 'console.log' statements from code before sending to QA or YSAcentral for testing. Also, do not let any code get uploaded to the live server with any 'console.log' statements.

Inline Scripts & CSS
Move any inline JavaScript and CSS to external files. We need to keep code clean to eliminate problems with troubleshooting and bug fixing.

Account User Names, Password and API Keys
Please make sure that anywhere in the source code that requires account user names, passwords and/or API keys, that you are including a "config" file that contains variables with all of those account settings. It could be file or database based. File based is probably the best option, unless it is already database driven. We do not want to have to search through source code anytime we need to move from a test environment to a live environment.