printers-for-people / catboat

Improve your pronter, nyan!
GNU General Public License v3.0
21 stars 6 forks source link

Replace install scripts #8

Closed Jookia closed 2 weeks ago

Jookia commented 1 year ago

The current install scripts are kind of crufty, we should replace it with a standardized systemd unit and a guide on setting it up on a user's distribution.

Pre-installed distro images with all tools needed for running a printer should be provided elsewhere.

kozross commented 1 year ago

I would try and make the install instructions as distro-agnostic as possible. Nothing Klipper needs is distro-specific anyway.

Jookia commented 1 year ago

Should we include instructions for Mainsail and other stuff?

The workflow is basically:

  1. Make an account for Klipper
  2. Git clone some repos
  3. Make some python venvs
  4. Make the ~/printer_data tree
  5. Make some systemd services to run these
  6. Install nginx (distro-specific)
  7. Set nginx config (distro-specific)

I could sit down and just make a systemd portable service for this?

kozross commented 1 year ago

A portable service would be way, way easier.

Jookia commented 2 weeks ago

So it's been a year of running Catboat, hoorah! I'm running it on a weak Arch Linux RISC-V board, what about you?

My setup so far has been to put klipper, moonraker and mainsail in the home directory as user services, and use venvs as well as Arch packages to install Python dependencies.

The system side of things is a bit of a mess since I manually set up an Arch system, . But I also plan to install Catboat on an Armbian machine too.

I think making a portable service based on a container rootfs would be the best approach at this point, it would be cross-distro and allow easy updates and ensure we all have the same version at once. The Catboat bundle/distro would be designed to drop in and provide everything to get Klipper and Mainsail running. It wouldn't touch any host files and be easily removable.

However, this would have the downside of not supporting configuring the host system settings. Moonraker has an update manager which wouldn't work. It's arguably less valuable here too if the service is sandboxed: Any updates would be our image updates.

Packaging KlipperScreen is also probably not going to happen since it requires interaction with GUIs from a container space and hardware and honestly I'm not sure if it's worth the hassle given you can open the printer management on a laptop or phone which is going to be infinitely better experience wise. Tools like Mobileraker also integrate well apparently (I haven't tried it.)

People could still totally install KlipperScreen, it would just require more work.

I think also giving instructions for KIAUH would be a good move. It might not be the best solution, but it's very well supported in the community and Catboat can be used fairly well with it.

kozross commented 2 weeks ago

I reckon KIAUH in the short term is fine. I ultimately set mine up from scratch as well, because I'm like that, but KIAUH seems to have become the go-to solution.

Does it work outside of Debian's ecosystem?

Jookia commented 2 weeks ago

As far as I know, no.

On Mon, Nov 04, 2024 at 10:20:08AM -0800, Koz Ross wrote:

I reckon KIAUH in the short term is fine. I ultimately set mine up from scratch as well, because I'm like that, but KIAUH seems to have become the go-to solution.

Does it work outside of Debian's ecosystem?

-- Reply to this email directly or view it on GitHub: https://github.com/printers-for-people/catboat/issues/8#issuecomment-2455404626 You are receiving this because you authored the thread.

Message ID: @.***>

Jookia commented 2 weeks ago

I actually see that the README has install instructions, so I'll just close this for now.