Skip to content

Queens-College-Libraries/openroom

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Openroom

Openroom is a web application that manages your room reservations.

This version of openroom is a work-in-progress. We have a lot of enhancements planned. The project is free and open source (GPLv3).

Implemented changes

Please help test "normal" mode (as opposed to ldap) of the application. Openroom now has preliminary support for password_hash() and password_verify(). This is a long overdue change and it is as important as fixing our SQL injection vulnerabilities. This means anyone who is using normal mode before today (hopefully not in production), should inform their users that we need to rehash their passwords. This is also a good time to ask the users to change their passwords. Please take it for a spin today and tell me if you face any bugs!

Proposed technologies

  • PHP 7.1 for a better PHP
  • PDO for database interaction
  • Twig for templating and better theme support
  • jQuery and bootstrap for front end
  • Rework the PHP objects.

Proposed supported web browsers

  • Support current versions of Google Chrome and Mozilla Firefox

A demo for twig support

Please take a look at

this screen shot. List of reservations

It is just an example to show you what I want you to be able to do with your own custom theme. This form is not functional and likely will not be in 2018. This is only a demonstration of my vision.

Rework the PHP objects

The PHP \model namespace is not fully implemented yet. One problem I noticed is I need to make a better use of object-oriented PHP. For instance, a reservation is for a particular room and a particular user. The reservation object is incomplete without a reference to the room object and the user object. When I give you an object of \model\Reservation, you should be able to have full access to the information about the room and the user without any further access to the database (and indeed not even care what database we use). On another hand, Openroom is flexible. This is the reason why administrator is a separate class and not a property of user. Under the current scheme, we need to be able to make a username an administrator without that user ever existing. This is also essential in case of LDAP authentication where we don't control user authentication.

Thoughts?

Please feel free to open an issue or a pull request on github.

On your development machine, log in to the mysql server as root and:

create user openroomdemo@localhost identified by '53PVs7nj2i2AD5FXNLNpZyW3B3sG31WGPThmPCntdldKwxZ5vvb3Pg266HSN8NG';
drop database if exists openroom;
create database openroom;
grant all privileges on openroom.* to openroomdemo@localhost;
mysql --defaults-extra-file=mylogin.cnf -u openroomdemo

now you can install today.sql

use openroom;
source today.sql;

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published