OpenSkedge
OpenSkedge copied to clipboard
FYI Install Status Feb 2018
Thought I would post this as a reference.
VM Setup:
- Google Cloud
- Centos 7 Image
- micro instance
- 10gb disk
- open port 8000 / or install nginx / or use cloud balancer
VM Install (packages with yum)
-
install git
-
clone this proj (branch 1.2)
-
install docker
-
install php70w
-
install php70w-mysql
-
install composer.noarch
-
sym link /usr/bin/composer to ./composer.phar
-
follow install intructions in README
-
run a mysql container
sudo docker run --name openskedge-mysql -e MYSQL_ROOT_PASSWORD=whatever -d mysql
-
configure parameters.yml - follow instructions in README
Issues
- sometimes mysql container produces 100% cpu and can't be stopped - hard to reproduce
- removed the security check in app/app_dev.php
- never used symphony before so be aware you need to run something like
php app/console server:status 10.138.0.7:8000
Unfinished Features?
- Positions cannot be assigned?
- Schedules cannot be exported to .csv or .pdf
Roadmap (for v1.2)
https://github.com/OfficeStack/OpenSkedge/issues/95
Seeing as the roadmap is untouched since 2015, thoughts on converting this to node.js ? I am thinking to fork and convert as I have devs to contribute but have a phobia of php. Does the owner have preferences?
@aogilvie Thanks for writing this up! I'm sure a lot of folks will find this useful. It's been quite awhile since I've run it from scratch.
As for rewriting, I always wanted to rewrite it in Ruby (started on it at one point a few years ago, but abandoned it due to being in school at the time). That being said, if you have other language preferences, go for it! PHP and Symfony are pretty big unmotivating forces for me, which is part of the reason why OpenSkedge has been stagnant for so long, so I understand the PHP phobia. (But more people interested in contributing to OpenSkedge is also a motivator :) )
I'm happy to answer any design questions and provide any historical context that might be useful as well.