Thank you for your comments hayzam (npub1mkd…p9nh). I must admit I'm a bit puzzled, though.
I had assumed most people took it for granted that, even if there isn't an automatic import mechanism (which, personally, I tend to distrust), there would at least be a documented manual migration/integration checklist.
Something outlining exactly what Sylve expects, where each piece of data belongs, and in what format, so administrators can populate the required data, migrate or clone datasets, adjust paths, and so on.
I understand this isn't particularly relevant for new deployments, but I'd expect anyone already running services in jails or VMs to think twice before deploying Sylve if there's no documented migration path.
Thank you for all your work so far ✌️
Ricardo Martín :bsdhead:
npub1dr…j38l0
2026-07-30 13:30:20 UTC
in reply to nevent1q…0zdu
Author Public Key
npub1drx03fy5ec0j0mskne3jct2urqa4xwty46tlzm996yc46l66rfpq3j38l0Seen on
wss://relay.momostr.pinkPublished at
2026-07-30 13:30:20 UTCEvent JSON
{
"id": "d2f83266d402b544eb6d1b7c822fd43e86fa38dad75f3f7ad473e7f865fc93fb",
"pubkey": "68ccf8a494ce1f27ee169e632c2d5c183b533964ae97f16ca5d1315d7f5a1a42",
"created_at": 1785418220,
"kind": 1,
"tags": [
[
"e",
"d6e8b0f6bab214fe770fee6c86e0f9b6f7307d4c26e6b66077c22afc4acbf9eb",
"",
"reply",
"dd9b383bbc433f1f63d0e041db703134b482a10771e5f9af3cfe7cc41049cb7a"
],
[
"e",
"c35547517b3eee8657de807708c850a86ea318b7fdf45ef9cea59989c0f94116",
"",
"root",
"68ccf8a494ce1f27ee169e632c2d5c183b533964ae97f16ca5d1315d7f5a1a42"
],
[
"proxy",
"https://mastodon.bsd.cafe/@ricardo/117009168473879144",
"web"
],
[
"p",
"dd9b383bbc433f1f63d0e041db703134b482a10771e5f9af3cfe7cc41049cb7a"
],
[
"p",
"68ccf8a494ce1f27ee169e632c2d5c183b533964ae97f16ca5d1315d7f5a1a42"
],
[
"proxy",
"https://mastodon.bsd.cafe/users/ricardo/statuses/117009168473879144",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://mastodon.bsd.cafe/users/ricardo/statuses/117009168473879144",
"pink.momostr"
],
[
"-"
]
],
"content": "Thank you for your comments nostr:npub1mkdnswaugvl37c7supqakup3xj6g9gg8w8jlnteule7vgyzfedaqjtp9nh. I must admit I'm a bit puzzled, though.\n\nI had assumed most people took it for granted that, even if there isn't an automatic import mechanism (which, personally, I tend to distrust), there would at least be a documented manual migration/integration checklist.\n\nSomething outlining exactly what Sylve expects, where each piece of data belongs, and in what format, so administrators can populate the required data, migrate or clone datasets, adjust paths, and so on.\n\nI understand this isn't particularly relevant for new deployments, but I'd expect anyone already running services in jails or VMs to think twice before deploying Sylve if there's no documented migration path.\n\nThank you for all your work so far ✌️",
"sig": "f062e3fa44440063a81dea273755bf5732f89df9383b82592467e7b87ea6fdc4f552c378b2aafb6afc72bbbe8176fe9433674fbd81b2a6e63f7e38623a3d4dbb"
}