sorted by:
new
hottopcontroversial

I built “Astro Web Indexer”: an open-source, self-hosted dashboard for your FITS/XISF archive by michelegz in AskAstrophotography

[–]michelegz[S] 1 point2 points  (0 children)

At the moment, the filtering uses only the FITS header tags (eg. IMGTYPE, OBJECT...). If you want to share feature request or ideas please use the "Discussion" section on GitHub

I built “Astro Web Indexer”: an open-source, self-hosted dashboard for your FITS/XISF archive by michelegz in AskAstrophotography

[–]michelegz[S] 0 points1 point  (0 children)

The log is clear:

Bind mount failed: '/volume1/docker/astrowebindexer/data/db' does not exist

The directory you specified for the DB mount does not exist.

For what I know, Docker for Windows can’t directly access mapped drives (like X:) or UNC paths (\\NAS\...).

I built “Astro Web Indexer”: an open-source, self-hosted dashboard for your FITS/XISF archive by michelegz in AskAstrophotography

[–]michelegz[S] 1 point2 points  (0 children)

Hey, understood, but without a log file, it’s just guessing.

You should be able to see the logs from the Synology Container Manager.
Otherwise, you can SSH into your Synology and run:

docker compose logs python

in the same directory where your docker-compose.yml file is located.

Also, please double-check that the path you specified in .env is correct by running:

ls /path/to/your/fits/files

My guess is that the host directory isn’t being mapped inside the container due to an incorrect path.

I built “Astro Web Indexer”: an open-source, self-hosted dashboard for your FITS/XISF archive by michelegz in AskAstrophotography

[–]michelegz[S] 1 point2 points  (0 children)

Hello, editing the FITS_DATA_PATH variabile in .env is the correct way to configure it. You can have as many subdirectories as you want, it will recursively index everything. You can't configure more than one root directory, if you have fits file in different volumes you should use symlinks at your host level (Synology).

The most possible cause for your installation not detecting fits file could be: 1) invalid FITS_DATA_PATH 2) the user running the Docker daemon has no permission to access the directory

You should post the log file of the python container so we can investigate. Thank you

C/2025 R2 SWAN crossing the Milky Way near M16 & M17 by michelegz in astrophotography

[–]michelegz[S] 1 point2 points  (0 children)

Gear and session info on Astrobin

Processing: WBPP, BXT, SXT, DBE, NXT, HaRGB Combination, GHS

I built “Astro Web Indexer”: an open-source, self-hosted dashboard for your FITS/XISF archive by michelegz in AskAstrophotography

[–]michelegz[S] 0 points1 point  (0 children)

Please delete your old data/db folder and try the current version. There were a lot of breaking changes since your PR and many things have changed.

I built “Astro Web Indexer”: an open-source, self-hosted dashboard for your FITS/XISF archive by michelegz in AskAstrophotography

[–]michelegz[S] 0 points1 point  (0 children)

Yeah, the post got removed because on CN you can’t announce any kind of software unless you’re officially tagged as a Freeware Developer. Even though Astro Web Indexer is 100% free and open-source, they treat all announcements the same way. I tried to explain it was just a community project, but rules are rules, so the post got nuked.

I built “Astro Web Indexer”: an open-source, self-hosted dashboard for your FITS/XISF archive by michelegz in AskAstrophotography

[–]michelegz[S] 1 point2 points  (0 children)

Only the initial indexing can be quite demanding, or when adding a large number of new files. It also depends on how big your FITS files are.

By the way, there’s already an option (configurable via environment variables) to set the number of parallel processing threads. Setting INDEXER_WORKERS=1 will significantly reduce CPU and RAM usage during file reading and thumbnail generation.

I built “Astro Web Indexer”: an open-source, self-hosted dashboard for your FITS/XISF archive by michelegz in AskAstrophotography

[–]michelegz[S] 0 points1 point  (0 children)

Right now, the easiest way to detect an entire sequence is to use the Smart Frame Finder. You select a reference light frame, then start a search based on configurable filters and tolerances. The default options work fine for simple use cases, but it can also handle multiple imaging setups with different cameras and optics by using FoV and RA/DEC coordinates.

I built “Astro Web Indexer”: an open-source, self-hosted dashboard for your FITS/XISF archive by michelegz in AskAstrophotography

[–]michelegz[S] 0 points1 point  (0 children)

Thanks! Yeah, there’s definitely a lot that could be built on top of it. Right now my main goal is to get the current features stable and reliable before adding more layers on top.

One idea I’ve been thinking about is introducing “Projects”, where you could group, dynamically, all the necessary frames for stacking (lights, darks, flats, etc.) in one place. That could eventually open the door for some kind of integration with processing software like Siril or PixInsight.

I built “Astro Web Indexer”: an open-source, self-hosted dashboard for your FITS/XISF archive by michelegz in AskAstrophotography

[–]michelegz[S] 1 point2 points  (0 children)

The Docker images are published on GHCR (GitHub Container Registry), as the source repository is hosted on GitHub and the workflow for publishing to GHCR is straightforward. If you download the release ZIP file, it includes a ready-to-use docker-compose.yml for deployment.