Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • May 19 14:12
    asitemade4u edited #36
  • May 19 14:10
    asitemade4u edited #36
  • May 19 14:10
    asitemade4u edited #36
  • May 19 14:09
    asitemade4u opened #36
  • May 19 13:27
    asitemade4u opened #35
  • May 19 12:41
    asitemade4u commented #32
  • May 18 21:21
    xemle commented #32
  • May 16 21:39
    asitemade4u opened #34
  • May 16 15:55
    asitemade4u opened #33
  • May 16 15:49
    asitemade4u commented #32
  • May 16 15:49
    asitemade4u commented #32
  • May 16 15:48
    asitemade4u commented #32
  • May 16 15:46
    asitemade4u commented #32
  • May 16 15:45
    asitemade4u commented #32
  • May 15 06:10
    xemle commented #32
  • May 14 13:38
    asitemade4u opened #32
  • May 08 20:55
    xemle commented #31
  • May 08 09:56
    xemle commented #28
  • May 08 09:53

    xemle on master

    webapp: Add image and video amo… (compare)

  • May 07 13:57
    matbgn commented #31
theaerotoad
@theaerotoad
@xemle, I'm having a bit of a problem testing out my changes. I'll make a (seemingly minor) change to a *.tsx in packages/webapp/src/, then issue another npm run build. It doesn't seem to consistently update the webapp, even after doing a force refresh in the browser. Is there some equivalent to make clean; make that I'm missing? I've not worked much with npm or lerna, so this may be a dumb question.
Sebastian
@xemle
@theaerotoad for developing the webapp you start your server on localhost:3000, run npm run dev in packages/webapp and open http://localhost:1234. Port 1234 is a dev webapp server and proxies api requests (database and previews) to the server on port 3000. Changes should be detected and the webapp on port 1234 should reload automatically.
Sebastian
@xemle
when you are done with the webapp packahe you need to build the server to copy the new webapp assets to the stic public folder of the server via npm run build -- --scope @home-gallery/server
Sebastian
@xemle

New Release

[1.2.0] - 2021-08-06

Added

  • Add option to open browser on server start
  • Add logger with console and file logger
  • Add quick search links on some media meta data
  • Add keyboard shortcuts to single view
  • Add end to end tests
  • Add file index journal
  • Speedup incemental database updates via file index journal

Fixed

  • export: Fix webapp copy for export
  • index: Fix checksum option. Use --no-checksum to disable it
Sebastian
@xemle
Good evening
Dennis Schey
@trashcoder
Good evening
Sebastian
@xemle
Which type of chat service do you prefer. I would suggest to make a jitsi call...
Dennis Schey
@trashcoder
jitsi is fine
Sebastian
@xemle

New Release

[1.3.0] - 2021-08-27

Added

  • Add cast cli for a Chromecast-enabled slide show
  • server: Apply events on database load
  • server: Allow query parameter for database api
  • Add fetch command to fetch and merge a remote gallery

Changed

  • Use /api/database.json instead of /api/database
  • Use /api/events.json instead of /api/events

Fixed

  • database: Handle incomplete geo data
  • index: Fix graceful abort by user (ctrl-c)

[1.2.2] - 2021-08-18

Fixed

  • Fix test execution on parallel streams
  • Fix logger colors for terminals with color level 1 (16 colors)
  • index: Fix error handling on checksum calculation

[1.2.1] - 2021-08-08

Fixed

  • Fix cli logger call
0x62646f727465
@peakaboo:matrix.org
[m]
Hello
I am discovering home-gallery
Tonight
I am thrilled by what you’ve done around this!
1 reply
Congratulations
May I tip you with Ethereum ?
0x62646f727465
@peakaboo:matrix.org
[m]
I mean Sebastian do you have an Ethereum wallet
1 reply
Steffen Roller
@sroller
I'm trying to create a Docker container on a Raspberry Pi4. I cloned the github repo and ran Docker build ...
The command throws a lot of warnings about outdated npm packages and eventually fails. It also pulls a node-14 base image. Is it safe to change that? Or has somebody already done it? I couldn't find a pre-built image for the Pi4 hence my question.
Steffen Roller
@sroller
eg.
npm WARN deprecated chokidar@1.7.0: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated highlight.js@9.18.5: Support has ended for 9.x series. Upgrade to @latest
npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated opn@6.0.0: The package has been renamed to open
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
n
Sebastian
@xemle
@sroller Thank you for trying HomeGallery. And I am sorry to reply so late. Unfortunately I do not receive a active trigger if someone posts something here. Please apologize.
Regarding the npm WARN messages: They come from the transitive dependencies and it is hard to avoid them. So they are "normal".
Regarding node v14 that should be fine. The upcoming release supports also the current LTS of node v16
Sebastian
@xemle
Regarding Raspberry Pi 4: The official docker image supports arm64 architecture. Which architecture is your docker on your PI running?
Sebastian
@xemle

New Release

[1.4.0] - 2022-03-26

This release adds tags from XMP sidecar files, enhances the media search
capabilities, adds support to use native commands like ffmpeg, extracts preview
files from RAW images and adds support to HEIC files (from iphones).

Added

  • docker: Support arm docker images
  • bundle: Add all-generic bundle
  • cli: Configuration for max memory value for database creation
  • extractor: Create only smaller preview images than the source
  • extractor: Option to use native system executables like vipsthumbnail or ffmpeg
  • extractor: Add support for heic/heif image format
  • extractor: Extract embedded previews from raw files
  • query: Add cmp, (all) in list and range to common properties
  • query: Allow capitalized keywords
  • database: Add entry groups
  • database: Add updated timestamp
  • database: Support IPTC keywords as tags
  • index: Improve journal for sidecar changes
  • server: Add optional basic authentication of users and ip whitelists
  • webapp: Add a tab to list tags (by biolds)
  • extractor: Add option for geo address server
  • extractor: Add error threshold for api calls
  • cast: Add reverse option

Changed

  • Default node version is v16 (Gallium)
  • extractor: Reduce log levels. Use debug log level for details
  • cast: Set default order is by date oldest first

Fixed

  • cli: Fix update with source selection
  • extractor: Fix resizing to squared boundary size
  • query: Fix query expression with keyword prefix like india or andrea
  • extractor: Except buggy Samsung images (by psdimon)
  • query: Fix query expressions with parenthesis
  • database: Unify city geo information from hamlet, village, town
  • fetch: Improve error handling for events
mom4mom🔞
@MostLikelyToRun_twitter
I don't know if I'm doing something wrong, but I'm trying to use the self-extracting Win64 binary and it keeps failing with the error "EPERM: operation not allowed", just for mkdir. Running as administrator from command line with full explicit permission given, antivirus and Defender are both off.
Sebastian
@xemle
Mm. That sounds strange. The selfextracting is done via the caxa project. Maybe they have an issue for Windows.
In theory caxa extracts the files below the (global) temporary directory tmp\caxa\home-gallery
Sebastian
@xemle
An alternative is to use the archive and call the gallery.js manually. This overcomes also issues with partials cleanups of the temporary directory
mom4mom🔞
@MostLikelyToRun_twitter
Yeah, I just switched to the archive. Didn't figure anything else out, not sure what's going on.
Sebastian
@xemle
OK. Glad you found a solution.
I use caxa as simple selfextracting binary from a archive which does its job mostly. But it becomes tricky to support anti virus programs or auto-cleanup of tmp dorectories. So not every case is covered by the caxa solution.
if you think you have a valuable solution for Windows to share, I would like to add it to the documentation
mom4mom🔞
@MostLikelyToRun_twitter
Actually I do have something to add to this. I was poking around with it the other day and found that it will actually extract when on the main drive, C. But despite full permissions given, it gave me the error when extracting to my external drive (USB), which is what I was trying to do the first time. File structure of the external drive didn't matter, I tried doing exFAT, NTFS with full permissions, etc. Not sure what to make of that exactly.
Sebastian
@xemle
I dont think it is the media source drive.mkdir should only happen for the config dir or for the preview media storage. Where are they located?
mom4mom🔞
@MostLikelyToRun_twitter
The self-extracting archives themselves were in a single-depth directory either way, and would fail before extracting anything. So in C:\homegallery or D:\homegallery. It succeeded when on the same drive as the OS.
Sebastian
@xemle
so you say if HomeGallery works well when the the self-extracting app is installed on the same drive as the photos?
Eg. everything is on drive C: or everthing is on drive D: the gallery works as expected
But when the app drive and the photo drive is different, the gallery fails? Eg app is on drive C: and the photos are on drive D:
Sebastian
@xemle
I am curious how to reproduce this failing behavior. Unfortunately I am an Linux and can not check the issue easily. It whould help (me) if you could describe the failing and the succeeding scenario for that issue.
Further, I assume that this issue is solved on your side by using the tar.gz bundle/archive, extracting the app files by your own and this mkdir issue disappears. Did I understand you correctly?
mom4mom🔞
@MostLikelyToRun_twitter
Running the self-extractor downloaded from the website causes the mkdir error is it is on an external drive without configuring photo drives and gallery drives.
And yes, extracting it manually works fine.
*mkdir error if it is
Sebastian
@xemle
so to reproduce: download self-extraction binary to an external drive, execute it and than it fails. Right?
mom4mom🔞
@MostLikelyToRun_twitter
That's right. Unfortunately I no longer have access to a PC at the moment, but I might be able to try it again in a couple days on the same device.
Sebastian
@xemle
that would be awesome. As I said earlier I use Linux but would like to add some valuable FAQs to the documentation to cover your issue and workaround. So every info like the exact (reproducable) setup, error messages, screenshot of error etc could help.
Thanks again for reporting the issue and this discussion
mom4mom🔞
@MostLikelyToRun_twitter
Sure thing. No problem, thanks for listening and wanting to fix it!