Hello again @nickcharlton. I took a look through this repo yesterday, and after creating credentials at the two external data providers (Dark Sky and Space Track) I was pleasantly surprised to find that everything seems to still be functioning perfectly.
I'm not a Python dev, and in building an API on top of this service would choose other technologies. The easiest way to leverage this library in other languages/tech/stacks in general would be some sort of CLI, I believe.
Moreover, a CLI might be interesting for developers in general, or consumers who wish to build their own services based off spacebodies.
Each CLI "action" would be a one-off action, so that means:
- Instantiate new
SpaceBodies class with credentials
- Perform requested work (eg run
next_events)
- Return data in some standardised way (probably JSON?)
We'd need to identify the required args for each action. Obviously the three credential vars would be required for all actions, as well as lat/lng, etc. There might be optional args, like category.
I wonder if you think this is an appropriate approach, and how much of a dev-time investment we're talking about?
Hello again @nickcharlton. I took a look through this repo yesterday, and after creating credentials at the two external data providers (Dark Sky and Space Track) I was pleasantly surprised to find that everything seems to still be functioning perfectly.
I'm not a Python dev, and in building an API on top of this service would choose other technologies. The easiest way to leverage this library in other languages/tech/stacks in general would be some sort of CLI, I believe.
Moreover, a CLI might be interesting for developers in general, or consumers who wish to build their own services based off
spacebodies.Each CLI "action" would be a one-off action, so that means:
SpaceBodiesclass with credentialsnext_events)We'd need to identify the required args for each action. Obviously the three credential vars would be required for all actions, as well as lat/lng, etc. There might be optional args, like category.
I wonder if you think this is an appropriate approach, and how much of a dev-time investment we're talking about?