CSforSAC

How to get set up:

Clone the repo into your own directory.

 git clone https://github.com/ejprok/senior_project.git

Go into the repo's directory.
```
cd senior_project
```
Create a virtual environment for Python. This is so that the project has its own version of python to install dependencies to. This makes it so that you don't install dependencies systemwide. We are using python3.
```
virtualenv -p python3 venv
```
After creating the virtual environment, you need to activate it. This is something that you will need to do everytime you want to run the project or install dependencies.
```
. venv/bin/activate
```
Now install the dependencies required for the project. We have them listed in a file called "requirements.txt". Pip will use this text file to look for the dependencies that it needs and will install what it needs to.
```
pip install -r requirements.txt
```
Go into the Django project's directory.
```
cd csforsac
```
Run migrations to build your database.
```
python manage.py migrate
```
Run the actual project. Replace "YOUR_PORT_NUM" with the port number assigned to you.
```
python manage.py runserver 0:YOUR_PORT_NUM
```
Test to see if you can visit the website by visiting 50.116.12.68:YOUR_PORT_NUM in your browser.

Update your Database

To stay updated with the current live demo's database, use this script to copy the database into your project. It will overwrite your current database. From the root directory of the project, use these commands.

Go into the scripts directory
```
cd scripts/
```
Run the script
```
./copy_db.sh 
```

Fix Migration Issues

If you are having trouble with migrations after creating new models or pulling in recent changes, here are some steps to try to resolve the issues.

You should first comment out any new model classes that you are trying to create.
You should also delete all of the migration files in the app that you are having issues with (ex Home, Blog, Events). Make sure that there is still an __init__.py file in the migrations directory, otherwise you wont be able to migrate. If you understand why the migrations are causing an issue, you could edit the migration files instead.
```
cd csforsac/<app_name>/migrations/

rm *.py

touch __init__.py
```
Go back to the directory where manage.py is located, and makemigrations.
```
./manage.py makemigrations
```
Migrate the db, but with the fake option.
```
./manage.py migrate --fake
```
If you had any new models that you commented out, go ahead and uncomment them and makemigrations.
```
./manage.py makemigrations
```
You should finally be able to properly migrate your db.
```
./manage.py migrate
```