Some ideas or features to implement about borgwarehouse HOT 9 CLOSED

Hi @shadowking001 ! A little teasing to tell you that the Apprise feature is coming soon 🤩

It takes time because even if it doesn't look like it, it's a lot of work. And I also had to discover and learn how Apprise works in order to successfully integrate this functionality.

The feature will be ready in the next few days, I will keep you informed here.

I hope you will like it ☺

from borgwarehouse.

Hello,

Nice addition, sorry I couldn't help you, I've been very busy these last weeks.
Of course I'll try it as soon as it will be released.

from borgwarehouse.

@shadowking001 🎉 https://github.com/Ravinou/borgwarehouse/releases/tag/v1.4.0 🎉

from borgwarehouse.

Hello,

I tried your apprise implementation, work flawlessly with the test notification.
I'm gonna set some repos in the next few days to see how it behaves, but it seems promising, good job ;)

from borgwarehouse.

Thank you for your ideas.

• Apprise : I didn't know this software. Basically, in the idea, you provide a URL to BorgWarehouse (say in the user account settings for example), and this URL is called in case of down ?

• Docker : The subject is very vast and complex and requires time. This is a longer term topic but I will be back in the next few months I hope.

• Documentation : can you open a specific issue for this please and give me more detail. I can't reproduce. Thanks.

• Group devices : I had the same idea for the use of tags. I thought about list ranking criteria but it's not very practical and functional. I have retained the idea of tags and I think it's the next project after the status notifications.

• Database : Maybe one day, but I know that the idea of having a database to manage borgwarehouse can also bother some people. It is resources (electrical, carbon and hardware), extra backups and maintenance, just for a repository list and some user settings... .

Ideally I'd like to offer both and choice for user (json or database), but it's still too early to do/plan today. BorgWarehouse is still young and I have other priorities like notifications or user interface (sorting...)

Have a good night !

from borgwarehouse.

• Concerning Apprise, you have two options, you can directly use the binary to send notifications based on logs or commands executed, up to you, to whatever notification service.
  Or, people can install Apprise by their own means, and BWH would use the API through curl. That's what I do with my Valheim server and hooks on events :

         ## Bootstrap
         - 'PRE_BOOTSTRAP_HOOK=curl -X POST -d "tag=botValheim&body=Server starting up..." http://apprise-api:8000/notify/apprise'
         ## Listening
         - 'POST_SERVER_LISTENING_HOOK=curl -X POST -d "tag=botValheim&body=Server __READY__..." http://apprise-api:8000/notify/apprise' 
         ## Shutdown
         - 'PRE_SERVER_SHUTDOWN_HOOK=curl -X POST -d "tag=botValheim&body=Shutting down server..." http://apprise-api:8000/notify/apprise'
         ## Restarting
         - 'PRE_RESTART_HOOK=curl -X POST -d "tag=botValheim&body=Restarting server..." http://apprise-api:8000/notify/apprise'

Jan 28 05:45:19 supervisord: valheim-server 2023-01-27 22:45:19,318 [INFO] apprise: Loaded 3 entries from memory://
Jan 28 05:45:19 supervisord: valheim-server 2023-01-27 22:45:19,318 [INFO] apprise: Notifying 1 service(s) asynchronously.
Jan 28 05:45:19 supervisord: valheim-server 2023-01-27 22:45:19,571 [INFO] apprise: Sent Discord notification.

You can almost do whatever you want. This Valheim docker image is not built to be used with Apprise, its integration is seamless.

• For the login problem, I'll open an issue, sure.

• Concerning InfluxDB, I think there is a misunderstanding, InfluxDB is Time Series Database that would be totally optionnal. Sending information to InfluxDB is just done with curl : https://docs.influxdata.com/influxdb/v1.8/guides/write_data/. Then people can build their own dashboard with Grafana, formatting data as will. Something like this should never be mandatory. ;)

from borgwarehouse.

Or, people can install Apprise by their own means, and BWH would use the API through curl. That's what I do with my Valheim server and hooks on events

Interesting, in the idea I can allow you in the account settings to enter your Apprise API URL and I trigger the curl on the backend in case of down so that you receive the notification. But I guess your API is secured with a password to put in the CURL header ?

I can add this function if you help me to test it because I don't have an Apprise service ;)

from borgwarehouse.

Hello,

Interesting, in the idea I can allow you in the account settings to enter your Apprise API URL and I trigger the curl on the backend in case of down so that you receive the notification. But I guess your API is secured with a password to put in the CURL header ?

Yeah, being able to select things like :

• Scheme
• Host
• Port
• Tag

should do the trick, at least for an alpha roll.
I'm not sure I'm using it at its best, so I'll give another shot to the documentation.

But I guess your API is secured with a password to put in the CURL header ?

It's not, by design, see https://github.com/caronc/apprise-api#api-notes
The secured transit is done from Apprise to your notification service(s). Usually, for such a use case, you put your containerized app and apprise-api in a same network, only both of them can see the data.

from borgwarehouse.

@shadowking001 Remember to check that your sudoers file is correct, because there were some changes and it is now versioned here: https://github.com/Ravinou/borgwarehouse/blob/main/docs/sudoers/10-borgwarehouse

So I also use Apprise now and send my notifications to a personal Matrix instance. It's great. It was a lot of work and a big feature over several days and hundreds of lines of code, but I'm proud of it !

from borgwarehouse.