-
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
Merged
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
03634ac
Add documentation for new Spoolman Rock-on
MikeMcPherson 569f27d
Update interface/docker-based-rock-ons/spoolman.rst to remove referen…
MikeMcPherson 33c12c3
Update interface/docker-based-rock-ons/spoolman.rst to change line br…
MikeMcPherson 07783a7
Update interface/docker-based-rock-ons/spoolman.rst to change line br…
MikeMcPherson c413c73
Update interface/docker-based-rock-ons/spoolman.rst to change line br…
MikeMcPherson 61bab54
Update interface/docker-based-rock-ons/spoolman.rst to fix Sphinx und…
MikeMcPherson 8f831c3
Update interface/docker-based-rock-ons/spoolman.rst to fix Sphinx und…
MikeMcPherson c6098b5
Update interface/docker-based-rock-ons/spoolman.rst to fix Sphinx und…
MikeMcPherson 0efce32
Update interface/docker-based-rock-ons/spoolman.rst to fix Sphinx und…
MikeMcPherson e5e4e7a
Add Spoolman to overview.rst
MikeMcPherson 3b1f0f7
Fix format error introduced in previous commit
MikeMcPherson 9bbf891
Remove environment screen shot
MikeMcPherson 815104e
More toc link to correct section
MikeMcPherson File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,117 @@ | ||
| .. _Spoolman_rockon: | ||
|
|
||
| Spoolman Rock-on | ||
| ================ | ||
|
|
||
| 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. | ||
|
|
||
|
|
||
| .. _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. | ||
|
|
||
| .. image:: /images/interface/docker-based-rock-ons/Spoolman_shareowner.png | ||
| :width: 100% | ||
| :align: center | ||
|
|
||
| .. _Spoolman_environment: | ||
|
|
||
| Spoolman Environment | ||
| ^^^^^^^^^^^^^^^^^^^^ | ||
| Spoolman does not need any environment variable defined. | ||
|
|
||
|
|
||
| .. _Spoolman_port: | ||
|
|
||
| Spoolman Port | ||
| ^^^^^^^^^^^^^ | ||
| 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. | ||
|
|
||
| .. image:: /images/interface/docker-based-rock-ons/Spoolman_port.png | ||
| :width: 100% | ||
| :align: center | ||
|
|
||
|
|
||
| .. _Spoolman_verify: | ||
|
|
||
| Spoolman Verify and Submit | ||
| ^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
| 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 | ||
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
| 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. | ||
|
|
||
| .. 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 | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
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?
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.
I like your wording better.
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.
@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.
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.
[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:
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.
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.
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.
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?