These are the main support channels:


Thanks to Github new donation system it is now possible to donate to the project by clicking this link

Frequently Asked Questions

Not yet. Ideally, I would like to reuse as much code as possible, so I don't have to reinvent the wheel, and write yet another autoguiding engine. This means some other autoguiding application should provide a backend service, and control APIs. The best candidate so far is OpenPHD2, as they already provide APIs, however there's no backend daemon at the moment. You can vote/comment this PR to request the change to PHD developers. As a workaround, I would recommend using PHD2 with a vnc server.

Not yet, but you shouldn't have any issues running it on a mobile browser (though of course it will not be as optimized as a native app can be). There are long term plans for a mobile version using React Native (possibly paid versions under a small fee, but I have to decide yet), but first I'd like to have a more feature complete web version.

Devices support is provided by the INDI Library. Please go to their website for device support. There is also a very active user forum where you can find lots of assistance.

In theory, all major browsers should work, as I didn't use anything specific to a single implementation. However I still didn't manage to do lots of testing on multiple browser, so you might expect some bits missing here and there. The reference browser I use for development is Google Chrome.

For the client, anything with a browser should work perfectly fine. However, since this is a client/server application, the server needs to be a machine running the python backend, and a web browser serving the javascript frontend. Theoretically every major operating system should be able to act as a backend, however the application is currently packaged only for Linux (hence making it perfect for Raspberry Pi and similar). Windows and OSX backend installation might be possible in the next future.

Native (HTML5) notifications are implemented in the application. However some browsers (particularly Google Chrome) only support notifications when using a SSL enabled server. Basically every installation of AstroPhoto Plus should generate its own SSL certificate. On the other hand, when a native IOS/Android version comes around, it will have proper notifications as it will be a native application. At the moment, the best way to get notifications is to use another browser, like Mozilla Firefox, that allows HTML5 notifications on a non https website.

The backend installation process might take a while, depending on how fast your platform is. If you think it's taking too long, check the backend logs using the command AstroPhotoPlus-ctl logs.

Please check you don't have any nginx old configuration conflicting with AstroPhoto Plus. Also worth noting that nginx seems to require IPv6 enabled on some configurations. If you disabled it, and you're seeing this error, try reenabling it and reinstalling nginx.