Direction of Statping and Statping-ng

[adamboutcher]

Hi All,

This is basically for a general discussion about statping and the statping-ng projects.

[adamboutcher]

We now have workflows/build/testing...

[adamboutcher]

Docker build failed but it looks like an os bug in the build host, going to change the build host os to solve that.

[adamboutcher]

Docker build seems to be building, will see if it uploads by morning.

[adamboutcher]

The docker build actually built but it failed on upload.

It looks like an auth timeout with docker hub,either it's new or my build box is slower than statping.

Theres some changes I'm going to make in the makefile which should ease this.

[adamboutcher]

We have a successful docker build of dev 😂💪

[adamboutcher]

Pushing for a stable build now.

[jemand771]

here's a list of all secrets used in the gha workflows:

• AWS_ACCESS_KEY_ID
• AWS_SECRET_ACCESS_KEY
• COVERALLS
• DISCORD_URL
• DOCKER_PASSWORD
• DOCKER_USERNAME
• EMAIL_HOST
• EMAIL_OUTGOING
• EMAIL_PASS
• EMAIL_PORT
• EMAIL_SEND_TO
• EMAIL_USER
• GITHUB_TOKEN
• GOTIFY_TOKEN
• GOTIFY_URL
• MJML_APP
• MJML_PRIVATE
• MOBILE_ID
• MOBILE_NUMBER
• POSTMAN_API
• PUSHOVER_API
• PUSHOVER_TOKEN
• SENTRY_AUTH_TOKEN
• SENTRY_URL
• SLACK_URL
• SNS_REGION
• SNS_SECRET
• SNS_TOKEN
• SNS_TOPIC
• TELEGRAM_CHANNEL
• TELEGRAM_TOKEN
• TEST_EMAIL
• TRAVIS_API
• TWILIO_FROM
• TWILIO_SECRET
• TWILIO_SID
• TWILIO_TO

I haven't looked into how exactly they're used and how to get them, but it looks like most of them are for deployment and automated tests. (I just regex'd for secret\.([a-zA-Z_]+) over all workflow files)

[adamboutcher]

Thanks, I'll try and figure out which is needed long-term, I've already got docker secrets in so it should start to make a build and upload them once the first workflow finishes successfully.

[adamboutcher]

I think as part of the build process there is a test against some of the notification services that use these secrets. I'm going to try and set some up and see if that's the case.

[DennisGaida]

Since this is the only location I found anything about „secrets“ - does statping-ng support docker secrets for all the sensitive stuff? if not I’ll open a fresh issue

[adamboutcher]

Going forwards; it would be good if any people that want to actively help maintain leave a reply, I think we'll need people across the board to either code or manage things.

I'm not a go developer, I don't manage software, im a sysadmin so I'm not highly qualified in that however I can read most code, get things passing builds etc so don't worry if you're not highly qualified in terms of go.

If we get lots of requests to be a maintainer, then I'll review any github history, we're after people that will be at least semi-active and not ignore issues for months and be the sole maintainer.

[adamboutcher]

Once I've got the dev builds sorted, I'll add other maintainers.

[jonathanrbarney]

I've used statping a bit in the past and it's been great, just kind of buggy on the more advanced features, which is why we are here.

• I'm a developer and most stuff I write on my own is golang/python/javascript in that order of preference.
• Not super familiar with github, but I use git daily, mostly on bitbucket.

If you have any golang questions with this whole setup/port feel free to ask me.

[adamboutcher]

Great! I'll start making groups/permissions/teams and start adding people to help contribute.

[Kovah]

I would like to opt-in for helping. Statping-NG is the only viable option for an uptime service with a working API and use it for one of my services. I already worked with Go, so could help a bit with programming. Also leading my own open source projects here on Github, so if you need help with organization and Github Actions, feel free to ask.

[adamboutcher]

Hi Kevin,

We'd be happy for some help!
Feel free to submit some PRs, if we're happy with your commits then we can look at adding you into the teams to have a bit more control etc.

[jemand771]

Since this is the intended chaos-thread anyway, I'm not making a new one. Question:

What's the intended workflow for contributing to a GitHub organisation project? statping-ng/statping-ng somehow refers to statping-ng/emails via its go dependencies, this makes forking them kind of awkward (I'd have to fork both, change the urls and hope that I don't actually commit them)

Not that I'd have anything to commit, I just wanted to tinker around and try to build statping locally at least once

[adamboutcher]

The statping-ng/emails looks to be a template for the email notification, I purely forked it incase we needed to make changes to it for a successful build and to reduce the dependancy on the original unmaintained statping.

You shouldn't need to fork emails for any significant work to statping-ng.

[adamboutcher]

I don't have any work flow ideas for contributions yet but you should only need to fork and push request like a normal repo, things like wiki edits etc I will have to provide access, will hopefully deal with that once I've got the initial build working.

[jemand771]

when i check out my fork of statping-ng/statping-ng locally, my IDE just tells me

go: github.com/statping-ng/emails@v1.0.0: parsing go.mod:
	module declares its path as: github.com/statping/emails
	        but was required as: github.com/statping-ng/emails

(command that was run: D:\Software\go-sdk\go1.16.3\bin\go.exe list -modfile=C:/Users/jeman/GolandProjects/statping-ng/go.mod -m -json -mod=mod all #gosetup)
have you seen this before while porting the project over? the error message is really confusing to me as statping-ng/emails does declare itself as github.com/statping-ng/emails which seems right

[adamboutcher]

the go.mod, try changing that to statping/emails instead? I think I might have reverted that change I made to get it to build to fix it later. Apologies, this is all new to me too :-)

[jonathanrbarney]

see #9

[BestGear-tech]

Hi - would it be possible to add MQTT as an alerting option?

[adamboutcher]

Hi, I can't see why not. If you can write go, then why not try it! If not, open an issue and we can add it and figure it out when we have time.