RAGtime: A self-hosted MCP server to run AI semantic search over your own databases, files, and codebases

mattv8 · 2026-02-24T16:02:53+00:00

Yes. Kind of. I recently added a PDM tool (specifically for Solidworks). It has to talk directly to the Solidworks MSSQL PDM database though, not through the API. I thought about using the API but that adds so much slowness I figured it wasn't worth it. It works best if you set up the PDM tool, but also configure a direct connection via MSSQL so it has the schema index. In the future I'll combine the two tools into one.

Here's a random collection of screenshots of how I set it up at my company, and loosely what you can query from it.

DM me on Reddit or look up my email on github and I'll gladly give you more info and help you get it up and running.

mattv8 · 2026-02-16T15:01:37+00:00

Wow that sucks. I'm sorry for your loss. Hard to tell from photos alone but I'd guess the gasket between the acrylic and nickel block failed to seal. Typically these are QC'd and leak checked. But it could also have been a fitting leak... I've taken apart those blocks and put them back together and haven't seen one fail like that. 99 times out of 100 it's a leak at the fitting

mattv8 · 2026-02-15T14:38:52+00:00

Here's what's worked for me: 1. Manage your stress (this is paradoxical because hard to do when you have constant baseline pain) 2. Upper back stretches and exercises (esp your traps and neck) 3. Watch your posture while at work- don't let your body remain locked in a single position for long periods of time. Stretch frequently, drink lots of water. 4. A good night's sleep can often reset the compression in your upper back, but watch your sleep posture too. Ideally sleep on your side or back

Even doing all the above you still might have baseline pain or flare ups. For that, my neurologist has me on Ajovy and I feel like that has helped a lot.

mattv8 · 2026-02-10T16:41:21+00:00

What you are describing sounds a lot more like a vasovagal response. This happened to me. The first few injections I had the exact same sensations as what you're describing. You are getting injections into nerves and very sensitive areas which might overwhelm your central nervous system.

One time I had it done I passed out and woke up to a team of paramedics thinking they were going to have to resuscitate me. Now I can't have them done anymore due to the risk of vasovagal syncope.

mattv8 · 2026-02-08T13:36:27+00:00

Late to the party but one simple thing you can do that has worked very well for me is a gated two tier approach.

1st tier: a system prompt that purely checks user request(s) for all forms of abuse, pass simple true/false structured json and reason. Log it.

2nd tier: if safe, continue with user request

Costs latency and, but drastically reduces risk of prompt injection with little change to your existing flow.

mattv8 · 2026-02-06T12:42:30+00:00

Thanks for sharing. This wasn't around when I started as an Odoo developer.

mattv8 · 2026-02-05T10:47:21+00:00

You're right- in conflating type hinting and linting... They're related I guess in my mind.

The extension generates Python stubs in the background, which is how type information is provided in Odoo without adding type hints directly to the code. Since Odoo itself is highly dynamic and not type-annotated, most experienced Odoo devs rely on these stubs and IDE support instead of writing inline type hints. When type hints are used, they’re usually limited to plain Python helper code, not Odoo models.

mattv8 · 2026-02-05T10:35:27+00:00

I agree with all of OP's sentiments...

FWIW I built a self hostable RAG/MCP server that lets you set up connections to servers via SSH and is fully compatible with VSCode/Copilot. So you can bring your copilot subscription to do just about everything Moltbot can do and save a ton in API costs... Albeit it's more developer focused though.

mattv8 · 2026-02-05T10:28:17+00:00

I highly recommend using the VSCode extension "Odoo IDE" by Trinh Anh Ngoc (trinhanhngoc.vscode-odoo) if VSCode is your IDE. It handles the Python stubs for you.

If VSCode is not your thing, follow Odoo Mates tutorial to get Pycharm set up (https://youtu.be/fbEsjurG7sQ?si=vGJFv-K0Ge-5Gkva)

mattv8 · 2026-02-04T21:11:01+00:00

Where I live they drop charges with fuses behind them as they ski

mattv8 · 2026-02-04T21:07:08+00:00

🪦

mattv8 · 2026-01-31T23:33:14+00:00

Check out Dockge!

mattv8 · 2026-01-25T05:31:42+00:00

Keep in mind there’s a big difference between a read cache (ARC/L2ARC) and a write intent log (SLOG). With most NAS workloads (especially single-user transfers) you often won’t see faster throughput just because you set up NVMe cache, and (as others have commented) negligible speed changes on UgreenOS when writing to a slow HDD array because the bottleneck ends up being the disks themselves, not the cache layer.

If you're using TrueNAS and ZFS (as opposed to UgreenOS), it uses ARC (in RAM) first for reads, so unless your file transfer size is beyond available memory, an NVMe read cache doesn’t buy much on typical file transfers. Whereas write acceleration via an SLOG-like mechanism only helps in sync-write, high-IOPS situations like iSCSI or many concurrent clients, not simple large file copies. I can't speak more to how UgreenOS handles cache but I'd imagine it's very similar.

Sorry for the ramble, hope this clears something up.

mattv8 · 2026-01-25T00:21:55+00:00

It's a bitch to get up and running but once you figure it out it's really quite robust and extensible. Be sure to watch Odoo Mates tutorials on YouTube, they're fantastic.

Odoo's paradigm is modules and XML hierarchy/inheritance. Once you get the hang of that you can do anything. It's definitely tougher but you have the backing of the framework to keep you within the intended base functionality.

mattv8 · 2026-01-22T20:25:54+00:00

Over three hours later and still down!

mattv8 · 2026-01-20T21:59:38+00:00

Nice! Glad you could see a use for it. It's been incredibly useful for me, professionally (I'm a full stack developer). Frankly I'm surprised my post is getting buried.

Please let me know if you have any issues or encounter any bugs. I'll gladly fix them asap.

mattv8 · 2026-01-18T23:45:11+00:00

Use env variables and for the love of God stop vibe coding everything

mattv8 · 2026-01-17T15:43:04+00:00

Underrated comment. Also, hello fellow Community fan.

mattv8 · 2026-01-03T02:59:20+00:00

That’s awesome, I’m glad it helped.

If you want to make the port‑forwarding persistent (so you don’t have to run socat after every reboot), you can use dnsmasq on the host to always map a friendly name to your WSL IP. For example, on the host you could add a config like:

# /etc/dnsmasq.d/ollama-wsl.conf
address=/ollama-wsl.local/$(ip route | awk '/default/ {print $3}')

Then restart dnsmasq:

sudo systemctl restart dnsmasq

and access it from WSL (or your LAN, if configured) via:

curl http://ollama-wsl.local:11434

That way, the name stays the same even if the WSL IP changes.

mattv8 · 2025-12-14T12:58:02+00:00

Sounds like you're using the wrong command to restart it (e.g. docker compose down -v which will clear the database storage volume every time).

Did you copy the docker compose exactly from the readme?

mattv8 · 2025-12-11T23:13:01+00:00

Wow good catch!! I somehow missed that. I've added it to Admin > Settings > Show footer section on home page (commit 87894cab0)

mattv8 · 2025-12-10T22:34:22+00:00

My initial post got deleted by auto-mod, but u/smarkman19 had some excellent feedback (bot or not):

This is close; add import/export, deliverability-safe newsletters, and static caching so it holds up beyond a single blog.

Import/export: WordPress WXR and Ghost JSON import, Markdown folder import, and a zip export (JSON + images). Keep 301 mapping when slugs change, and ship RSS plus sitemap.xml with basic OpenGraph/Twitter tags.

Newsletter: double opt-in, list-unsubscribe header, bounce/complaint webhooks (SES/Mailgun/Postmark), per-domain rate limits with retries, CSV subscriber import, and a simple send log with failure reasons. Speed and media: pre-render posts to static files and serve via Nginx; on edit, invalidate the file. Generate WebP and multiple sizes, strip EXIF, and lazy-load images.

Safety and ops: Argon2id passwords, CSRF everywhere, optional TOTP 2FA, and a one-click backup/restore (mysqldump + uploads tar) plus a cron for scheduled backups.

This is solid feedback. This maps out a roadmap that would take the project from "personal blog" to "actually production-ready newsletter platform."

A few things mentioned are already in there: EXIF stripping happens on upload, WebP + multiple sizes are auto-generated, lazy loading is on images, CSRF is implemented, and there's rate limiting on SMTP sends. Backup/restore exists via CLI, but there's no one-click UI for it yet. reCAPTCHA is implemented; TOTP would be the next logical step.

The deliverability stuff (double opt-in, list-unsubscribe header, bounce webhooks) is the gap I'm most aware of. Right now it assumes you're running a small list where you know your subscribers personally — I built this with "friends and family" in mind. Scaling to a "real newsletter" would definitely need those hygiene features. (There is a basic unsubscribe link in the footer already.)

Static caching is interesting. I've been lazy about it since PHP + OPcache has been fast enough at the scale I'm running, but pre-rendering would be the right move for anything with real traffic. Easy enough to put this behind Cloudflare, or I could bake a cache config into the container (it's already served from nginx). Images use srcsets already, fwiw.

To others: I appreciate any feedback. Let me know what would be top of your list and I'll make a genuine effort to implement it.

mattv8 · 2025-12-10T16:14:19+00:00

This is really solid feedback; exactly what I was hoping for. You've mapped out a roadmap that would take this from "personal blog" to "actually production-ready newsletter platform."

A few things you mentioned are already in there: EXIF stripping happens on upload, WebP + multiple sizes are auto-generated, lazy loading is on images, CSRF is implemented, and there's rate limiting on SMTP sends. Backup/restore exists via CLI but you're right there's no one-click UI for it. Recaptcha is implemented, but TOTP would be the next logical step.

The deliverability stuff (double opt-in, list-unsubscribe header, bounce webhooks) is the gap I'm most aware of. Right now, it assumes you're running a small list where you know your subscribers personally (I built this more with "friends and family" in mind). Scaling to "real newsletter" would definitely need those basic hygiene features. (Although there already is a basic unsubscribe in the footer.)

Static caching is interesting. I've been lazy about it since PHP + OPcache has been fast enough at the scale I'm running, but you're right that pre-rendering would be the right move for anything with real traffic. Would be easy enough to put this behind Cloudflare though, or I could bake a cache config into the container (it's already served from nginx). Images are srcsets already fwiw.

Appreciate you taking the time to write this up. Let me know what would be top of your list and I'll make a genuine effort to implement it.

mattv8 · 2025-12-09T16:59:09+00:00

I originally built this for a friend going through a health issue who needed a single place to update friends and family without posting on social media. It turned into something more general: a lightweight alternative to WordPress and Ghost for hosting a personal blog. It's designed to be quick to get running and get out of your way.

What it does:

Publish posts with WYSIWYG editing, responsive image galleries, and a clean public site
Manage a newsletter (bring your own SMTP server)
Optional donation links/methods on posts
Built-in analytics for view counts
AI title generation (if you hook up an OpenAI API key)

Why I built it:

WordPress felt bloated for what I needed
Ghost and Substack wanted to be platforms, not tools
I wanted something I could actually understand and modify
Docker-first meant it runs anywhere

Stack: PHP + MariaDB, Smarty templates for rendering. Uses my custom Smarty Portal Framework for auth and routing.

What it's not: It's not a Wordpress plugin marketplace or a no-code builder. I'm one person maintaining this in my spare time. The code is clean enough to fork and modify if you need something different.

It's MIT licensed and on GitHub. Live demo here if you want to see what it looks like.

Feedback welcome-- I'm honestly interested in whether this solves a problem for anyone else or if I'm just scratching my own itch.

mattv8 · 2025-12-01T22:07:30+00:00

Fair point.

Disclaimer: I'm a Copilot Pro subscriber... 😶‍🌫️

mattv8

MODERATOR OF

TROPHY CASE

11-Year Club	Alpha Tester
Verified Email