-
You can no longer enter Issues in GitHub (you can still enter Discussions). Instead, use the new Getting Support page in the WebUI to automatically collect the information needed to troubleshoot your problem. Simply following the instructions on that page.
-
NO private information is sent; that information is kept in the ~/allsky/env.json file which should never be uploaded.
-
The WebUI's Editor page now:
- Tells you if there is a formatting error on the page, for example, if you are missing a comma. You will not be able to save the file until the error(s) are fixed.
- Placeholder values that need updating before a Website will work are highlighted like XX_NEED_TO_UPDATE_XX.
-
The WebUI now displays the status of Allsky (Running, Stopped, etc.). The status is determined every time a WebUI page is displayed, so if the status changes while you are on a page it won't be updated until the page is refreshed.
-
You can now easily specify a location to store Allsky's image other than in ~/allsky/images. This is typically done to store images on an SSD or a similar larger, faster, and more reliable media than an SD card. See the allsky-config move_images command.
-
If you are having problems getting startrails to show the trails, the new allsky-config get_brightness_info command helps by displaying information on image brightness determined during startrails generation. That information helps determine what to put in the Brightness Threshold setting. See Startrails settings for details.
-
The new allsky-config compare_paths command helps determine where to upload your remote Website files and what URL to use. See the Mapping Server Locations to URLs page for details.
-
The allsky-config command can do more, including lettings you change the size of the ~/allsky/tmp directory and the amount of swap space. Run allsky-config for a full list of what it can do.
-
The new meteors directory in Allsky Websites is to upload images with meteors. A meteor icon can be displayed to the list of icons on the left side of a Website page by setting the "display" line to "true" in the "Archived Meteors" section of the associated configuration.json file.
-
NOTE: Support for saving and uploading images with meteors will be added in a future Allsky release.
-
The remoteWebsiteInstall.sh command now prompts to upload any local startrails, keograms, and timelapse files. It's also more "polished", doesn't fail as often, and provides better messages.
-
Allsky Websites now give a detailed message when they can't find the image, instead of just the "Loading..." picture forever.