Package for FreeBSD

[h-2]

Hey,

I am running FreeBSD on my server which does not support Docker (or at least it doesn't support running Linux Docker images atm).

I successfully managed to use the Linux prebuilt package, but I'd like to add a native Port to the FreeBSD-Ports collection. This requires running the respective build steps on package build. Since I didn't find any manual install instructions, I did some guessing and came up with yarn install --frozen-lockfile --production and yarn build.

The first command runs fine:

[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
warning "@excalidraw/excalidraw > @radix-ui/react-tabs@1.0.2" has incorrect peer dependency "react@^16.8 || ^17.0 || ^18.0".
warning "@excalidraw/excalidraw > @radix-ui/react-tabs@1.0.2" has incorrect peer dependency "react-dom@^16.8 || ^17.0 || ^18.0".
warning "@excalidraw/excalidraw > @radix-ui/react-tabs > @radix-ui/react-context@1.0.0" has incorrect peer dependency "react@^16.8 || ^17.0 || ^18.0".
warning "@excalidraw/excalidraw > @radix-ui/react-tabs > @radix-ui/react-direction@1.0.0" has incorrect peer dependency "react@^16.8 || ^17.0 || ^18.0".
warning "@excalidraw/excalidraw > @radix-ui/react-tabs > @radix-ui/react-id@1.0.0" has incorrect peer dependency "react@^16.8 || ^17.0 || ^18.0".
warning "@excalidraw/excalidraw > @radix-ui/react-tabs > @radix-ui/react-presence@1.0.0" has incorrect peer dependency "react@^16.8 || ^17.0 || ^18.0".
warning "@excalidraw/excalidraw > @radix-ui/react-tabs > @radix-ui/react-presence@1.0.0" has incorrect peer dependency "react-dom@^16.8 || ^17.0 || ^18.0".
warning "@excalidraw/excalidraw > @radix-ui/react-tabs > @radix-ui/react-primitive@1.0.1" has incorrect peer dependency "react@^16.8 || ^17.0 || ^18.0".
warning "@excalidraw/excalidraw > @radix-ui/react-tabs > @radix-ui/react-primitive@1.0.1" has incorrect peer dependency "react-dom@^16.8 || ^17.0 || ^18.0".
warning "@excalidraw/excalidraw > @radix-ui/react-tabs > @radix-ui/react-roving-focus@1.0.2" has incorrect peer dependency "react@^16.8 || ^17.0 || ^18.0".
warning "@excalidraw/excalidraw > @radix-ui/react-tabs > @radix-ui/react-roving-focus@1.0.2" has incorrect peer dependency "react-dom@^16.8 || ^17.0 || ^18.0".
warning "@excalidraw/excalidraw > @radix-ui/react-tabs > @radix-ui/react-use-controllable-state@1.0.0" has incorrect peer dependency "react@^16.8 || ^17.0 || ^18.0".
warning "@excalidraw/excalidraw > @radix-ui/react-tabs > @radix-ui/react-id > @radix-ui/react-use-layout-effect@1.0.0" has incorrect peer dependency "react@^16.8 || ^17.0 || ^18.0".
warning "@excalidraw/excalidraw > @radix-ui/react-tabs > @radix-ui/react-presence > @radix-ui/react-compose-refs@1.0.0" has incorrect peer dependency "react@^16.8 || ^17.0 || ^18.0".
warning "@excalidraw/excalidraw > @radix-ui/react-tabs > @radix-ui/react-primitive > @radix-ui/react-slot@1.0.1" has incorrect peer dependency "react@^16.8 || ^17.0 || ^18.0".
warning "@excalidraw/excalidraw > @radix-ui/react-tabs > @radix-ui/react-roving-focus > @radix-ui/react-collection@1.0.1" has incorrect peer dependency "react@^16.8 || ^17.0 || ^18.0".
warning "@excalidraw/excalidraw > @radix-ui/react-tabs > @radix-ui/react-roving-focus > @radix-ui/react-collection@1.0.1" has incorrect peer dependency "react-dom@^16.8 || ^17.0 || ^18.0".
warning "@excalidraw/excalidraw > @radix-ui/react-tabs > @radix-ui/react-roving-focus > @radix-ui/react-use-callback-ref@1.0.0" has incorrect peer dependency "react@^16.8 || ^17.0 || ^18.0".
warning " > @rcode-link/tiptap-drawio@1.0.21" has unmet peer dependency "@tiptap/core@^2.0.0-beta.220".
warning " > @rcode-link/tiptap-drawio@1.0.21" has incorrect peer dependency "@tiptap/pm@^2.0.0-beta.220".
warning "@rcode-link/tiptap-drawio > @tiptap/extension-image@2.27.1" has unmet peer dependency "@tiptap/core@^2.7.0".
warning " > @tiptap/extension-bubble-menu@3.13.0" has unmet peer dependency "@tiptap/core@^3.13.0".
warning " > @tiptap/extension-code-block@3.13.0" has unmet peer dependency "@tiptap/core@^3.13.0".
warning " > @tiptap/extension-highlight@3.13.0" has unmet peer dependency "@tiptap/core@^3.13.0".
warning " > @tiptap/extension-image@3.1.0" has unmet peer dependency "@tiptap/core@^3.1.0".
warning " > @tiptap/extension-link@3.13.0" has unmet peer dependency "@tiptap/core@^3.13.0".
warning " > @tiptap/extension-table@3.13.0" has unmet peer dependency "@tiptap/core@^3.13.0".
warning " > @tiptap/extension-task-item@3.13.0" has unmet peer dependency "@tiptap/extension-list@^3.13.0".
warning " > @tiptap/extension-task-list@3.13.0" has unmet peer dependency "@tiptap/extension-list@^3.13.0".
warning " > @tiptap/extension-text-align@3.13.0" has unmet peer dependency "@tiptap/core@^3.13.0".
warning " > @tiptap/extension-text-style@3.13.0" has unmet peer dependency "@tiptap/core@^3.13.0".
warning " > @tiptap/react@3.13.0" has unmet peer dependency "@tiptap/core@^3.13.0".
warning "@tiptap/react > @tiptap/extension-floating-menu@3.13.0" has unmet peer dependency "@floating-ui/dom@^1.0.0".
warning "@tiptap/react > @tiptap/extension-floating-menu@3.13.0" has unmet peer dependency "@tiptap/core@^3.13.0".
warning " > @tiptap/suggestion@3.13.0" has unmet peer dependency "@tiptap/core@^3.13.0".
warning " > recharts@3.6.0" has unmet peer dependency "react-is@^16.8.0 || ^17.0.0 || ^18.0.0 || ^19.0.0".
warning " > tailwind-scrollbar@4.0.2" has incorrect peer dependency "tailwindcss@4.x".
warning Workspaces can only be enabled in private projects.
warning Workspaces can only be enabled in private projects.
[4/4] Building fresh packages...
Done in 6.80s.

But the build command fails:

yarn run v1.22.19
$ next build && node scripts/postbuild.js
⨯ Failed to load next.config.mjs, see more info here https://nextjs.org/docs/messages/next-config-error

> Build error occurred
Error: Cannot find package '@serwist/turbopack' imported from /usr/home/hannes/devel/jotty/next.config.mjs
    at ignore-listed frames {
  code: 'ERR_MODULE_NOT_FOUND'
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I am new to the whole node ecosystem, so maybe I am on the wrong track altogether.

If you don't have time for this, feel free to ignore, but I thought it would be nice to have a native FreeBSD package for this :)

[fccview]

Hey, you almost got it, the issue with running it locally is that some of the Dev packages will be required, I don't fully understand why next 16 behaves this way, it was never a problem in next 14.

If you remove that --production flag it'll build properly, however you'll end up with all the node modules junk.

Have a look at my workaround in the build phase to get that linux pre-build package in the release, it should be everything you need ♥️

https://github.com/fccview/jotty/blob/main/.github/workflows/prebuild-release.yml

[fccview]

I actually looked into this the other day and totally forgot to reply. Sorry!

Can you try adding a .babelrc file in the root of the project and put this in it

{
  "presets": ["next/babel"]
}

Then run

yarn install --frozen-lockfile

And lastly

yarn build

If this works I'll see if I can script it for the poor future souls running into the same issue haha

[h-2]

Thanks! I did it, but same problem as before.

Like I said, I believe I have the problem that a dependency just isn't available for FreeBSD. But maybe we can avoid that somehow?

[fccview]

Well that was my idea of a workaround, I was forcing the build to use the Babel presets.

I think the issue is that turbopack doesn't work on freebsd , I was trying to see if next would be smart enough to work around it with these preset being forced but I think due to using serwist for the pwa turbopack is being forced in there.

Next16 relies on it anyway, so I'm not entirely sure how to realistically sort this out. If you want to do some research I'd check how to run next 16 with webpack instead of turbopack on a freebsd environment.

Unfortunately I'm still in hospital, I don't have Jotty setup on my laptop for development as I usually work on it directly from my homelab (which is not remotely accessible via ssh)

Long story short, this may take me a while to help you out with, all I can do is theorise with you for now haha

[h-2]

Sorry to hear, and no worries at all!

The core of the problem is swc-project/swc#10106 and I don't see us fixing that. Some people seem to have used workarounds through WASM, but they also don't seem easy to replicate.

I will meditate on this a bit, but I think the easiest solution is just using the prebuilt linux package via FreeBSD's linux-binary-compat. It means that development on FreeBSD will be difficult, but deployment should be easy (even if it means pulling in useless linux binary compat packages).

Regarding LDAP, I will see if I find a spare hour on my work laptop (which runs Linux and Claude 😉 ).

[fccview]

Let me know what you cook up and I'll happily review and help as soon as I have more capacity ❤️

[h-2]

So, I have setup Jotty on my Work laptop which runs Linux/aarch64. Since not all dependencies are available on aarch64, I expected the yarn install to fail. Interestingly, yarn converted the project to yarn-4.1.0 and then decided to build all missing dependencies, which took 45min(!).
An important thing is that this changes the lock file, so --frozen-lockfile is not supported.

However, I have hopes that it might work on FreeBSD with a newer version of yarn, as well. FreeBSD is currently still at 1.2...

[h-2]

I have now created a Port for the FreeBSD ports collection:
https://github.com/h-2/freebsd-ports/blob/add_jotty/www/jotty-page/

But it's not yet submitted. Could you have a look if it looks good to you?

In particular, I'd had to do two things to make the builds reproducible (or at least the filenames stable):

1. Fixing the build-ID
2. Fixing an ACTION_KEY

Maybe those changes would be interesting to you?

Also, I am not sure whether all of the 3000+ files really need to be shipped?

Thank you for your time!

edit: posted this message in the wrong place before

[fccview]

hey!
I am not 100% sure what i'm looking at, not gonna lie, i have never had to deploy anything on freeBSD, but i can say that your link market as 1 is missing about half the file (ends abruptly on line 13 for some reasons).

Regarding the 3k files, i think you may need them indeed, it seems like you are packaging the entire codebase and doing it this way means you will need all of the node_modules dependencies...

I feel a little useless on this particular task as I don't know enough about freebsd, sorry

[h-2]

I am not 100% sure what i'm looking at, not gonna lie, i have never had to deploy anything on freeBSD,

Well, it's just Makefile plus some patches, and a file-list etc. Just thought you might spot some obvious-to-you problems in the Makefile regarding some environment variables that I am setting correctly or incorrectly 😅

your link market as 1 is missing about half the file

That's a diff 😆 It adds generateBuildId to the nextConfig. This (in combination with the ACTION_KEY) is needed to make the filenames deterministic. Or are you using some other mechanism for this?

Regarding the 3k files, i think you may need them indeed, it seems like you are packaging the entire codebase and doing it this way means you will need all of the node_modules dependencies.

Yeah, I wasn't complaining. I just wondered whether everything is necessary, but if it is, it is! Or is there another way to package this where it is not needed, but still self-contained?

I feel a little useless on this particular task as I don't know enough about freebsd, sorry

No worries, thanks for your time!

[fccview]

Fucking hell i was from mobile and hadn't even noticed that was a diff 😆 I'm so sorry!
Just finally managed to look at it from my laptop and can see a bit more of what you are trying to do with that makefile!

You can remove all of these at least, but it's really not that big of a deal

%%DATADIR%%/.eslintrc.json
%%DATADIR%%/.github/...
%%DATADIR%%/.vscode/...
%%DATADIR%%/CLAUDE.md
%%DATADIR%%/CONTRIBUTING.md

The makefile looks good and the env vars you are using are correct, you can add an increased body size limit if you want with JOTTY_BODY_SIZE_LIMIT=100mb if you want, that'll probably come in handy whenever you decide to upload any files to a note.

Everything looks good to me for as much as I can understand of it now that I have more of a bigger picture lol

[h-2]

No worries, and thanks for checking! I don't think it's worth it to mess with the file list, if it only affects those few files. I'll have a look at JOTTY_BODY_SIZE_LIMIT (what's the default right now?) and then submit this to FreeBSD!

[fccview]

1MB is the default and it can't be changed, there's a bug in nextjs for stuff served the way Jotty is, so I added a patch (very much like the one I did for FreeBSD) to bump it up haha