arch1e

6 ms·

1.
by arch1e 2mo ago
As someone who tried to build a fairly large project with HTMX + Go, I can say it just wasn't there for me. Maybe it will get there eventually, but I'm not convinced. For simple CRUD apps and admin dashboards, HTMX is great. But o
2.
by arch1e 6mo ago
Yes! We're planning out terraform provider, It should land in v0.2.5, we're at v0.2.3 now.
3.
by arch1e 6mo ago
It's funny, I love how FreeBSD manages iSCSI even though I have only used it a few times, I put it in my to-do list but never really got around to writing a UI for it. Come next release (v0.3.0) I will definitely integrate it because a
4.
by arch1e 6mo ago
That’s fair, but Sylve isn’t GUI-only. We’re API-first, the UI is just a client on top. We already ship Swagger docs with the code (docs/ on the repo), so everything the UI does is exposed and usable programmatically today. Right now w
5.
by arch1e 6mo ago
Yeah, that’s pretty much been my experience as well. Last time I seriously used Proxmox with ZFS (I think 8.4.x), it felt a bit… bolted on. It works fine for the common VM workflows, but once you step outside that path, you end up dropping
6.
by arch1e 6mo ago
Yeah, I’m kind of in the same camp. I never really had issues with systemd either. It mostly just works, even if it’s a bit heavy. For me, moving to FreeBSD wasn’t about escaping systemd, it was more about the overall system design and how
7.
by arch1e 6mo ago
Author of Sylve here, and I helped deploy the setup in the post. > All I read is that they are still doing ClickOPS over DevSecOps!! Their setup is mostly working on embedded stuff, and this involves some amount of moving VM disk images
8.
by arch1e 6mo ago
OP here. It’s less about Sylve doing something Proxmox can’t do, and more about a bunch of QoL improvements that come from us being heavy Proxmox users and building what we felt was missing. A few concrete things: ZFS-first UX: Not just &
9.
by arch1e 6mo ago
That’s true, bhyve doesn’t support nested virtualization right now. In practice though, most setups don’t actually need it if you’re running workloads directly on the host. Also, if your goal is testing or simulating clusters, you can alrea
10.
by arch1e 6mo ago
OP here. One thing we mentioned in the blog but probably didn’t emphasize enough is how deeply ZFS is integrated into the UI. With Sylve, you rarely need to touch the CLI. Snapshots, datasets, ZVOLs, even flashing images directly to ZVOLs,
11.
by arch1e 6mo ago
LXCs are pretty similar to jails, and Sylve makes them really easy to use. One nice trick is that you can template a base jail and clone it any number of times straight from the UI, no need to drop into a shell and script it like I used to.
12.
by arch1e 6mo ago
That’s fair, but that kind of reinforces my point. If the expected recovery path is “wipe and reinstall,” then it’s clearly not just a thin layer on top of Debian. It’s effectively its own platform with its own assumptions, lifecycle, and u
13.
by arch1e 6mo ago
It’s not really just a fancy UI though. The entire Sylve bundle (backend + frontend) is ~55 MB, fully self-contained, and doesn’t mess with the base system in any destructive way. You can drop it in and remove it cleanly. Proxmox, on the ot
14.
by arch1e 6mo ago
It’s kind of funny, Debian was my distro of choice since I was 15, so about 10 years up until last year. I still envy its huge application ecosystem. But over time I’ve come to really appreciate simplicity and the principle of least astonis
15.
by arch1e 6mo ago
I would've given up on this project without Svelte 5! It’s so hard to justify React after using it. Proxmox always felt sluggish, but Sylve with Svelte stays smooth even on large clusters. DX is also much better. We started on Svelte 4
16.
by arch1e 6mo ago
Sylve Dev here! The port is in review and the maintainers has told me that it'll be merged into the next quarterly slush (which is next week). And the installation script on the website will automatically switch to ports when it's
17.
From Proxmox to FreeBSD and Sylve in our office lab(iptechnics.com)
98 points by arch1e 6mo ago|84 comments
18.
Show HN: Sylve – A management plane for FreeBSD (ZFS, VMs, jails, clustering)(sylve.io)
5 points by arch1e 6mo ago|0 comments
19.
by arch1e 7mo ago
Author here: I get where you’re coming from and long term, I agree. I don’t want FreeBSD to slowly turn into "Linux but different." For me though, the Linuxulator is about practicality today, not philosophy. It lets me use one or
20.
by arch1e 7mo ago
We build and sell multi-service business gateways, basically devices that do networking, VoIP, etc. all in one box. https://difuse.io/ if you're interested!
21.
Linuxulator on FreeBSD Feels Like Magic(hayzam.com)
7 points by arch1e 9mo ago|0 comments
22.
by arch1e 10mo ago
I'm curious, what hardware would you run it on?
23.
by arch1e 2y ago
I've been using Zen ( https://github.com/zen-browser ) for a while now, it's still in beta but is very cool.
24.
Show HN: Signify – FOSS tool to generate Email signatures (HTML and PNG)(signify.difuse.io)
9 points by arch1e 2y ago|4 comments
25.
Saving 100+ Desk Phones from E-Waste Doom with TFTP and a Simpler PBX(difuse.io)
19 points by arch1e 2y ago|0 comments
26.
by arch1e 2y ago
This would be awesome if we can export it to plain HTML. Things like the twitter icon doesn't make sense in the PNG that is exported?
27.
by arch1e 2y ago
> I'd want to keep the build step since I may pull markdown from other sources like I think astra allows. Pushing without building is not a difficult thing to do, in-fact it will make changes much faster too. But you mention pulling
28.
by arch1e 2y ago
We’re actively working on a feature to support deployment to Git-based repos, including GitHub Pages. Stay tuned!
29.
by arch1e 2y ago
I don’t think there’s an existing tool that handles Markdown and Git repos without requiring users to interact with Git directly. We’re currently developing a feature that allows you to push directly to Git from Kalmia. Instead of pushing M
30.
by arch1e 2y ago
Thank you for the feedback! I understand the confusion. Kalmia is indeed a server-side CMS, but its Go-based architecture allows it to be lightweight and run on various platforms, from cloud servers to smaller setups like Raspberry Pi. Thin

More ›