Habitat Plan Issue about reticulum HOT 8 CLOSED

We are still working to fix this. Any updates we release for public use will be on the Polycosm branch.

from reticulum.

@yk-eta Are you following the unstable channels on your hubs cloud instance?

As far as I'm aware, this should not affect hubs cloud users on the stable channels, so if you're seeing this issue that is surprising and might indicate another problem.

To check what channels you are following, look at the spec file for reticulum which should be on your instance at /hab/sup/default/specs/reticulum.spec

If you cat /hub/sup/default/specs/reticulum.spec, you should see

channel = "polycosm-stable-a"

If you see something else (polycosm-unstable-a or just unstable), then that is a problem and it would be helpful to share if you've ever opted into a beta or are doing anything unusual. If you're on the unstable channels, this is recoverable by following the instructions here: https://gist.github.com/johnshaughnessy/eca6719c6e920dcc22bce80369ad850e#how-do-i-revert-packages-to-the-stable-versions

But I'm concerned that if you didn't explicitly change this, then we need to check whether other Hubs Cloud users are encountering this problem as well.

from reticulum.

@johnshaughnessy I customized reticulum on master branch and recently pulling latest changes, I think on README.md, it does not clarify which branch is for hubs cloud.

from reticulum.

@pattersonbl2 ok, I will sync polycosm-stable branch next time

from reticulum.

it will just be the polycosm branch located here. I am not sure if you're running the reticulum locally or with hubs-cloud. You may run into issues with your code being overwritten by the stable or unstable channel unless you have configured your custom reticulum to track a different channel.

I can add a section in the readme to point to this branch, but we don't have many people to my knowledge running a custom reticulum server.

from reticulum.

@yk-eta Yes, it would definitely help to know a bit more about how you're deploying reticulum. Are you building habitat packages yourself for running on your Hubs Cloud instance? Definitely +1 to @pattersonbl2 's comment above. If you're building reticulum from source, it'll be safer to follow the polycosm branch rather than master. (And if you're also modifying hubs / spoke, the correct branches for those repos are called "hubs-cloud"). We try to keep those branches more stable for hubs cloud users, whereas our main branches update more regularly.

from reticulum.

In any case, I believe this issue should now be resolved because we uploaded the missing erlang/elixir packages and were able to build reticulum packages again. If that's not the case for you @yk-eta please feel free to reopen the issue because I might be mistaken.

from reticulum.

@johnshaughnessy is there any guide for creating AMI with customized reticulum service?

from reticulum.