Conference Submission System
This is an open-source conference submission system, built in Rails and has been used for the Agile Brazil conference since 2010. Some of the features supported are:
- User registration
- User profiles
- Support for I18N (currently supports: en, pt-br)
- Conference tracks, audience levels, and different session types
- Session submission
- Comments on sessions
- Phases and deadlines (submission, early review, review, program compilation)
- E-mail notifications
- Track organizers
- Adding reviews and feedback to authors
- Review decisions of acceptance/rejection and e-mail publishing
Just clone this repo (including submodules so ensure you run
git clone https://github.com/agilealliancebrazil/submissions.git --recursive or if you already cloned, use
git submodule foreach git pull origin master), enter it and run
./dev.sh. This should be enough to install whatever is needed on your machine and start guard to run specs and front end tests.
vagrant destroy -f dev && vagrant up dev && vagrant ssh dev
Once inside the vagrant box, run
/srv/apps/registrations/current/dev.sh. Note that the code will be sync'ed between the virtual machine and your machine so you can still use your favorite editor and handle version control from your machine if you prefer.
Deployment is handled by Capistrano. And can also be tested using the vagrant set up.
To test, run:
vagrant destroy -f deploy && vagrant up deploy && bundle && bundle exec ruby deploy/first_deploy.rb vagrant 10.11.12.16 staging certs/insecure_private_key
Note that Capistrano uses the code currently available in github so you need to push to test it.
You can set up
config/deploy/vagrant.rb to use a different branch with
set :branch, 'your_branch'.
Deploying to a cloud
If you're deploying to any cloud, after you've created your virtual machine, add
config/<vms_ip>_newrelic.yml. You can, optionally, also add
certs/<vms_ip>_server_key.pem to set up apache to work with SSL. Then run:
bundle && bundle exec ruby deploy/first_deploy.rb <configured_sudoer_user> <vms_ip> <type> <ssh_key_to_access_vm>
Where your sudoer user is a user in that machine that has sudo right (no password required), vms_ip is the vm IPv4 addres, type is either 'production' or 'staging' and the ssh key is the path in your machine to the ssh key that allows non password protected access to your cloud VM.
From then on, you can use:
bundle && bundle exec ruby deploy/digital_ocean/new_machine.rb
If you have a bug or a feature request, please create a issue here:
Thanks to all our contributors! The core team is:
- Hugo Corbucci (Core Developer)
Our huge thanks to past developers:
- Danilo Sato (Original Developer)
The conference submission system is released under the MIT license. See LICENSE for details.