search

ubc / iPeer

Peer Evaluation System
http://ipeer.ctlt.ubc.ca
Other
17 stars 18 forks source link

iPeer newbie question #593

Open hcanning2014 opened 6 years ago

hcanning2014 commented 6 years ago

Hi, I managed to install iPeer 3.3.2 with TeamMaker on Ubuntu 16 in the var/www/html folder for evaluation. In the home page how to I remove the show hide info at the bottom. Is there a debug mode on someplece? See pic Also I can access the app using 1.2.3.4:8080...how do I change the port so user doesnt need to enter the port number. Finally is phpmyadmin installed? Whats the url? Thanks debug

kitsook commented 6 years ago

Thanks for trying out iPeer.

The info at the bottom can be disabled by changing the debug value, which is defined in app/config/core.php. You can override it by either

(1) create a local config file app/config/config.local.php e.g.

<?php
Configure::write('debug', 0);
?>

or (2) set the environment variable IPEER_DEBUG as 0. If you are using the docker approach, you can find it defined in docker-compose.yml

As for the port number 8080, it depends on the web server you are using on the machine. If you are running iPeer with docker, you can change it in docker-compose.yml

The iPeer package doesn't include phpmyadmin.

hcanning2014 commented 6 years ago

Thanks that worked. It appears I had to restart the docker engine for the change. Have you a non docker iPeer 3.20 version that I can install on a LAMP server the traditional way? 2 more issues: 1.During the install phase the screen said "Display Errors" were OFF instead of ON. Where do I change that?

  1. I am trying to change some CSS (/var/www/html/app/webroot/css.ipeer.css) but the changes aren't registering in the browser. Originally I unzipped the iPeer tar file to /var/www/html. Do I have to restart a service someplace for html and css changes? I also see multiple ipeer.css locations: 
    find . -name ipeer.css
./var/www/html/app/webroot/css/ipeer.css
./var/lib/docker/overlay2/200d136ac23ba7df246dbcb75e46a8b583de54434d47fcc4ffa886ec56b3ee48/diff/var/www/html/app/webroot/css/ipeer.css
./var/lib/docker/overlay2/52ed4bb858ccf63f877b0cfdd41cc571cf04af2fef0575db09e1877e31012b87/diff/var/www/html/css/ipeer.css
./var/lib/docker/overlay2/b520a508b04d96a1460a4a7fbd1cd4ad2a89450db831462ca8a1e56255a69c63/merged/var/www/html/css/ipeer.css
./var/lib/docker/overlay2/e4c95ec6dfa1661cad5a6a7f0f93a30e373a9eac486a841f4322d71d5d6f1064/merged/var/www/html/app/webroot/css/ipeer.css
root@ip-172-31-40-46:/#

I'm working off the below iPeer Readme file. Thanks

ReadMe: Running with Docker

Prerequisites

Running

Pulling images

Note: if you are planning to do development, you can skip this step.

docker pull ubcctlt/ipeer-app
docker pull ubcctlt/ipeer-web

Running iPeer

Note: if you are planning to develop iPeer and did not run docker pull with above commands, you will need to run composer install to install the dependencies and generate database configuration file.

docker-compose up -d

Running Virtual Development Server

Virtual Environment Setup:

  1. Install VirtualBox at http://virtualbox.org
  2. Install Vagrant at http://www.vagrantup.com/downloads

  3. Go to the iPeer root directory in the terminal. Then run the following commands:

    git submodule init
git submodule update
vagrant box add ipeerbox http://developer.nrel.gov/downloads/vagrant-boxes/CentOS-6.4-x86_64-v20130731.box
vagrant plugin install vagrant-vbguest
vagrant up
  4. Go to localhost:2000 in your browser.

Using a different port (the port number must be available on both the virtual and host environment):

  1. change the line in file puppet/dev.pp from

    port => 2000,

    to (eg. port 8888)

    port => 8888,

  2. AND change the line in file app/tests/cases/controllers/v1_controller.test.php from

    $server = 'http://localhost:2000';

    to

    $server = 'http://localhost:8888';

Running Tests:

Go to the iPeer root directory. Then run the following commands vagrant ssh cd /var/www phing test

For more vagrant commands go to http://docs.vagrantup.com/v2/cli/index.html.

Running Tests

Integration Tests

Requirements:

Runing the tests:

cd iPeer
cake/console/cake -app app testsuite app group system

It is better not to touch the mouse or keyboard during the tests.

iPeer 3.2.0

iPeer 3.1.9

iPeer 3.1.8

iPeer 3.1.7

iPeer 3.1.6

This is a maintenance release.

iPeer 3.1.5

This is a maintenance release.

iPeer 3.1.4

This is a maintenance release.

iPeer 3.1.3

This is a maintenance release.

iPeer 3.1.2

This is a maintenance release.

iPeer 3.1.1

This is a maintenance release.

iPeer 3.1.0

This is a feature release that has a few exciting new features:

iPeer 3.0.8

This is a maintenance release.

iPeer 3.0.8

This is a maintenance release.

iPeer 3.0.7

This is a maintenance release.

iPeer 3.0.6

This is a maintenance release. It fixes a few bugs related to the building block API and web interface.

iPeer 3.0.5

This is a maintenance release. It fixes a few bugs related to the building block API and web interface.

iPeer 3.0.4

This is a maintenance release. It is recommended to upgrade to this version as it fixes a one critical bug.

iPeer 3.0.3

This is a maintenance release. It is recommended to upgrade to this version as it fixes a one critical bug.

iPeer 3.0.2

This is a maintenance release. It is recommended to upgrade to this version as it fixes a few critical bugs.

iPeer 3.0.1

This is a maintenance release. It is recommended to upgrade to this version as it fixes a few critical bugs.

iPeer 3.0.0

More than 74 bug fixes or improvements from 3.0.0 Beta

iPeer 3.0.0 Beta

New Features:

iPeer 2.2

Changelog from 2.1 1) Students are now able to view released evaluation results (grades and comments) These results are anonymous, and randomly ordered. Fixed for Rubrics and Mixed Evaluations. 2) Import from CSV changes for Students/Groups: Email and password are optional. Password will be randomly generated if it is omitted from the import file. Column orders are changed. Please see the sample file on import page. Mac/Windows Excel CSV format is supported. Default course is set to blank when importing student. 3) Export Changes Corrected Export Evaluation result calculations. Evaluation result export with details. 4) Copy mixed evaluation function is now working. 5) Small GUI Changes: Changed phrasing and language to make things more clear. More clear notice if student did not finish all questions on student portal. 6) General bug fixes, including some code clean-up. 7) New Listing component Replaces most lists in iPeer with a unified component (with notable exception of Advanced Search). Easy to use for end-users, and to implement and augment by developers.

Changelog from 2.0

1) Over 180 bugs are fixed 2) Major browsers are supported 3) PHP 5.3 is supported 4) Improved security and permission checking 5) Improved installation script and new upgrade script 6) Now exports comments in the CSV file 7) Import Students/Groups from CSV file now functional 8) Instructors can only add students to the courses the instructor teaches 9) Instructors can no longer remove students from courses the instructor does not teach 10) Instructors can no longer remove students from the database 11) An instructor can no longer remove himself/herself from the course 12) Group email links are removed temporarily

Changelog from 2.0.8

1) Bug fix: #1725231 , #1725229 (see bugs list in SF for details) 2) Modify default login page to remove unnecessary JavaScript codes

upgrade from 1.6:

  1. copy the ipeer_export folder OUTSIDE of your iPeer 2 folder
  2. run it from your browser http://yourserverpath/ipeer_export/ipeer_export.php
  3. type the user/pass and whatnot to get the xml file of your database
  4. save it for now and continue on to installation of iPeer 2.

iPeer 2 install:

requirements: mod_rewrite for apache PHP 4.3.10+ with GD extension MYSQL 4+ PEAR with XML_RPC module (optional, only needed when using CWL)

  1. run http://yourserverpath/youripeerpath/install (trailing slash may be required) 1b. create a database in MySql
  2. follow the instructions for the install 2a. if you are upgrading, select UPGRADE and load the xml file there. -- in install4, make sure you set the absolute path to your path!
  3. once the install is complete, delete controllers/install_controller.php and /ipeer_export directory.

please note:

  1. The database config file /app/config/database.php must be writable during installation.
  2. After installation, please make database.php read only. It is VERY important.
  3. To change file permission, you may either use a FTP client or do it directly through command line (if you have shell access to your server. In unix, you may use chmod command to do it)

please report any bugs you find on sourceforge. we can't fix it if we don't know about it.

any suggestion or question? please let us know

troubleshooting:

-if you type http://yourserverpath/youripeerpath/ and you get http://yourserverpath/loginout/login, your mod_rewrite is not set up properly. make sure the line in http.conf has 'AllowOverride All'.

kitsook commented 6 years ago

The "Display Errors" is referring to the PHP settings display_errors . You can set it in php.ini with display_errors = On. If you are using docker, the easiest way (without changing docker images) is to change it at runtime by adding this in app/config/config.local.php:

<?php
......
ini_set('display_errors', 1);
?>

Note that it is recommended to keep this setting off for production servers or machines that are connected to the internet.

If you are using the docker approach, changes should be made to files under git repository you cloned. In your case, that should be app/webroot/css/ipeer.css.

hcanning2014 commented 6 years ago

Thanks. So if I update the css at app/webroot/css/ipeer.css and restart the containers using: docker restart ipeer_app and docker restart ipeer_web ...and then run docker-compose up -d ...should that work such that I see my css edit? ..If not what approach would you use? Appreciated!

kitsook commented 6 years ago

For changing static files like CSS, there is no need to restart the containers. The app/webroot directory in the git repository on your host machine is mounted as /var/www/html in web container. So changes made to files under app/webroot will be picked up by web server container automatically.

For modifying PHP files, if you have debug mode on, changes should also be picked up automatically by the app container without restarting.

hcanning2014 commented 6 years ago

Weird...the css just won't update on the front end

On Wed, Jul 18, 2018, 1:39 PM Clarence Ho notifications@github.com wrote:

For changing static files like CSS, there is no need to restart the containers. The app/webroot directory in the git repository on your host machine is mounted as /var/www/html in web container. So changes made to files under app/webroot will be picked up by web server container automatically.

For modifying PHP files, if you have debug mode on, changes should also be picked up automatically by the app container without restarting.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ubc/iPeer/issues/593#issuecomment-406014582, or mute the thread https://github.com/notifications/unsubscribe-auth/AGG0mGIVtm5UImkt1jk9LNR2wZjRPB2Fks5uH3K1gaJpZM4VLd0l .

hcanning2014 commented 6 years ago

Should I be clearing a cache folder someplace because any changes to files or folders in /var/www/html/app/webroot are not getting reflected on the front end. If I SFTP in with FileZilla and change the css at /var/www/html/app/webroot/css and view source on the front end it still shows the old/original css? Heck if I rename webroot I can still see the site correctly instead of getting a 404. If I search for ipeer.css on the server I see these locations. It seems the iPeer site is served for somewhere other than /var/www/html/app/webroot Totally confused. 

./var/www/html/app/webroot/css/ipeer.css
./var/lib/docker/overlay2/abb0b7e95dc44f31fa14895ae5f8f3fe183fbe7bb147dce549b550ba97c1a9a0/merged/var/www/html/css/ipeer.css
./var/lib/docker/overlay2/200d136ac23ba7df246dbcb75e46a8b583de54434d47fcc4ffa886ec56b3ee48/diff/var/www/html/app/webroot/css/ipeer.css
./var/lib/docker/overlay2/52ed4bb858ccf63f877b0cfdd41cc571cf04af2fef0575db09e1877e31012b87/diff/var/www/html/css/ipeer.css
./var/lib/docker/overlay2/e4c95ec6dfa1661cad5a6a7f0f93a30e373a9eac486a841f4322d71d5d6f1064/merged/var/www/html/app/webroot/css/ipeer.css
kitsook commented 6 years ago

@hcanning2014 Are you using the docker approach? As explained in my previous comment, if you are using the docker approach, the web container mounts the app/webroot directory under your git clone repository as the web root. So you should be editing the CSS / HTML files under that directory, not the /var/www/html on your host machine.

Please let me know if you are using a different installation approach.

hcanning2014 commented 6 years ago

Ok thanks. It seems to be getting more complicated than I expected. What the latest release that doesn't rely on the docker approach. I just want to upload the files and db to my public_html folder and mysql db and run install.

On Thu, Jul 19, 2018, 4:26 PM Clarence Ho notifications@github.com wrote:

@hcanning2014 https://github.com/hcanning2014 Are you using the docker approach? As explained in my previous comment, if you are using the docker approach, the web container mounts the app/webroot directory under your git clone repository as the web root. So you should be editing the CSS / HTML files under that directory, not the /var/www/html on your host machine.

Please let me know if you are using a different installation approach.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ubc/iPeer/issues/593#issuecomment-406403587, or mute the thread https://github.com/notifications/unsubscribe-auth/AGG0mI9BfRGO79eX55fCshnHP_auEexGks5uIOuOgaJpZM4VLd0l .

kitsook commented 6 years ago

You can run the latest source without docker. You just need to configure the web server and DB etc manually. You can refer to the files under docker to see the settings used to configure PHP and nginx.

If you just want to have the web root somewhere else on your host machine, maybe you can move app/webroot to there and create a symbolic link on file system to point to that.