Oops, you're right! I had something there and deleted it before posting :)
Added a short sentence now, thanks for the heads up!
mlunar
joined 2 years ago
Hehe, alright, no worries! If you change your mind the PRs are open :)
๐ค you got it! Mascots are underrated!
Hi! Thanks a lot for trying it out!
I manage all my apps via docker compose, so I'm actually less familiar with TrueNAS apps, so I'm happy that setup was quick :) Would you be interested in contributing a short guide on the setup?
When viewing a snapshot, highlight files (and possibly folders) that differ from the current state (deleted files in red, modified files in yellow, for example)
Yeah, I was thinking something along those lines as well. Maybe being able to "diff" between two snapshots as well, for example to see what was changed in a snapshot compared to its predecessor. Would be cool to have file diffs as well :)
Downloading entire folders, that would probably require timeship to zip them up beforehand, though.
Yeah, that would be nice too. I think archiving / zipping multiple files or folders on the fly is fairly straightforward in Go, it's just the matter of putting in the time to make it happen.
If you have any other ideas, let me know! Or open an issue directly :)
Some of the other things I was thinking of are just in the README roadmap, but I'll move them to issues soon enough I guess
You don't need a "platform" if you just want a simple blog. I don't know your values, but you can check mine: https://lnar.dev/blog/blog-setup/
I'm just getting my feet wet really, but I love that setup. The only change since that post is that I use Obsidian for editing (and some minor extension changes). It's a shame Obsidian is not FOSS, but it also doesn't matter as there is no lock-in and easy to switch.
Thanks! Hmm, not sure what you mean, that I shouldn't install devDependencies when building the release? That's a good point, I'll need to look into it
Oh interesting! Thanks for explaining :)
Thanks for the explanation, makes sense! This app relies quite heavily on in-memory caches, so it's somewhat incompatible with that model :)
That said, I wonder if the startup time would be noticeable. Depends a lot on the configuration, but it shouldn't take more than a few 100ms (esp. if you use skip_collection_counts).
Thx! Out of interest, what is your use case?
I don't know a lot about fastcgi, but looking it up it seems like it also keeps a persistent process running to avoid execution overhead, but I don't know how that process is managed ๐คทโโ๏ธ
Either way, you could use a supervisor of sorts that shuts down the process/container after some idle time (at least for containers I know some exist) and that should probably work fine (outside of interrupting scanning operations).
I haven't tried it myself yet though :)
view more: next โบ
There's an easy solution to that problem: grab a camera and get crackin'! ๐