Memories' make php-lint target runs the fixer, and the release list mixes three tag namespaces
Fast, modern and advanced photo management suite. Runs as a Nextcloud app.
At a glance
- What is it?
- Memories is a Nextcloud photo and video management app: PHP backend and migrations, a Vue frontend for all platforms, a Go transcoder and a Kotlin Android client in one monorepo. Its build is a Makefile with six sections, and two of its targets do not do what their names say.
- Who is it for?
- The app fits a Nextcloud operator who wants timeline, albums, external sharing and on-demand video transcoding without building a separate stack, and the store installation plus one indexing command is a short path to a working instance. It does not fit a team that wants its vendor's support to keep pace with Nextcloud releases.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly PHP, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- pulsejet/memories3,878 ★ · +40
| Repository | 2026-09-11 | 2026-11-15 |
|---|---|---|
| pulsejet/memories | 3.8k | 3.9k |
40 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The release list interleaves three tag namespaces
The three most recent releases are not three versions of the app. They are v9.1.0-alpha.1 from 2026-09-21, go-vod/0.6.0 from 2026-09-25 at 10:06, and v9.1.0-alpha.2 from 2026-09-25 at 10:11.
The middle one is the Go video transcoder, published four and a half minutes before the app alpha. It is on the same repository because the project documents three tag namespaces: v for overall releases such as v1.0.0 or v1.0.0-beta.1, go-vod/ for transcoder releases, and android/ for the Android client.
So a reader who treats the releases page as an app version list sees a Go module version sitting between two app alphas, and a reader watching for the Android client has to look for a third namespace that is not in the recent list at all.
The last push to master is dated 2026-10-04, so the tree is ahead of every tag.
The target named php-lint runs the fixer, which rewrites your files
The Makefile's PHP section has four targets and one of them is not a check:
php-lint:
vendor/bin/php-cs-fixer fixThat runs the fixer in write mode with no dry-run flag, so the target named for linting changes the files it inspects and exits successfully either way. A contributor running it before a commit gets a modified working tree rather than a report.
The aggregate target composes three of them:
lint: php-lint psalm js-lintwith psalm running the static analyser and js-lint running the Vue type checker with library checks skipped. So two of the three lint paths report and the first one edits.
The development instructions then tell you the alternatives are make php-cs-fixer and make psalm. There is no php-cs-fixer target in the file; the target is php-lint. The psalm target does exist.
The target named build-js runs the development build
The Vue section names five targets, and the two build ones point at different webpack modes:
build-js:
npm run devThe target called build-js invokes the development script. The production one is a separate target that clears the output directory first and then invokes the production script.
The cleaning targets have the same habit. clean removes the compiled output, and clean-dev removes node_modules entirely. And dev-setup, which the development instructions tell you to run after installing Composer and Node, is the three of them in sequence:
dev-setup: clean clean-dev initSo the documented first step of a manual development setup deletes node_modules, which it also installed moments earlier in the same target chain, and then rebuilds it. The dependency install on the JavaScript side uses npm ci rather than npm install, which means the lockfile is authoritative and the tree has to be gone for it to be used at all.
Batteries-included, with face recognition delegated to two other repositories
The page describes Memories as a batteries-included photo management solution and then lists twelve features.
Most of them are self-contained: a timeline sorted by the date taken parsed from Exif data, a rewind view, albums, sharing with people outside your Nextcloud instance, a map with reverse geocoding, bulk metadata editing, an archive folder for photos you do not want in the timeline, video transcoding with HLS playback, and migration from Nextcloud Photos and from Google Takeout.
One is not. Grouping photos by people and objects is described as being powered by two other projects, a Nextcloud recognition service and a face recognition library by another author. So the one feature that needs a model runs on two dependencies maintained somewhere else.
The performance line is the other claim with a number attached: tested on instances with over a million photos. No configuration, no hardware and no method are given for it.
Installation is four steps and one of them is a command you have to remember
The installation section is four items. Install the app from the Nextcloud app store. Perform the recommended configuration steps, which live on the project's own documentation site. Run a command to generate metadata indices for existing photos. Then open the app and set the directory containing your photos.
The command is the only executable line in the section:
php occ memories:indexIt matters because of the first feature on the page. The timeline is sorted by the date taken, and that date comes from Exif data in each file, which means an instance with existing photos has nothing to sort by until the index has been built. A fresh install appears empty until this runs.
Nothing in the section says how long the index takes, whether it is incremental, or what happens if it is interrupted, and the configuration link it defers to is where those answers would have to be.
The setup tells you to install an editor extension and then to disable part of it
The manual development path starts from an existing Nextcloud: clone the monorepo into that installation's custom_apps folder, install Composer and Node.js 18, run a setup target, run a watch target for the interface, and enable the app through the Nextcloud app management.
Then the editor advice. Five extensions are recommended, three of them for PHP and two for the Vue side, and each carries an alternative in the project's own tooling: a formatting target for PHP-CS-Fixer, a target for Psalm, and nothing for Prettier or Volar.
The last instruction is the one worth keeping. If you use PHP Intelephense, search for a specific built-in feature identifier in the extensions tab and disable it.
So the page tells you to install an extension and then to turn off part of it, without saying what the disabled part does or why the recommended configuration conflicts with it. The alternative path, a dev container with Nextcloud and Memories already installed, avoids the whole question.
The npm manifest is private, its licence string is not SPDX, and a Vue app depends on a React editor
The frontend manifest describes itself as a better photos app at version 9.1.0-alpha.2, authored by one person, with the licence written as the string agpl and the package marked private.
Private is right for a Nextcloud app, since the app ships through the app store rather than through npm. The licence string is the problem: agpl is not a valid SPDX identifier, so tooling that reads the licence from the manifest gets a string it cannot resolve, while the page's licence section correctly names AGPLv3 and points at the COPYING file, and correctly notes that subpackages such as the Go transcoder carry their own licences.
The dependency list mixes three ecosystems. About nineteen packages from the Nextcloud JavaScript libraries, a Leaflet binding for Vue with the map, a PhotoSwipe viewer, an HLS client, a Fuse search index, Hammer for touch gestures, Luxon for dates, and two builds of the same image editor, one vanilla and one React.
The React build of that editor in a Vue codebase is the entry that raises an eyebrow, since it suggests either a wrapper or a leftover.
The tree also holds two agent instruction files, an Exif test image committed at the root, four webpack-related files including two custom plugins, and root directories such as appinfo, lens and metadata that the five documented monorepo packages do not mention.
Editorial conclusion
The app fits a Nextcloud operator who wants timeline, albums, external sharing and on-demand video transcoding without building a separate stack, and the store installation plus one indexing command is a short path to a working instance. It does not fit a team that wants its vendor's support to keep pace with Nextcloud releases. Three things to settle first. What you are pinning, because the tag scheme has three namespaces and the release list interleaves them. What your lint run does to your working tree, because the target named for linting rewrites files. And which parts of the feature set are actually inside this repository, because face and object grouping is delegated to two other projects while the page calls the app batteries-included.
Frequently asked questions
how to install memories nextcloud
Install it from the Nextcloud app store, follow the recommended configuration steps, run `php occ memories:index` to build metadata indices for existing photos, then open the app and set the directory holding your photos. A dev container with Nextcloud and Memories pre-installed is also offered.
Which versions of Memories should I pin?
The repository uses three tag namespaces: v for overall releases, go-vod/ for the Go transcoder and android/ for the Android client. The three most recent releases are v9.1.0-alpha.1, a transcoder release tagged go-vod/0.6.0, and v9.1.0-alpha.2, so the release list interleaves namespaces.
Does Memories include face recognition?
The feature list describes grouping photos by people and objects as being powered by two external projects, a Nextcloud recognition service and a separate face recognition library, rather than by code in this repository.
What licence is Memories released under?
AGPLv3 for the app, with the licence file named COPYING at the root. Subpackages such as the Go transcoder carry their own licences, and the page points to each subpackage's directory. The frontend manifest instead carries the non-standard string agpl.
What does make php-lint do in Memories?
It runs the PHP-CS-Fixer in write mode with no dry-run flag, so the target named for linting rewrites files instead of reporting on them. The aggregate lint target chains it with the Psalm analyser and the Vue type checker.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/pulsejet-memories)Star history chart for your README
[](https://hysenlabs.com/projects/pulsejet-memories)Was this useful?