Skip to content
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

Added Portainer Agent #123

Open
wants to merge 103 commits into
base: master
Choose a base branch
from

Conversation

Willem-Dekker
Copy link

Added Portainer Agent this allows you to connect your stack to a other Portainer instance/ server

Willem-Dekker and others added 3 commits January 2, 2020 21:32
Added Portainer Agent this allows you to connect your stack to a other Portainer instance/ server
fix for username not equal pi
@gcgarner
Copy link
Owner

Hi Willem

Thanks for the PR. Could you please send me a link to the setup process for the agent so I can make a wiki entry

Gitea is a lightweight implementation of a Git server. Makers who are
already running a local IOTstack server may prefer to commit their work
to a local repository running on their Raspberry Pi, rather than
GitHub/GitLab/etc. Implementing Gitea under the IOTStack umbrella
inherits the existing IOTstack backup mechanisms for free.

Candidate page for the wiki at
https://www.dropbox.com/s/onqndgyamo2h74i/Gitea.md.zip?dl=1
@Willem-Dekker
Copy link
Author

Tomasmerca and others added 12 commits January 15, 2020 00:24
Route filter.acl to add the option in mosquitto/mosquitto.conf of filtering wich topics can be read or writen by defined users.
Added the file where the user creates filters.
The example filters don´t affect usage in any way.
Version "2" of the docker-compose.yml cannot use "Healthcheck" instructions.  Only 2.1+ can do this.  I propose we upgrade the version to at least 3 so we can incorporate HealthCheck commands and any other new features as appropriate.  We're running the latest version of docker - the latest version of the docker-compose.yml is 3.7 - unless there's a really, really good reason to use an older format of the docker-compose.yml, can we please update it to at least 3.0, preferably 3.7?
The url for the supervised HASSIO is changed, because the old one is resulting with error 404 and you cannot finish the installation
@Slyke
Copy link
Collaborator

Slyke commented Apr 19, 2020

I have submitted this PR on your behalf over at the fork: SensorsIot#2, If you would like to have your name to the commits, please submit the PR there and let me know so I can remove the PR I created on your behalf.

lepirlouit and others added 29 commits May 7, 2020 10:40
Added deconz install instructions and references
this ensures that no deCONZ container is created if a device is not plugged in (the user has chosen cancel) or selected from the deconz menu
added deconz device config menu and amended wiki accordingly
Inspired by discussion at
gcgarner#185 and
gcgarner#131 and similar.

Covers setting the time-zone for the container.

Recommends NOT attempting to change either the admin username or
password via environment variables and explains why. Also includes how
to recover from a lost admin password.

Discusses the how-to of overriding Grafana settings using the example
of enabling anonymous access.

Explains how to establish a "clean slate" state (a bit quicker than
completely deleting and re-installing IOTstack).
Grafana is pinned to version 6.3.6. There is no obvious reason.

I removed the pinning and Grafana advanced to 6.7.3. Some of the
Grafana user interface had moved around (eg the top level contained
a panel for the Grafana blog rather than the list of installed panels)
but things like that are to be expected. There were one or two cosmetic
changes in some of my dashboards (eg font size changes in bar charts)
but the panels all worked out-of-the-box and there was nothing that
suggested any need for caution in removing the pinning to 6.3.6.
…fana

Removes pin of Grafana to version 6.3.6.
deleted unnecessary echo's
Added troubleshooting text, new menu text and minor code cleanup
Fixed bug where yaml merging was overwriting deconz services
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet