Developer Guide

Thank you for your interest in developing SatNOGS! There are always bugs to file; bugs to fix in code; improvements to be made to the documentation; and more.

The below instructions are for software developers who want to work on satnogs-network code.

Workflow

When you want to start developing for SatNOGS, you should follow the installation instructions, then…

  1. Read CONTRIBUTING.md file carefully.
  2. Fork the upstream repository in GitLab.
  3. Code!
  4. Test the changes and fix any errors by running tox.
  5. Commit changes to the code!
  6. When you’re done, push your changes to your fork.
  7. Issue a merge request on Gitlab.
  8. Wait to hear from one of the core developers.

If you’re asked to change your commit message or code, you can amend or rebase and then force push.

If you need more Git expertise, a good resource is the Git book.

Templates

satnogs-network uses Django’s template engine templates.

Frontend development

Third-party static assets are not included in this repository. The frontend dependencies are managed with npm. Development tasks like the copying of assets, code linting and tests are managed with gulp.

To download third-party static assets:

  1. Install dependencies with npm:

    $ npm install
    
  2. Test and copy the newly downlodaded static assets:

    $ ./node_modules/.bin/gulp
    

To add new or remove existing third-party static assets:

  1. Install a new dependency:

    $ npm install <package>
    
  2. Uninstall an existing dependency:

    $ npm uninstall <package>
    
  3. Copy the newly downlodaded static assets:

    $ ./node_modules/.bin/gulp assets
    

Simulating station heartbeats

Only stations which have been seen by the server in the last hour (by default, can be customized by STATION_HEARTBEAT_TIME) are taken into consideration when scheduling observations. In order to simulate an heartbeat of the stations 7, 23 and 42, the following command can be used:

$ docker-compose exec web django-admin update_station_last_seen 7 23 42

Coding Style

Follow the PEP8 and PEP257 Style Guides.

What to work on

You can check open issues. We regurarly open issues for tracking new features. You pick one and start coding.