Add archived images upload and gallery

[roman-dvorak]

This pull request introduces support for archiving and uploading daily images into a date-based directory structure (images/YYYY/YYYYMMDD/), along with user interface improvements for browsing these archived images. It adds configuration options, updates backend logic to handle uploads and queueing, and enhances the website UI to make archived images easily accessible.

Features

• Instant image upload: Upload images directly from ramfs after each capture (respects "Upload Every X Images" frequency setting)
• Retry Queue: Failed uploads are queued in RAMFS and retried on subsequent captures
• Web Gallery: PHP-based gallery at html/allsky/images/ with calendar navigation and thumbnail support
• Archive Integration: Archive icon in days view shows when archived images are available
• New option uploadimages in Settings > Timelapse panel:
  • Default: false
  • Uploads to: images/YYYY/YYYYMMDD/image-YYYYMMDD_HHMMSS.jpg
  • Depends on: Local Website, Remote Website, or Remote Server being enabled

Technical Details

• Images uploaded from RAMFS (${ALLSKY_TMP}) to avoid SD card writes
• Queue stored at ${ALLSKY_TMP}/image_upload_queue/YYYY/YYYYMMDD/
• Gallery supports date html attribute ?date=YYYYMMDD

Live deployment:

https://space.astro.cz/meteo/sutiny/allsky/images/

The next step is to use a JavaScript library that allows scrolling between images using arrow keys. This should also be implemented for keograms and star trails. It will be in following PR because it is related to multiple parts of sw stack.

[Alex-developer]

Thanks for the PR. I like the idea :-)

I am currently testing the next release, the v2025.xx.xx branch. Once I have done the initial testing I will look at this as it will need merging into the current master branch and refactoring to go into v2025.xx.xx

Thanks

Alex

[roman-dvorak]

Hi, great.
We can definitely leave this until after this release. I can rebase it afterwards and place it over following devel branch. I still need to add documentation to it anyway.

[Alex-developer]

Hi, great. We can definitely leave this until after this release. I can rebase it afterwards and place it over following devel branch. I still need to add documentation to it anyway.

Thanks, more than happy for you to have a look at a PR into the v2025.xx.xx branch if you would be so kind. If you do please do a fresh install of v2025.xx.xx as I have not finished testing the upgrade logic yet but the install code all seems fine for a fresh install.

A lot of the php code has been changed so you will have to re implement it.

[Alex-developer]

I will look at this over the next few days and try and get art into the new release

[Alex-developer]

I have had a look over the code and have a few questions

1. Where is S_uploadimages set , it's used in saveImage.php? - IGNORE this one Eric has answered it
2. I am a little concerned about the delays this could cause in saveImage if images started to queue. Obviously you are running this live so what, if any overhead have you seen this add to the sameImage script.

Thanks

Alex

[EricClaeys]

@Alex-developer, see the code on lines 93 - 98 in saveImage.sh for an explanation of the S_* shell variables.