Welcome! This is the in-progress redesign for the HKN (Mu Chapter) website, built with Django.

Mac M1 users or ARM computers: VirtualBox will not work on the ARM architecture, including M1. Docker using Vagrant exists but currently is not supported and tested.

For now, you can create a venv Virtual Environment without the use of a Virtual Machine. Simply follow all the below instructions and ignore any vagrant ... commands.

This approach is simpler if you are new to developing software.

Vagrant will automatically setup a virtual machine with the correct setup for developing hknweb.

• NOTE: Windows machine users MUST open their Terminal as Administrator
• We have success of the setup completing on Windows Command Prompt, Windows Git Bash, and Windows Linux Subsystem (WSL). Regardless, you must open them as Admin via a right click! Same with Windows Terminal if you use that.

Install Vagrant and VirtualBox (use older version: 6.0.14):

First, within the directory you cloned the hknweb repository, make sure to cd into the hknweb directory. The following commands will only work if you are within the same directory as the Vagrantfile. Then, run

$ vagrant up

which will download and boot a Linux virtual machine, then run setup.

To access the environment, run

$ vagrant ssh

which will ssh your terminal into the virtual machine.

See Development for how to run the Django web server.

To turn off the virtual machine, run

$ vagrant halt

which will attempt to safely shutdown the virtual machine, or kill it otherwise.

This approach requires less space, and is faster if your computer already has Python and GNU Make installed (i.e. most GNU/Linux machines.)

Developing on hknweb requires a virtual environment so that every developer has the exact same development environment i.e. any errors that a developer has is not due to difference in configuration. We will be using Python's built-on venv to make our virtual environment. This command creates our virtual environment.

$ make venv

Next, we need to have our current terminal/shell use the virtual environment we just created. We do this through:

$ source .venv/bin/activate

Finally, we need to install all of our dependencies:

$ make install

In summary, the setup looks like:

$ vagrant up                    # boot up the vm
$ vagrant ssh                   # enter into our vm
$ cd hknweb                     # enter our main directory
$ make venv                     # create our virtual environment
$ source .venv/bin/activate     # enter our virtual environment
$ make install                  # install our dependencies
$ make migrate                  # apply all database changes
$ make permissions              # initialize our database
$ make dev                      # start local web server
$ logout                        # exit the virtual machine
$ vagrant halt                  # after developing, shut down our virtual machine

Without sudo privileges, you will need to add the binary location to your PATH variable. On Linux, this is ~/.local/bin, and on Windows, this is AppData\Roaming\Python\bin.

$ echo "export PATH="$PATH:$HOME/.local/bin" >> .bashrc

Django will also require a working copy of MySQL (or MariaDB).

To run the Django development server (which runs a web server locally), run

$ make

In a Vagrant box, run

$ cd ~/hknweb
$ make

which will make the web site available at http://localhost:3000.

If you would like to access the admin interface in the local web server, run

$ make createsuperuser

You will be prompted for some login info, after which you should be able to access the admin interface with your super user credentials at http://localhost:3000/admin.

This is a compilation of past errors and how they were solved.

• pypa/pipenv#2084
• https://stackoverflow.com/questions/24640819/protocol-error-setting-up-virtualenvironment-through-vagrant-on-ubuntu

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "3e703a10-ae97-4ef6-80fa-bf959a3905dc", "--type", "headless"]

Stderr: VBoxManage.exe: error: Call to WHvSetupPartition failed: ERROR_SUCCESS

• Running the Command Prompt as Administrator, and then running: bcdedit /set hypervisorlaunchtype off
• https://superuser.com/questions/1502529/call-to-whvsetuppartition-failed-error-success-last-0xc000000d-87-verr-nem-v -> see "Simon"'s response