https://satnogs.mhuebner.eu/index.htmlsatnogs-client-rs is a lightweight, rust-based implementation of a client for the SatNOGS network. It focusses on different goals: Minimalism: The client itself should do the bare necessities, to keep the codebase small and comprehensible Hackability: The original pre-/post-script mechanism of SatNOGS client is modified to be more versatile: Instead of calling scripts with some cmd-line options, we give them the whole job-metadata as json, so they can use anything they possibly can need. Additionally, scripts run in lexicographical order from a scripts directory. You don’t need to adjust any code to get your pre/post script run. Configurability: Clients configuration gets heavily simplified by using a comprehensible toml configuration format. Config files work hierarchically, so you can override single values and leave the rest at the default. This leads to small, readable config files. Additionally, it provides a web-based configuration interface, for those who don’t like command lines Tip Don’t want to read that much? You may hop directly to the install chapter. If you feel lucky and trust me, just paste this command to your shell:Hugoen-ukhttps://satnogs.mhuebner.eu/install/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://satnogs.mhuebner.eu/install/index.htmlTip For fast installation: Copy this line and paste it in the shell of your SatNOGS station: curl -sfL https://satnogs.mhuebner.eu/install.sh | bash -s -- Foreword: Deployment Philosophy satnogs-client-rs aims to be more easy in installation compared to the standard SatNOGS client. Therefore, some deployment decisions were made: Avoid Ansible: While I found ansible to be an excellent tool for system provision, it certainly needs you to understand it concepts. Most users don’t know these concepts and therefore can’t fix things, if they break (again). This can be highly frustrating to users, which we want to avoid. Instead, we opted for a web-based wizard (see chapter Setup). Do things the Debian way: In my personal opinion, Debian has solved most of the deployment problems, the SatNOGS community is facing, already in a mostly elegant and practical way. Therefore, I opted for Debian packages (.deb) and systemd service units, instead of a single monolithic docker container (which is in fact Debian again, but that’s another story…). Simplicity is key: Installing on top of a standard Debian image should be easy and follow standard procedures practised in other projects too. Preparations and Overview I assume that your hardware is the Raspberry Pi based reference ground station as described by the SatNOGS people in the wiki. Other stations (e.g. x86-64 based) should also work though. On that station needs to run a plain Debian 12 (bookworm) or Debian 13 (trixie). Please prepare those images according to the Raspberry Pi Tutorial or another suitable source of your choice.https://satnogs.mhuebner.eu/setup/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://satnogs.mhuebner.eu/setup/index.htmlBasic web-based Setup To set up the basic parameters of your station, please open a webbrowser of your choice and navigate the hostname/ip-address of your station in your network. Please use http protocol, e.g. like this: http://192.0.2.42 or http://2001:db8::42 Please mind, that you will need to access the site in unencrypted http. If you can’t access the page, your browser might have swapped it silently for https, which is on another port. At the time of writing, station configuration can only be done with http on port 80.https://satnogs.mhuebner.eu/operation/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://satnogs.mhuebner.eu/operation/index.htmlIn this chapter, you will get some information and examples on operation and modify/extend a station with satnogs-client-rs. Basics satnogs-client-rs is controlled via systemd-units. To start/stop it, you can use the systemctl command: # start the station $ sudo systemctl start satnogs-client-rs # stop the station $ sudo systemctl stop satnogs-client-rs Per default, satnogs-client-rs is enabled and will startup with your system booting up.https://satnogs.mhuebner.eu/internal/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://satnogs.mhuebner.eu/internal/index.htmlThis chapter gives you information that I wasn’t sure on where to put else. Configuration Reference adsf Observation Data Layout The original SatNOGS client opted for a single directory in /tmp/ that holds all (temporary) observation artifacts. While this work okay for most of the time, I found some drawbacks with this: