search

helfrichmichael / prusaslicer-novnc

Simple Docker container that serves Prusaslicer via noVNC in your web browser.
52 stars 20 forks source link

[FR] Option to select a specific PS Release #3

Open P-C-R opened 2 years ago

P-C-R commented 2 years ago

Right now it's using the latest on the release page. As the time of the writing 2.4.1 beta 1

Would be nice to select at least between stable and beta

For me beta is fine ;) and i always opt for it.

On another note

A super slicer docker would be nice too for all the voron user out there.

helfrichmichael commented 2 years ago

For the latter part of this request, I've got a superslicer-novnc container nearly working (https://github.com/helfrichmichael/superslicer-novnc)!

https://github.com/supermerill/SuperSlicer/issues/2323 is open due to a weird behavior on launch that's causing repetitive crashing. Nothing stands out in the logs, but I'm assuming it's a missing GTK dependency, just not sure what.

helfrichmichael commented 2 years ago

Update to my last comment, @P-C-R . I've successfully built a Superslicer Docker :).

https://github.com/helfrichmichael/superslicer-novnc you can give it a whirl and let me know what you think.

Next task will be allowing beta/stable selection for the Prusaslicer offering.

Tuncay-Ayhan commented 1 year ago

Update to my last comment, @P-C-R . I've successfully built a Superslicer Docker :).

https://github.com/helfrichmichael/superslicer-novnc you can give it a whirl and let me know what you think.

Next task will be allowing beta/stable selection for the Prusaslicer offering.

How is the progress going? What is the correct way to just define a prerelease (url) in the Dockerfile instead of polling the latest release.?

helfrichmichael commented 1 year ago

Update to my last comment, @P-C-R . I've successfully built a Superslicer Docker :). https://github.com/helfrichmichael/superslicer-novnc you can give it a whirl and let me know what you think. Next task will be allowing beta/stable selection for the Prusaslicer offering.

How is the progress going? What is the correct way to just define a prerelease (url) in the Dockerfile instead of polling the latest release.?

Ideally I'll just keep rolling builds out as Prusa rolls PrusaSlicer out since if a build is bad, you could always fall back to a previous known working version (in theory).

If this seems to become a problem, I am certainly opening to generating a separate Docker container for the pre-release offerings, etc.

Tuncay-Ayhan commented 1 year ago

Update to my last comment, @P-C-R . I've successfully built a Superslicer Docker :). https://github.com/helfrichmichael/superslicer-novnc you can give it a whirl and let me know what you think. Next task will be allowing beta/stable selection for the Prusaslicer offering.

How is the progress going? What is the correct way to just define a prerelease (url) in the Dockerfile instead of polling the latest release.?

Ideally I'll just keep rolling builds out as Prusa rolls PrusaSlicer out since if a build is bad, you could always fall back to a previous known working version (in theory).

If this seems to become a problem, I am certainly opening to generating a separate Docker container for the pre-release offerings, etc.

Wouldn't be possible to use an environment variable to choose the version?

example docker-compose.yml (partly)

environment:
     - VERSION=version_2.6.0-alpha6

but the default should be the latest stable release.