Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iPeer newbie question #593

Open
hcanning2014 opened this issue Jul 11, 2018 · 10 comments
Open

iPeer newbie question #593

hcanning2014 opened this issue Jul 11, 2018 · 10 comments
Assignees

Comments

@hcanning2014
Copy link

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
Copy link
Contributor

kitsook commented Jul 11, 2018

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
Copy link
Author

hcanning2014 commented Jul 18, 2018

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?
2. 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,
  1. 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

  • Fixed wrong score calculation when using rubric with zero mark enabled
  • Validated Rubric and Mixeval form data
  • Fixed Permission denied when re-add user with super admin #532 permission issue when re-add user
  • Fixed empty email body when there is no special merge field
  • Commented out volume mount for ipeer app docker image
  • Fixed the permission issue in docker image
  • Added docker instructions to readme
  • Added image directive in docker-compose
  • Added AWS deployment script
  • Added a simple health endpoint
  • Added deployment instruction/scripts for GCE
  • Removed config dir and database writable checking
  • More strict checking for env vars
  • Updateed build.xml and travis.yml to use environment vars
  • Set default Session.model value
  • Added web container for static file serving
  • Updated cake guard
  • Used table to detect installation and refactor installation
  • Added docker support
  • Updated translation file
  • Updated deployment script for travis

iPeer 3.1.9

iPeer 3.1.8

  • Fixed incorrect timezone adjustment #494 the incorrect timezone adjustment
  • Removed result release date from survey event view
  • Fixed Cake console i18n task doesn't complete #508, Extract only model,view and controller for i18n
  • Fixed the issue that no event listed when user has dual roles
  • Allowed partial submission for rubric eval
  • Added composer
  • Changed criteria comment field in evaluation_rubric_details to text
  • Fixed wrong calculation in grade API
  • Fixed missing student in eval when he/she has non student role

iPeer 3.1.7

  • Fixed course enrolment not saved on hidden page on user edit
  • Added License file
  • Changed the box Vagrant is using
  • Trimed the input from CSV file
  • Allowed users to hold multiple roles in different courses problem with users that have multiple roles #413
  • Fixed issue showing blank page when admin click on list events

iPeer 3.1.6

This is a maintenance release.

iPeer 3.1.5

This is a maintenance release.

  • Fixed emails templates filling in wrong names.
  • Fixed bug where empty ipeer evaluation reminder emails were sent
  • Added system.version parameter to delta7
  • Updated vagrant and puppet modules
  • Fixed missing formLoaded parameter in event editing
  • Fixed the failed test and update version in sample data
  • Moved delta 5 into delta 4 and remove sql mode in 6
  • Fixed some bugs && temporarily removed show student events
  • Fixed releasing comments for student view of evaluation results
  • Added commands to refresh the cache directory into the upgrade script
  • Implemented some validations to event edit
  • Fixed super admins unable to view all instructors and faculty admins
  • Created upgrade script to version 3.1.4
  • Fixed events add/edit event forms

iPeer 3.1.4

This is a maintenance release.

  • Increase the script exec time on export action
  • removed disabling edit group buttons when submissions have already
  • added pseudo data for rubric view
  • fixed broken link for adding survey questions when using
  • added individual criterion comments to the rubric csv export

iPeer 3.1.3

This is a maintenance release.

  • Fix a bug causing upgrade from 2.x failed
  • Improved the language on Student Result Mode help text

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:

  • New mixed evaluation question type called Score Dropdown
  • New interface to add or remove instructors and tutors from courses
  • Permissions Editor
  • Basic evaluation results view for students
  • Email reminders for submitting evaluations
  • New auto-release evaluation results option. Results can be release without review
  • PDF export for evaluation results
  • Ability to import groups with student numbers
  • New option to update or merge for users and groups import
  • Account Consolidation
  • Moving students between courses with the same survey
  • Bulk moving students between courses
  • Google Analytics Support
  • Support for PagodaBox for easier instance set up
  • Login logging
  • Improved interfaces for mixed evaluation and survey templates

iPeer 3.0.8

This is a maintenance release.

  • Fix the API logging message missing info
  • Text Wrap for Survey Response and Timezone Fix
  • Fixed Firefox issue with mixed eval scale weight

iPeer 3.0.8

This is a maintenance release.

  • Fixed reported bug in student index
  • Fixed courses edit for instructors and tutors
  • Modified courses/edit for instructor in no faculties
  • Fixed a timezone bug.
  • Added a small event model test
  • Fixed survey group member model tests

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.

  • Fixed a bug in the api
  • Modified groupMembers and enrolment in the api
  • Updated guard plugin
  • Fixed a bug when adding 0 member to course using API
  • Fixed zero_mark bug for rubric view and rubric evaluation forms
  • Fixed non-existing users added to group as id 0 by API
  • Fixed Comment vous pouvez a Facebook compte #480, removed auth error on login page when redirect from app root
  • Moved API log into logs/api.log
  • Fixed a style issue
  • Fixed failed to add user when user data has tab (\t) in API

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.

  • Fix submissions for simple evaluation are not stored correctly

iPeer 3.0.3

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

  • Fix incorrect question number in mixeval
  • Using student first submission timestamp as late penalty criteria
  • Fix mixeval descriptor overflow issue

iPeer 3.0.2

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

  • Disable submission confirmation email
  • Fix some bugs & outdated instructions
  • Fix change password for editProfile
  • Fix some bugs for email templates
  • Fix warnings caused by empty courseId in group controller
  • Fix user can't login with session transfer if there is an old session
  • Unify the views in v1 controller
  • Fix preview button on add event page in IE and FF
  • Allow fall back to mail in template email
  • Fix incorrect logging when sending submission email failed.
  • Fix missing names in the email after creating user
  • Disable the type checking for upload csv file for now
  • Fix Grade release failed when installation is under sub directory #471, add extra file type to allow upload for user import
  • Fix that email failed to send when stmp parameters are not set
  • Fix students unable to submit evaluations #464. The student view of mixeval result was not showing correctly.
  • Update guard to allow login in with PUID as username in cwl module

iPeer 3.0.1

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

  • Fix old survey event can't be edited
  • Fix penalty display when only 1 penalty present.
  • Remove result release date from event form for surveys
  • Fix it couldn't add question in survey in IE and Firefox
  • Fix a teammaker xml issue when student survey response id is NULL
  • Fix Survey result link on instructor/admin home.
  • Fix old survey result do not show on viewEvaluationResult
  • Exclude dropped student from survey result summary
  • Fix survey save for "Choose any of" questions
  • Fix unable to add text answers to surveys
  • Fix master question losing responses & deletion
  • Fix previous submissions not loading
  • Fix Survey Question - Add/Remove Answer not working

iPeer 3.0.0

More than 74 bug fixes or improvements from 3.0.0 Beta

  • Better CSV export. More efficient and better format for process
  • Upgrade scripts allowing to upgrade from 2.x
  • Better student home page
  • Confirmation email after evaluation submitted
  • New color theme
  • And more

iPeer 3.0.0 Beta

New Features:

  • Improved Installation and Upgrade Wizard
  • The new Tutur Role and Faculty Admin Role
  • Evaluation Absence and Mark Deduction
  • Fine-grainded Access Control
  • New APIs
  • Group Export
  • Group Email
  • CWL/Shibboleth, LDAP Authentication
  • Basic LTI Support
  • Internationalization (i18N) support
  • Upgrade to CakePHP Framework 1.3
  • A lot bug fixes
  • And more

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
Copy link
Contributor

kitsook commented Jul 18, 2018

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
Copy link
Author

hcanning2014 commented Jul 18, 2018

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
Copy link
Contributor

kitsook commented Jul 18, 2018

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
Copy link
Author

hcanning2014 commented Jul 18, 2018 via email

@hcanning2014
Copy link
Author

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
Copy link
Contributor

kitsook commented Jul 19, 2018

@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.

@kitsook kitsook self-assigned this Jul 19, 2018
@hcanning2014
Copy link
Author

hcanning2014 commented Jul 19, 2018 via email

@kitsook
Copy link
Contributor

kitsook commented Jul 20, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants