Web Tool for editing Career Pathways roadmaps used by the community colleges in the state of Oregon. The Oregon Department of Community Colleges and Workforce Development (OCCWD) working in partnership with Oregon's 17 community colleges through the Oregon Pathways Alliance developed the Career Pathways Roadmap Web Tool to provide visual maps us…
HTML PHP JavaScript CSS Shell Ruby
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
common
examples
scripts
tests/unit
www
.gitignore
CHANGELOG.md
Career_Pathways_Web_Tool_License_Agreement.pdf
LICENSE.md
LICENSING.md
README.md
composer.json
composer.lock

README.md

1. Install

After downloading the source code, you will need to do some initial configuration.

You can download the source code here: https://github.com/careerpathways/Career-Pathways-Web-Tool

Configure Application

Configure .htaccess file

Copy the www/htaccess file to www/.htaccess and modify it to point to your www/include and common folders.

Set Up Database

Configure the database username and password in your www/include/*.settings.php file. If you can't create your own file, you will have to edit the default.settings.php file directly, just make sure not to commit that file back to the repository.

Install the database tables from the scripts/sql/schema.sql file provided. After the tables are created, run the scripts/sql/initdata.sql file to insert some default data.

Make sure to run updates in scripts/sql to get your database up to date.

Install Dependencies

From the project root, run composer install

2. Start

Development

Requirements

Run vagrant up from www/Vagrant/, then visit http://localhost:8080 in the browser, and you should be presented with a login prompt.

The default user account is admin@example.com and a password of 1234.

Live Server

Requirements

The Career Pathways Web Tool is best suited for a Linux web server running Apache, PHP, and MySQL. It can also run on a Windows web server, but has not yet been implemented in Windows on a production system. The following software is required for Linux and Windows installations:

Note: It may be possible to run the software under a web server other than Apache, however this has not yet been attempted.

Live Server Additional Config

Apache

Configure apache to serve files from the "www" folder in the project. This is usually accomplished with a VirtualHost definition like the following.

<VirtualHost *:80>
	ServerName test.ctepathways.org

	DocumentRoot /web/test.ctepathways.org/www
	<Directory /web/test.ctepathways.org/www>
                Options +FollowSymLinks
                AllowOverride All
                allow from all
	</Directory>
</Virtualhost>

If you have the SetEnv module installed, add this line inside the Directory block:

SetEnv CONFIG_FILE my.settings.php

Change the filename to whatever you want, and copy www/include/default.settings.php to the filename you set here.

Filesystem

If it doesn't already exist, create a cache folder next to the www and scripts folders, and make it writable by apache. If it doesn't already exist, create a asset folder next to the www and scripts folders, and make it writable by apache.

drwxr-xr-x  3 apache   apache    4096 2011-03-24 14:35 cache
drwxr-xr-x  3 apache   apache    4096 2011-03-24 14:35 asset
drwxr-xr-x  7 apache   apache    4096 2011-03-24 14:15 common
drwxr-xr-x  2 apache   apache    4096 2011-03-24 14:15 examples
drwxr-xr-x  3 apache   apache    4096 2011-03-24 14:15 scripts
drwxr-xr-x 12 apache   apache    4096 2011-03-24 14:29 www

Additional Information

PHP Includes

This project is set up to use php includes and modifies the include path. See www/Vagrant/bootstrap.sh where Apache virtual sites are defined for a line similar to php_value include_path \".:/home/project/$projectName/www/include:/home/project/$projectName/common\"

Notice that now, when you see include('x.php'); in PHP, these paths will be checked as well.

Release Process

  • Update (core)/common/version.php with appropriate version number.
  • Add config and release notes to (core)/CHANGELOG.md
  • Tag the release, e.g. 4.3.0