And how testable is that solution? Sure macros are helpful but testing and debugging them is a mess
- 1 Post
- 9 Comments
To run perhaps. But what about the same metrics for debugging? How many hours do we spend debugging c/c++ issues?
witx@lemmy.sdf.orgto Selfhosted@lemmy.world•Friendly reminder that Tailscale is VC-funded and driving towards IPOEnglish6·6 天前Because it offers much more than just VPN even though that’s what most users use it for. Read their documentation and you’ll see
You are amazing. Such a great response!
You don’t seem great at taking decisions
Not sure, I use it containerised though
Thank you all, I was able to solve the issue as said here https://lemmy.sdf.org/comment/20412456
I also wanted to mention that normally Immich dumps its own db into a file backup file somewhere. I forgot where. Check the database dump backup cron job in the settings
Hi, thank you. This was the solution. Immich was storing its backup files to DB_UPLOAD (as defined on the .env) file. There will be a backup folder with a bunch of .sql.gz files) Picked one and ran the following command
gunzip --stdout “/path/to/backup/dump.sql.gz”
| sed “s/SELECT pg_catalog.set_config(‘search_path’, ‘’, false);/SELECT pg_catalog.set_config(‘search_path’, ‘public, pg_catalog’, true);/g”
| docker exec -i immich_postgres psql --dbname=postgres --username=<DB_USERNAME>As documented on immich’ s website
Yes I mean mocking, faking, et. al. Not this particular library but macros in general