Provide .deb packages

[ilovethensa]

Description

Would make installing on docker-less environments way easier

Desired Behavior

Provided .deb files

Additional Context

No response

Code of Conduct

• I agree to follow Jellyseerr's Code of Conduct

[joshuaboniface]

Agreed, willing to take this on.

[joshuaboniface]

So, Debian packaging here is going to be quite difficult to do "properly", as splitting the various parts out into Debianlized folders seems to be impossible.

I can do a hacky alternative though of putting everything under /opt/jellyseerr, which isn't quite as nice (and wouldn't be accepted to an upstream) but will work for now.

[Fallenbagel]

So, Debian packaging here is going to be quite difficult to do "properly", as splitting the various parts out into Debianlized folders seems to be impossible.

I can do a hacky alternative though of putting everything under /opt/jellyseerr, which isn't quite as nice (and wouldn't be accepted to an upstream) but will work for now.

How about something similar to the AUR package? Is that doable? Where the config folder is symlinked?
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=jellyseerr#n60

[joshuaboniface]

That is possible, but I don't think it's good practice to do so.

[joshuaboniface]

The other issue would be packaging the node_modules in the .deb which makes it huge. I'm trying to see if there's a way around that but I'll need to do some more reading into how to properly package NodeJS projects in Debian.

[joshuaboniface]

Just for context: the big difference between a .deb and the AUR is that AUR packages are built on the client machine at install, while .debs are built remotely and the full binaries are sent. This is running into problems with node_modules because it tries to do a lot of .deb magic on them and fails. So there has to be a better way here, but I'm also thinking that this might not be entirely possible, at least not in a clean way that won't result in a 1.6+GB(!) .deb.

[Fallenbagel]

Just for context: the big difference between a .deb and the AUR is that AUR packages are built on the client machine at install, while .debs are built remotely and the full binaries are sent. This is running into problems with node_modules because it tries to do a lot of .deb magic on them and fails. So there has to be a better way here, but I'm also thinking that this might not be entirely possible, at least not in a clean way that won't result in a 1.6+GB(!) .deb.

I guess at that point and install script would be better then? 🤔

[joshuaboniface]

I've done some more digging, and for simple NodeJS projects, https://github.com/heartsucker/node-deb seems like a good solution. But from what I've seen of it Overseerr (and hence Jellyseerr) is not simple. Most of all, the fact that the node_modules dir is over 1.6GB pretty much precludes making a sensible .deb here, as that entire thing needs to be included. We just don't have the AUR benefit of running things like yarn build at install time.

So I definitely think an installer script is the better bet here.