-
Notifications
You must be signed in to change notification settings - Fork 33
Add documentation for new Spoolman Rock-on #554
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 1 commit
03634ac
569f27d
33c12c3
07783a7
c413c73
61bab54
8f831c3
c6098b5
0efce32
e5e4e7a
3b1f0f7
9bbf891
815104e
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,124 @@ | ||||||||||||||||
| .. _Spoolman_rockon: | ||||||||||||||||
|
|
||||||||||||||||
| Spoolman Rock-on | ||||||||||||||||
| ============= | ||||||||||||||||
MikeMcPherson marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||||||||||||
|
|
||||||||||||||||
| Before you install Spoolman, you should understand the prerequisites | ||||||||||||||||
| and configurations common to all Rockstor :ref:`rockons_intro`; | ||||||||||||||||
| specifically the :ref:`rockons_preinstall` and :ref:`rockons_root` | ||||||||||||||||
| requirement. | ||||||||||||||||
|
|
||||||||||||||||
|
|
||||||||||||||||
| .. _Spoolman_whatis: | ||||||||||||||||
|
|
||||||||||||||||
| What is Spoolman | ||||||||||||||||
| ----------------- | ||||||||||||||||
|
|
||||||||||||||||
| From the author's repository description: "Spoolman is a self-hosted web service designed | ||||||||||||||||
| to help you efficiently manage your 3D printer filament spools and monitor their | ||||||||||||||||
| usage. It acts as a centralized database that seamlessly integrates with | ||||||||||||||||
| popular 3D printing software like OctoPrint and Klipper/Moonraker. | ||||||||||||||||
| When connected, it automatically updates spool weights as printing progresses, | ||||||||||||||||
| giving you real-time insights into filament usage." | ||||||||||||||||
|
|
||||||||||||||||
| For more information go to https://github.com/Donkie/Spoolman. Be sure to check for | ||||||||||||||||
| compatibility with your print system. | ||||||||||||||||
MikeMcPherson marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||||||||||||
|
|
||||||||||||||||
|
|
||||||||||||||||
| .. _Spoolman_install: | ||||||||||||||||
|
|
||||||||||||||||
| Installing Spoolman Rock-on | ||||||||||||||||
| ---------------------------- | ||||||||||||||||
| The Spoolman Rock-on requires a Rockstor share to use as the object store. | ||||||||||||||||
| You should create this share in a pool with sufficient space for your needs | ||||||||||||||||
| before beginning the Spoolman Rock-on installation. | ||||||||||||||||
|
|
||||||||||||||||
| Once your share is ready, click the "Install" button next to the Spoolman listing | ||||||||||||||||
| on the Rock-ons page. | ||||||||||||||||
|
|
||||||||||||||||
| .. image:: /images/interface/docker-based-rock-ons/Spoolman_rockons.png | ||||||||||||||||
| :width: 100% | ||||||||||||||||
| :align: center | ||||||||||||||||
|
|
||||||||||||||||
|
|
||||||||||||||||
| .. _Spoolman_share: | ||||||||||||||||
|
|
||||||||||||||||
| Spoolman Share | ||||||||||||||||
| ^^^^^^^^^^^^^^^^ | ||||||||||||||||
| Specify the share you created for Spoolman. | ||||||||||||||||
|
|
||||||||||||||||
| .. image:: /images/interface/docker-based-rock-ons/Spoolman_share.png | ||||||||||||||||
| :width: 100% | ||||||||||||||||
| :align: center | ||||||||||||||||
|
|
||||||||||||||||
| The Spoolman docker app does not run as root, so you must change the | ||||||||||||||||
| ownership of the share so that the user is the same as the user you | ||||||||||||||||
| created when installing Rockstor (the "admin" user) and the group is | ||||||||||||||||
| "users". Give group full permissions, as well. | ||||||||||||||||
|
Comment on lines
+54
to
+57
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It might be worthwhile to mention that the admin:users should have the corresponding UID:GID of 1000:1000 in case that mapping changes in the future. What do you think @phillxnet?
Suggested change
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I like your wording better.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @Hooverdan96 re:
Agreed. The admin user is likely to be 1000, but not guaranteed; plus explicit is best and it is the UID that is canonical for docker, not the user. We also have a partial unknown: group 1000 is from CentOS et-al (users), I don't think our "Built on openSUSE" base even have one out of the box (users group is 100 here). It may be that the user is all that matters here. Otherwise folks have to create a place-holder group of 1000 as we can only assign named groups to Shares. But if all works OK with Share owner as user 1000 only, we are good and can also use the -1 uid Rock-on element.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [EDIT] just check on a buildbot worker we use to prove stuff and it has the first use as buildbot, akin to a normal install where the first created non-system user is uid 1000: So in that case the Web-UI admin user would then be 'other' than 1000, in this case I see: But a regular install on our new openSUSE base results in the following for the Web-UI setup created user:
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We can drop the group permissions instruction; it was really "belt and suspenders". I just tested and it works fine leaving GID and group permissions at the default.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm leaning back to my original wording for the share owner. It seems to me that the one thing the admin does control is the username they picked when they install Rockstor. What do you think? |
||||||||||||||||
|
|
||||||||||||||||
| .. image:: /images/interface/docker-based-rock-ons/Spoolman_shareowner.png | ||||||||||||||||
| :width: 100% | ||||||||||||||||
| :align: center | ||||||||||||||||
|
|
||||||||||||||||
| .. _Spoolman_environment: | ||||||||||||||||
|
|
||||||||||||||||
| Spoolman Environment | ||||||||||||||||
| ^^^^^^^^^^^^^^^^^^^^^^ | ||||||||||||||||
| Spoolman needs a value for one environment variable, the timezone | ||||||||||||||||
| to be used when time-stamping database entries. Specify the timezone | ||||||||||||||||
| in the standard tzdata format, for example "America/New_York". | ||||||||||||||||
|
|
||||||||||||||||
| .. image:: /images/interface/docker-based-rock-ons/Spoolman_environment.png | ||||||||||||||||
| :width: 100% | ||||||||||||||||
| :align: center | ||||||||||||||||
MikeMcPherson marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||||||||||||
|
|
||||||||||||||||
|
|
||||||||||||||||
| .. _Spoolman_port: | ||||||||||||||||
|
|
||||||||||||||||
| Spoolman Port | ||||||||||||||||
| ^^^^^^^^^^^^^^^^^^^^^^ | ||||||||||||||||
MikeMcPherson marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||||||||||||
| Spoolman needs to know what TCP port you would like to assign to the Web | ||||||||||||||||
| admin interface. Select a port that is not currently in use on your | ||||||||||||||||
| RockStor server. | ||||||||||||||||
MikeMcPherson marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||||||||||||
|
|
||||||||||||||||
| .. image:: /images/interface/docker-based-rock-ons/Spoolman_port.png | ||||||||||||||||
| :width: 100% | ||||||||||||||||
| :align: center | ||||||||||||||||
|
|
||||||||||||||||
|
|
||||||||||||||||
| .. _Spoolman_verify: | ||||||||||||||||
|
|
||||||||||||||||
| Spoolman Verify and Submit | ||||||||||||||||
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||||||||||||||||
MikeMcPherson marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||||||||||||
| Verify the information you've provided is correct, then click "Submit". | ||||||||||||||||
|
|
||||||||||||||||
| .. image:: /images/interface/docker-based-rock-ons/Spoolman_submit.png | ||||||||||||||||
| :width: 100% | ||||||||||||||||
| :align: center | ||||||||||||||||
|
|
||||||||||||||||
| You'll see screens indicating the Rock-on is being installed. Click "Close". | ||||||||||||||||
|
|
||||||||||||||||
| .. image:: /images/interface/docker-based-rock-ons/Spoolman_installing.png | ||||||||||||||||
| :width: 100% | ||||||||||||||||
| :align: center | ||||||||||||||||
|
|
||||||||||||||||
| .. image:: /images/interface/docker-based-rock-ons/Spoolman_inprogress.png | ||||||||||||||||
| :width: 100% | ||||||||||||||||
| :align: center | ||||||||||||||||
|
|
||||||||||||||||
|
|
||||||||||||||||
| .. _Spoolman_success: | ||||||||||||||||
|
|
||||||||||||||||
| Spoolman Installation Successful | ||||||||||||||||
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||||||||||||||||
MikeMcPherson marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||||||||||||
| Congratulations! You can click the red "Spoolman UI" button or open a Web browser | ||||||||||||||||
| and navigate to `http://ROCKSTOR-IP:PORT-NUMBER` to go to the Spoolman Web | ||||||||||||||||
| management interface. There you can begin to create and manage your filament library. | ||||||||||||||||
MikeMcPherson marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||||||||||||
|
|
||||||||||||||||
| .. image:: /images/interface/docker-based-rock-ons/Spoolman_success.png | ||||||||||||||||
| :width: 100% | ||||||||||||||||
| :align: center | ||||||||||||||||
|
|
||||||||||||||||
| .. image:: /images/interface/docker-based-rock-ons/Spoolman_homepage.png | ||||||||||||||||
| :width: 100% | ||||||||||||||||
| :align: center | ||||||||||||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as mentioned in the rst below this screenshot won't be necessary anymore, since you adapted the Rockon definition to not ask for a timezone anymore, but automatically will use the system timezone.