Releases · aaronwmorris/indi-allsky

Previously, the camera/hardware management occurred in the same process as the main program loop. In release 7.2, I have separated the camera management from the main program loop. The main program loop only handles process management and config management. The capture process is now fully independent. A reload event now completely shuts down the indi client and a new process is created with a new client. If the indi process were to crash, a new process would get created within a few seconds.

This might also help (very slightly) with memory, since using separate processes in python multiprocessing performs a full copy of memory in the new processes. None of the memory related to indi and camera management is copied to the other processes anymore.

File transfer processes are now converted to threads. This should significantly reduce the impact of memory usage when more threads are used. I have increased the default threads to 2.

Assets 2

08 Jul 03:31

aaronwmorris

v7.1

43ced7a

Release v7.1

Data from the NOAA Space Weather Prediction Center is used to predict the possibility of aurora activity.
Text overlay customizations.
Add image saturation controls.

Assets 2

19 May 17:20

aaronwmorris

v7.0

f40342e

Release 7.0

Image stretching
Docker support

Assets 2

30 Mar 02:41

aaronwmorris

v6.3

ab21958

Release v6.3

Authentication handled directly in web application
- Multiple user support
Multi-camera support in web portal
Add passive indi camera support
- Multiple indi-allsky instances can utilize the same camera
SyncAPI REST service
Remote web portal
S3 Object Storage support
Multiple upload worker support
MySQL/MariaDB support
Configs stored/versioned in database
libcamera temperature support
File transfer credential encryption
Logo overlay support
Image circle mask