Show HN: HortusFox – FOSS system for houseplants with enterprise-scale features
Show HN (score: 6)Description
That was possible because of the great community that evolved around this leafy project, that kept me motivated as well as supported me in a very kind and lovely way.
After a few months of no new version release, a few days ago I've published v5.3 of HortusFox, which provides some cool changes to help empower your plant parenting. You can see a very detailed changelog in the 5.3 release page on GitHub. Overall 25 issues have been resolved, where some of them were actually quite big.
If you're new to HortusFox: the system offers you a large number of features to support your plant parenting (or gardening) journey with plant details, locations, photos, default and custom plant attributes, inventory system, tasks system, calendar, history (to keep a memory of your leafy friends), collaborative group chat and a few opt-in features such as weather forecast or plant identification (via photo). It also offers an extensive REST API, backup feature and themes (if you want your workspace a little more personal).
I have to say, for me it's the perfect blend of two things: The passion for software development as well as the fondness for nature. I'm really grateful for that.
Thanks for reading and have a wonderful and leafy day.
More from Show
Show HN: Control Claude permissions using a cloud-based decision table UI
Show HN: Control Claude permissions using a cloud-based decision table UI We’ve been building visual rule engines (clear interfaces + API endpoints that help map input data to a large number of outcomes) for a while and had the fun idea lately to see what happens when we use our decision table UI with Claude’s PreToolUse hook.<p>The result is a surprisingly useful policy/gating layer– these tables let your team:<p>- Write multi-factor, exception-friendly policies (e.g. deny rm -rf / when --force; allow cleanup only in node_modules; ask on network calls like curl/wget; block kubectl delete or SQL DROP, each with a clear reason)<p>- Roll out policy changes instantly (mid-run, flip a risky operation from allow → ask; the next attempt across devs and agents is gated immediately– no git pull, agent restart, or coordination)<p>- Adopt lightweight governance that is somewhat agent agnostic and survives churn (MCP/skills/etc)- just add columns/rules as new tools and metadata show up<p>- Get a quick central utility to understand which tools are being used, which tools get blocked most often, and why
Show HN: Claude Code Scheduler
Show HN: Claude Code Scheduler I found myself frequently wanting to schedule tasks in Claude Code (both one-time and recurring) so I built a CC plugin to help with that.<p>To install: /plugin marketplace add jshchnz/claude-code-scheduler /plugin install scheduler@claude-code-scheduler<p>Then just tell Claude what you want (some examples):<p>Every Wednesday at 3am find dead code: unused functions, unreachable branches, commented-out code, and unused imports. List by file with line numbers.<p>Schedule a code review every weekday at 9am. Review commits from the last 24 hours, check for bugs, security issues, error handling gaps, and code that needs comments. Summarize with file:line references.
Show HN: Webctl – Browser automation for agents based on CLI instead of MCP
Show HN: Webctl – Browser automation for agents based on CLI instead of MCP
Show HN: Tsonic – A TypeScript to native code compiler via CLR and NativeAOT
Show HN: Tsonic – A TypeScript to native code compiler via CLR and NativeAOT
No other tools from this source yet.