Skip to content

vagrant-vm-README.md

Latest commit

 

History

History
92 lines (78 loc) · 3.14 KB

vagrant-vm-README.md

File metadata and controls

92 lines (78 loc) · 3.14 KB

Vagrant VM (VirtualBox) Development Environment

Note: There are known issues with running VirtualBox on Apple Silicon. Use the Docker option instead.

The application may be installed within a Vagrant VM that is running on Scientific Linux 7. The VM is provisioned using the same Ansible playbook used in production.

Initial Setup

  1. Install VirtualBox.
  2. Clone the repository. 
    git clone https://github.com/ucb-rit/coldfront.git
cd coldfront
  3. Prevent Git from detecting changes to file permissions. 
    git config core.fileMode false
  4. Checkout the desired branch (probably develop).
  5. Install vagrant-vbguest. 
    vagrant plugin install vagrant-vbguest
  6. Create a main.yml file in the top-level of the repository. This is a file of variables used by Ansible to configure the system. 
    cp bootstrap/ansible/main.copyme main.yml
  7. Generate a key to be used as the SECRET_KEY for Django. 
    # This produces two lines: condense them into one.
openssl rand -base64 64
  8. In main.yml, uncomment everything under the dev_settings section, and customize the following variables with your own values. 
    django_secret_key: secret_key_from_previous_step 
chmod_tasks: true # Can be false when a Windows FS is mounted
db_admin_passwd: root
redis_passwd: root
  9. Provision the VM. This should run the Ansible playbook. Expect this to take a few minutes on the first run. 
    vagrant up
  10. SSH into the VM.
vagrant ssh
  1. On the host machine, navigate to http://localhost:8880, where the application should be served.

Virtual Machine

  • Once the VM has been provisioned the first time, starting and accessing it can be done with:

    vagrant up
vagrant ssh

  • To stop the VM, run:

    vagrant halt

  • To re-provision the VM, run:

    vagrant provision

Environment

  • The application is served via Apache, so any changes to the application (excluding changes to templates) are not applied until Apache is restarted, which can be done with:

    sudo systemctl restart httpd

  • The Ansible playbook can be run manually as follows.

    cd /vagrant/coldfront_app/coldfront
# Assert that there is a properly-configured main.yml in the current directory.
ansible-playbook bootstrap/ansible/playbook.yml
    • Note that to skip initial provisioning tasks you can use the --tags common or --skip-tags provisioning arguments to ansible-playbook.
    • Alternatively, you can set provisioning_tasks to False in main.yml

  • Any custom Django settings can be applied by modifying dev_settings.py. Note that running the Ansible playbook will overwrite these.

Emails

  • By default, emails are configured to be sent via SMTP on port 1025. If no such server is running on that port, many operations will fail. To start a server, start a separate SSH session (vagrant ssh), and run the below. All emails will be outputted here for inspection. 
    python -m smtpd -n -c DebuggingServer localhost:1025