Adding OctoEverywhere Support#210
Conversation
|
This is being discussed in issue #203 |
|
This is just a personal thought @paxx12 and @QuinnDamerell I would be interested to see your thoughts on implementing this. https://github.com/jbatonnet/Rinkhals Jbonnet implemented an app style system to help keep things "apps" centralized using scripts system. I was talking with him on the discord and from what I can understand about the code he shared it should be possible to just implement it on any system with similar chips which the U1 does. Here is the app system and @QuinnDamerell it has some maybe helpful stuff for octoeverwhere support. https://github.com/jbatonnet/Rinkhals.apps https://github.com/jbatonnet/Rinkhals.Apps/tree/master/apps/octoeverywhere I only mention this because alot of what has been implemented seems extreemly close to what this group of people has been trying to do with the K3 and K3m. I think he has a similar philosophey of making sure that he does not touch the main firmware but only add files that are easy to uninstall. The apps can be disabled and enabled from the GUI. |
|
Not sure if it is helpful or means much in relation to how you would like to carry out the U1 but thought it may provide helpful script work for easy installing of and use of octoeverywhere |
|
@cdvankammen I would personally prefer to have some internal support for |
|
So for anything we want to add into the future you are wanting to make it like mac where everything is included in a single run application? if I am not mis understanding? |
|
@cdvankammen Not all, some. The |
|
I'm going to mark this as open because, from my perspective, it has everything OE needs. Please let me know if there are any edits, changes, or different patterns you would rather me use, and I can update them. Is there an easy way for me to build the firmware locally with these changes to actually test them end-to-end? |
I guess this is a question for you @paxx12 |
|
@QuinnDamerell look at |
185989f to
6421036
Compare
| @@ -28,6 +28,7 @@ vpn: none | |||
| # klipper_exporter: :9101 | |||
|
|
|||
| [octoeverywhere] | |||
There was a problem hiding this comment.
This is part of remote_access:. Maybe we should name it cloud: none, octoeverywhere?
|
@QuinnDamerell I think I would like to see this follow that pattern:
I would also want that WDYT about those changes? |
|
That's the biggest thing I was wondering about. I didn't want to put it as remote access because it's more than that. So I think cloud would be a good common root. |
|
@QuinnDamerell Yes, I think this is part of |
400ee84 to
7e7ae2d
Compare
✅ Build ArtifactsVersion:
|
|
@paxx12 I moved all of the docs to a cloud.md doc and moved the config options to remote_access -> cloud. The only thing I need to do now is figure out how to set up the firmware_config page with the settings and grep for the account linking URL. |
|
It should look more or less like this: settings:
remote_access:
label: Remote Access
items:
vpn:
label: Cloud Access
get_cmd:
- /usr/local/bin/extended-config.py
- get
- /home/lava/printer_data/config/extended/extended2.cfg
- remote_access
- cloud
- none
options:
none:
label: None
cmd:
- bash
- -xc
- |
/usr/local/bin/extended-config.py add /home/lava/printer_data/config/extended/extended2.cfg remote_access cloud none &&
/etc/init.d/S99cloud stop
octoeverywhere:
label: OctoEverywhere
cmd:
- bash
- -xc
- |
/usr/local/bin/octoeverywhere-pkg download &&
/usr/local/bin/extended-config.py add /home/lava/printer_data/config/extended/extended2.cfg remote_access cloud octoeverywhere &&
/etc/init.d/S99cloud restart &&
/usr/local/bin/octoeverywhere up --timeout=60s # to pull the access tokens
default: noneCreate in a place similar as current |
✅ Build ArtifactsVersion:
|
✅ Build ArtifactsVersion:
|
✅ Build ArtifactsVersion:
|
385116c to
137eb05
Compare
✅ Build ArtifactsVersion:
|
✅ Build ArtifactsVersion:
|
✅ Build ArtifactsVersion:
|
✅ Build ArtifactsVersion:
|
✅ Build ArtifactsVersion:
|
|
@QuinnDamerell Please allow this PR to be edited. I do have some changes that I want to push. |
|
@paxx12 Hmm, I'm trying to figure out how to do that, I don't see the option |
|
Maybe I can't because it's based on my repo? |
|
Ok. You can't, since this is forked into organization, not user profile. |
|
Closed in favor of the #244 |
This is my first attempt at adding OctoEverywhere support to the firmware. Feel free to ask for any edits or changes you want. I roughly modeled it off the Tailscale, Monitoring, and Moonraker services/integrations.
Testing
TODO
Please provide feedback! @paxx12