Skip to content

Latest commit

 

History

History
37 lines (32 loc) · 2.47 KB

README.md

File metadata and controls

37 lines (32 loc) · 2.47 KB
Raw

acpc_vagrant

Vagrant virtual machine set up for developing, testing, and (possibly) deploying the ACPC poker GUI client and related gems.

Developing with forks of the original ACPC repositories

Edit the paths in grab_projects.sh to retrieve your fork of the ACPC repositories if desired.

Zero to Playing Poker

  1. Download this repository

  2. Install Ruby (>= 1.9.2)

    • On Windows, go to http://rubyinstaller.org/downloads/ and install:
      1. Ruby 2.1.6
        • Ensure that the "Add Ruby executables to your PATH" is selected during installation so you can run the gem and bundle later.
      2. The corresponding DevKit

  3. Install Bundler, gem install bundler

  4. Install gems, bundle install in project root)

  5. Install cookbooks, librarian-chef install

  6. Start the virtual machine, vagrant up

    • This step could take tens of minutes
    • If connecting to the VM times out, but you can still manually connect to it afterwards, then run vagrant halt and vagrant up or vagrant reload. This occurred for me on Windows and vagrant was able to complete the VM setup after restarting.

  7. Log in to the virtual machine, vagrant ssh on Linux or OSX, PuTTY on Windows

    • On Windows, you can try vagrant ssh first, but if that fails, follow these instructions. Afterwards, you should be apply to access the VM from PuTTY or vagrant ssh.

  8. Navigate to shared project directory, cd /vagrant/repositories/acpc_poker_gui_client

  9. In most cases, you will want to use v1.2 since the previous versions are quite old. The rest of the instructions assume v1.2. Run git checkout v1.2 to do this.

  10. Install gems, bundle install

  11. Compile the ACPC server project, bundle exec acpc_dealer compile

  12. Modify config/overlord.yml to be:

    redis: redis-server config/redis.conf
tm-server: bundle exec acpc_table_manager -t config/acpc_table_manager.yml

  13. Run script/start_daemons to start the table manager.

  14. Start the Rails server, bundle exec rails s

  15. Point your browser to localhost:3000, and you should see the match start screen. You should now be able to start a match. If that succeeds, congratulations, you've completed the set up!