I'd like to move away from Apples Photo.app to open-source, self-hosted, and browser-based application that may run on a NAS or Linux server.
There seem to be lots of alternatives out there (Nextcloud, Piwigo, ...) but I'd love to hear about recommendations and experiences.
https://photonix.org/
Installation is fairly simple with Docker, frontend is web-based (React), backend is Python with a sprinkling of Tensorflow. So far auto-tagging of photos by location, object detection and colour is fairly decent. UI is progressing and is useable on most devices, though quite minimal.
Please feel free to check out the demo site and the GitHub issues. I'd really appreciate feedback and help. Thanks.
I've been struggling to find a tool that handles that handles the duplicates problem within a web interface. I've been experimenting with some approaches including perceptual hashes and was wondering if that's something you'll include?
Is there any way to use metadata from Lightroom Catalogs, or enable people tagging in your current implementation?
I don't have any experience of Lightroom but I can have a go at reading the files if you think it's useful.
I have checked this out, running the docker-compose method, and kudos for your work. Looks great.
One issue I ran into was regarding videos (tried with a couple of MOV and MP4) - it doesn't generate a thumbnail and in fact throws an error along the lines of: File "/srv/photonix/photos/models.py", line 84, in base_image_path AttributeError: 'NoneType' object has no attribute 'base_image_path'
Happy to open a gitHub issue, but thought I'd drop you a line here to see if it was your intention to support videos (which would be cool!)
Cheers,
I'm looking at the docker-compose.yml and wanted to give it a go, but not allow it any way of deleting anything :)
The thinking behind GraphQL was to allow for advanced filtering, supporting all the attributes we store without a lot of extra API work. The GraphiQL web interface makes it quite nice to explore the data and is bundled in and accessible at /graphql . GraphQL also has "subscriptions" which allows for pushing data from the server. The Apollo JS library I used also provides built-in extras like caching.
PhotoStructure is browser-based (using Vue), and scales to hundreds of thousands of assets over millions of files. Your library can be created on a Mac, saved on your NAS, then later opened and managed by a Linux box, seamlessly. Raw images have highlight restoration before rendering previews. Videos are auto transcoded for mobile and desktop web use. Corrupt images are detected automatically and culled. Image source sets are used to minimize network data and maximize viewing quality. XMP sidecars are imported for metadata. Importing aggressively coalesces duplicate images and videos using direct and inferred metadata, so even your downsized Google photos takeout will be deduped with your originals.
Once you've got a huge library, though, it needs a novel UX. Scroll-reverse-chron and a search bar shouldn't cut it. PhotoStructure has a couple novel and unique approaches to navigation, which you can read about here: https://blog.photostructure.com/introducing-photostructure/
It scales down to odroids, and up to as many CPUs as you can throw at it, and self-throttles CPU during library sync so the machine is still useable. Installation takes under a minute, and updates are automatic.
It's closed-source because it's how I want to pay for my food and clothing, but it's a corporate mandate to open source in case of business closure, which is also explained in that blog post.
I'm sending out another wave of beta testers later today, and during the beta it's free. I'm giving heavy discounts to my beta testers that share feedback.
I'd love to hear what you think.
I am not making any judgement on the service, just that it is not an appropriate reply for what is being asked here.
Having written many open source libraries (my rubygems have been downloaded several million times, my node packages are close to that, and I've contributed to other libraries for over a decade), I personally will choose open source projects over closed-source because I don't want to be victimized by abandonware or corporate whims.
It seems like photo software (both closed and open source) is especially prone to dying on the vine. It's a common need, and it's easy (and fun) to write a simple script that makes thumbnails from a folder of images. I seen countless photo projects on github, but as complexity ramps up quickly, the installer script (if there is one) breaks, updates fail, there aren't any tests, and the author gets bored and moves on.
I guess I felt justified here because a) it is self-hosted, and b) I'd added my corporate mandate to open-source the codebase in case of business closure. (I don't remember a corporation doing this open-source-on-close before, do you?)
I've actually already open-sourced some of the trickier bits: https://exiftool-vendored.js.org/ and https://batch-cluster.js.org/. I expect that to continue.
I am essentially looking to leave the original photos on external drives and have an app that indexes them and stores a customizable thumbnail with the app to view them on my local machine. This way I can browse through all my photos and figure out the original file path if I want to retrieve them. The most important aspect is that I can take the drives offline while the thumbnails and index remains within the app and re-indexing when connected again.
My existing workflow is to import all photos on my mac to the Photos app. I pull them from different devices (phones, camera, etc). The photos app does an OK job at de-duping any matches. I also run PhotoSweeper to further de-dupe which analyzes the photos itself and I can leave the best ones remaining. After that I run some custom scripts to export the data as [year]-[month]/[year]-[month]-[day] [hour].[min].[sec].jpg. I then merge those onto my external drive and kick off my backup process to clone them to other drives and sync to cloud.
The closest I have come is Lightroom which indexed the drive a little bit but the "thumbnails" and catalog is huge. It allows some tagging and other features to discover old photos but some processes are a bit manual. This workflow seems to be common among digital asset management software which is expensive and way more then I am looking for.
After you install, the second question you should pick "No thanks, I like my photos and videos where they already are." See https://support.photostructure.com/automatic-library-organiz...
Email me at hello at photostructure.com or sign up for the beta. I'd love to hear what you think!
https://github.com/srinathh/naspics
(edit: some data destination paths are probably hard coded since I wrote it for myself but can be easily broken out into command line options if needed)
> It is build on React using the Create React App tool, written in Javascript and requries a NodeJS development environment.
https://m.imgur.com/gallery/gNFw1PU
https://m.imgur.com/gallery/NzatdKZ
It was way ahead of it's time, and actually worked!
Best of all, it did everything locally... not cloud based and thus retained privacy of your personal photo collection.
It took multiple disparate photo directories and presented everything in a timeline of folders. And because everything was local, that happened quickly, rather than waiting for your browser to get the next 100 photo results from a javascript call or whatever.
Are there any photo clients for windows that present multiple folders as a single coherent timeline? And can manage tens of thousands of pictures? I've got stuff going back to the late 1990s and would love to be able to find all those old cat pictures or whatever.
PhotoStructure does this (and I believe is the only software that does robust time zone inference, as well). (I've posted elsewhere here with more details).
Doesn't help much for privacy, however.
I'd love to have you try out the beta and have you share feedback!
One question though - if you end up feeling it's unsustainable to continue developing PhotoStructure down the line do you have a plan? Obviously we would rather not be burned by it either, you you consider at that point making it open source so existing users can continue and make improvements?
Certainly I hope it never comes to it but it's nice to have a little reassurance.
It's really the killer-feature that made Picassa so great - find all the photos over several years of a family member or friend.
Sadly, I've needed this feature for funeral photo albums lately and could really use the old Picassa!
https://perkeep.org/doc/
Which is a shame because I really like Perkeep/Camlistore as a concept.
-- Edit --
Actually on checking, it doesn't seem like Perkeep is at all dead. I'm seeing several updates in the last month...
I can still take pics on the phone which will be synced via Dropbox and Shotwell picks them up immediately. The sync is faster than I’m used to on iCloud and finally I just have files that I can tag, again.
Shotwell is also super fast, has a similar UI to photos.app (automatic events for example), but it also had hierarchical tags which it can even write to the files itself. So it’s very simple and yet portable without lock-in. Couldn’t be happier. Of course ymmv.
Good luck!
It looks pretty good, has multi-user capability, metadata editing, etc. It would be nice if it had some geotagging integration and ability to group albums into sets.
I filed a bug report and the developers/maintainers fixed it very quickly.
[1] https://github.com/LycheeOrg/Lychee