These environment variables should be set before starting the server:

• LOGFILES_PATH => Complete path to the folder where you want to save the log files (e.g. logs on user uploads)
• DATAFILES_PATH => Complete path to the folder where you want to save the files user uploads
• DB_NAME => Name of the database to connect to
• DB_HOSTNAME => Hostname of the database server
• DB_USERNAME => Username to connect to on the database server
• DB_PASSWORD => Password of the database user connecting to on the database server

Run the file Server.py to start the flask web server.

The Schema/ folder has SQL required to set up the database. Run the files in the increasing order of number.

• Python, Flask, MySQL for backend
• ES2015, JQuery, AngularJS for front end
• NPM, Bower as build system
• Heroku, Azure for hosting

Search for the keyword Assumption in the code to find all assumptions. Match the unique number below for each assumption to find where exactly in the code this assumption is used.

Assumptions related to the domain or business logic

• 251020: Each star is separated by ONE blank line
• 251021: Each attribute of the star is on its own line
• 251024: Because of the way the records are updated, if a catalogue is updated say from 'FeH 0.3 [Adamow et al. (2015)]' to 'FeH 0.3 [Adamow et al. (2016)]' a new catalogue is added and the particular composition for that catalogue will still be present with old catalogue in the composition table. For the above example the table composition will have 2 entries, one with 2015 catalogue and one with 2016 Fix: Delete the star completely and add it again. Deleting a star, also deletes the corresponding composition elements, but catalogues are retained as other stars may still use it!
• 251026: M_p, P, e, a planet information should be in the same order in the input file for import
• General: All solar normalizations have same stars. Its only the composition for each that changes. In the explore page, we do not consider the type of normalization selected when filtering stars

Assumptions related to code and are useful for future developers of this project

• 251022: First column returned from select * is always id which is the primary key for this table