• Python 3.7|3.8|3.9
• Django 3.1+
• See and install requirements.txt for full dependencies

• Add the data you want to add in a subfolder of data, e.g. data/MW_GCS_Harris1996e2010
• Add a parser in the data folder, e.g. data/parse_harris_1996ed2010.py
• You could stop here and add, commit and push the data + parsers, and we'll handle inserting it into the database.
  • If you do stop here, it would be very helpful if you could provide a mapping (dictionary) that converts the name/identifier (e.g. NGC, Messier) in the dataset you want to add to the name that we use in the SupaHarris database
  • See above, but mapping the parameter names in your database to the parameters we use in the SupaHarris database

• For this step it would be useful to have the development server running locally. Below you'll find three options to achieve this (in order of complexity).
• Parsed data can be inserted into the SupaHarris database by creating a new management command (= a new python file) in the folder apps/catalogue/management/commands. We provide boilerplate to get going! :-)
• cp apps/catalogue/management/commands/add_author_year.py apps/catalogue/management/commands/add_changemeauthor_changemeyear.py, e.g. naming the file add_harris_1996ed2010.py
• Implement apps/catalogue/management/commands/add_changemeauthor_changemeyear.py
• python manage.py add_changemeauthor_changemeyear

• Create virtualenvironment: virtualenv venv

• Activate virtualenv: source venv/bin/activate

• Install required packages: pip install -r requirements.txt

  • If you experience difficulties installting mysqlclient, remove it from requirements.txt (and run with an sqlite3 database)

• Install pre-commit hooks: pre-commit install

• Setup local settings: cp settings/.env.example settings/.env

• Edit settings/.env to tailor to your machine.

  • The example env uses the sqlite3 database backend, console EmailBackend, DummyCache, and without support to auto-retrieve reference data through the ADS API

• python manage.py check

• python manage.py migrate

• python manage.py createsuperuser

• When using SITE_ID = 1 in the settings module one must make sure that the Site with id=1 exists. So first we delete all existing sites, then create one for localhost.

• python manage.py shell -c 'from django.contrib.sites.models import Site; Site.objects.all().delete(); Site.objects.create(id=1, name="localhost:8000", domain="localhost:8000")'

• python manage.py loaddata fixtures/catalogue_AstroObjectClassification.json
• python manage.py loaddata fixtures/catalogue_Parameter.json
• python manage.py add_harris_1996ed2010
• python manage.py add_vandenberg_2013

• python manage.py runserver (and leave running)

• Make sure Docker Engine and docker-compose are installed (see [Docker docs[(https://docs.docker.com/install/))

• Build the image /w BuildKit: DOCKER_BUILDKIT=1 docker build -t supaharris .
• Setup local settings: cp settings/.env.example settings/.env
• Edit settings/.env to tailor to your machine.
• Run the server: docker run --rm -it -v "$(pwd)/settings/.env:/supaharris/settings/.env" -v "$(pwd)":/supaharris -p 1337:1337 --name runserver supaharris bash -c "python manage.py runserver 0.0.0.0:1337" (and leave running)
  • Visit the website at http://localhost:1337
• In a new terminal, one can execute commands in the running container. Load the fixtures:
  • docker exec runserver bash -c "python manage.py loaddata fixtures/catalogue_Parameter.json"
• In a new terminal, one can attach to the container in an interactive session:
  • docker exec -it runserver bash

• ./utils/generate_sslcert.sh
• docker-compose up -d mariadb
  • On first launch, the database and user will be created (you don't have to do anything)
• docker-compose build django nginx
• docker-compose up --build
• In a new terminal, one can attach to the container in an interactive session:
  • docker exec -it supaharris_django_1 bash
• Now add the initial data (run this command in the container!)
  • python manage.py loaddata fixtures/catalogue_AstroObjectClassification.json
  • python manage.py loaddata fixtures/catalogue_Parameter.json
  • python manage.py add_harris_1996ed2010
• Create a superuser (run this command in the container)
  • python manage.py createsuperuser
• Visit the website at https://localhost (and accept the self-signed certificate warning of the browser)

To run all the tests

• python manage.py test apps

Or to run tests in one specific file

• python manage.py test apps.accounts.tests.test_admin

Or to run one specific TestCase

• python manage.py test apps.accounts.tests.test_admin.ParameterAdminTestCase

Or to run one specific test in one specific TestCase

• python manage.py test apps.accounts.tests.test_admin.ParameterAdminTestCase.test_login_of_admin_200

To speed up running the test suite one can keep the database afterwards so the next iteration does not need to create it:

• python manage.py test apps --keepdb

To run the tests /w coverage

• coverage run --source='.' manage.py test apps --keepdb

  • Inspect the Coverage report or html
    • coverage report
    • coverage html

Open the Coverage report, e.g. in a browser on the Docker host (not in the container)

• open htmlcov/index.html

Creation of a References requires the ADS or arXiv url, and all data are automatically retrieved on save. For the arXiv urls the bibtex is scraped, but for new-style ADS we rely on an API connection.

• Create an account for new-style ADS, if you haven't alreay
• Go to you ADS user profile and generate an API key
• Add the key to ADS_API_TOKEN in settings/.env

• Install NodeJS including npm
• cd staticfiles
• npm install
• New packages can now be added, e.g. npm install bokehjs

• gulp the default task that builds everything
• gulp dev browserSync opens the project in your default browser and live reloads when changes are made
• gulp css compiles SCSS files into CSS and minifies the compiled CSS
• gulp js minifies the themes JS file
• gulp vendor copies dependencies from node_modules to the vendor directory