Page MenuHomeFreeBSD

sysutils/sylve: new port, lightweight GUI for managing jails, zfs, net
Needs RevisionPublic

Authored by dch on Aug 23 2025, 3:14 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Mar 10, 1:20 AM
Unknown Object (File)
Sat, Feb 21, 12:40 PM
Unknown Object (File)
Sat, Feb 21, 2:31 AM
Unknown Object (File)
Fri, Feb 20, 10:09 AM
Unknown Object (File)
Feb 2 2026, 2:16 AM
Unknown Object (File)
Dec 31 2025, 2:40 AM
Unknown Object (File)
Dec 24 2025, 6:52 AM
Unknown Object (File)
Dec 24 2025, 3:12 AM

Details

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 66882
Build 63765: arc lint + arc unit

Event Timeline

dch requested review of this revision.Aug 23 2025, 3:14 PM
dch created this revision.

NB this is still WIP, we need to add in the typescript UI for embedding still.

minor tweak to appease poudriere test

Based on the patch provided by acm@, I removed the -r flag from daemon(8) and everything related to it. The reason is that, for example, if sylve fails for any reason, daemon(8) keeps restarting it over and over again, filling up /var/log/daemon.log. I think it's better to let sylve fail and let the user see what happened.

add acm@ patch to prepare and bundle npm assets

@acm thanks your patch handles the web bits already? awesome :-) I'd suggested to @hayzam_gmail.com that he could generate those
directly as part of his own release process.

pouria requested changes to this revision.Dec 2 2025, 10:54 AM
pouria added a subscriber: pouria.
pouria added inline comments.
sysutils/sylve/files/sylve.in
11–13

Set the real default value here please

This revision now requires changes to proceed.Dec 2 2025, 10:54 AM
hayzam_gmail.com added inline comments.
sysutils/sylve/files/patch-config.example.json
7

The correct json key here is "dataPath", there are some more options in, we might need to update this file too as there are things that changed in config.example.json

sysutils/sylve/files/pkg-message.in
26

I think we can get rid of these (_enable) lines, let Sylve manage the life cycle of these services on its own (if the user does enable them at the initialization step), as they might depend on things like bridges created by Sylve