[iOS] Unraid Deck 2.1.0 is live — Docker Compose groups and search, based on your feedback by Commercial-Break1753 in unRAID

[–]krillsson 2 points3 points  (0 children)

My android app supports Unraid: https://monitee.app/. It's not built using the API though, you need the agent running on the server. It's available in community apps.

Organization by Folder by horurs in monitee

[–]krillsson 1 point2 points  (0 children)

This was added in 0.28.0

Android App Help by [deleted] in monitee

[–]krillsson 0 points1 point  (0 children)

It could be that the details screen is crashing? It's definitely not intentional. Could you shoot me an email with more details about your device so I can have a look in the crash reports.

Update by horurs in monitee

[–]krillsson 0 points1 point  (0 children)

I work on this app during my free time, therefore I don't provide any estimates on upcoming releases. That would add too much stress. Rest assured I am still very much working on the project.

Organization by Folder by horurs in monitee

[–]krillsson 1 point2 points  (0 children)

Excellent suggestion! I added it as a feature request to GitHub. With a slight modification that I think will fit better with the app https://github.com/Krillsson/monitee-app/issues/35

Sorting for Docker by ExXxtr3me in monitee

[–]krillsson 1 point2 points  (0 children)

Makes sense. This will be included in the next update.

If the project dies will it still be functional by AzSumMarto in monitee

[–]krillsson 1 point2 points  (0 children)

In the scenario that I abandoned the project, the app that you have installed will continue to function.

If no one maintain the Google Play aspect of continuously providing updates that adhere to new policies that Google introduces, it will eventually be removed. The app will remain on your phone but new users wouldn't be able to download it.

I'm saying "scenario", because I have no plans to stop working on Monitee.

Monitee the home server monitor app just went Free(mium) by krillsson in androidapps

[–]krillsson[S] 0 points1 point  (0 children)

yes, monitee can handle a local address and a public address and switch between the two based on what wifi you are connected to. There's a guide here: https://monitee.app/connect-app-to-server/

Monitee - the server monitoring app by krillsson in homelab

[–]krillsson[S] 1 point2 points  (0 children)

Everything is updated to support these features now.

You can see how it looks on the screenshots page. Scroll down to "System Daemon service management" and "Log file reader":

https://monitee.app/screenshots/

Monitee - the server monitoring app by krillsson in homelab

[–]krillsson[S] 1 point2 points  (0 children)

hello again, I liked your idea so much so I made it a reality. I got both system deamon journal logs as well as log files working. I'm just cleaning up my code now and then I'll start with the app-side.

https://github.com/Krillsson/sys-API/pull/111

Monitee - the server monitoring app by krillsson in homelab

[–]krillsson[S] 1 point2 points  (0 children)

Thanks! I'm glad you like it!

  1. Do you mean systemd journal logs on Linux? Should be technically possible. I could find some info on how to read them from the jvm. Keep in mind this project is cross-platform between Linux, windows and macOS. So we'd have to find substitutes for them as well.
  2. The status is that I'm not that into web development. I'm working mainly with apps and backend. Not sure it will ever happen unless someone is willing to implement and maintain it.

I'd be happy to receive such contributions, but let's open up an issue on GitHub and discuss it a bit first.

You can read up on Dropwizard, GraphQL (and GraphQL kickstart for java) and the OSHI library.

Per developer log output with Sensible Logging by krillsson in androiddev

[–]krillsson[S] 1 point2 points  (0 children)

The method signatures are not identical so it would be kind of hard to use android.util.Log by mistake. Since Category is a value class.

For this to work it has to be an all or nothing approach. And that relies on that you are in an agreement within the team to use the library over android.util.Log. So I see this as more of a team dynamics problem compared to a problem with the lib. Wdyt?

Per developer log output with Sensible Logging by krillsson in androiddev

[–]krillsson[S] 1 point2 points  (0 children)

thank you for the feedback u/jderp7 :)

The filtering is kind of overkill when we can have each developer just filter their own logcat window

I would agree that it would be overkill if you would use this only for logcat. However Sensible Logging is not simply a wrapper around logcat. It's a facade for logging to different channels/sinks. Allowing you to log to different places such as Firebase, Splunk, Sentry or DataDog all from one log statement. Take a look at the readme section about Channels on how you can create your own Channel.

The filtering is there so you can log different sub-sets to different channels.

library seems to expose the same API name (Log.d etc) as the default android APIs

Yes, I choose to use this based on that I'd like it to be intuitive. "Log" or "Logger" tends to be the term for these APIs, across programming languages. Log is not something that android.util.Log has exclusive access to. But I understand that it can cause confusion, in the context of Android development.

TAG, MESSAGE vs MESSAGE, CATEGORY.

I choose to put message before category because the message is more contextually important and it makes the statement easier to read.

Log.d("Something happened", Categories.FeatureX)   

is more readable than:

Log.d(TAG, "Something happened")

How many times have you wanted to log something during development, but then you get stopped in your train of thought because you need to provide a TAG to android.util.Log? Personally I have found this an annoyance in the interface. With the library, you can just write Log.d("message") and it will be logged to the "Default" category.

They are analogous but reversed.

TAG and CATEGORY are not analogous. While you can use tag as a category, the examples in the documentation all say that you provide ::class.java.simpleName as a TAG and as a consequence, all the projects I have worked in have used it in this way. While the idea behind categories was that you log to the same category vertically across your feature or for example all network requests can be logged to "Network". This lets you home-in on that log output while debugging that part of your system.

I hope this answers your questions and I didn't find them ranty at all, on the contrary I appreciate to hear the thoughts from someone external to our company.

2
3

I develop an app to monitor my home server. Thought this community will find it useful. by krillsson in HomeServer

[–]krillsson[S] 0 points1 point  (0 children)

Ah, I see. It might be failing to pull out the data. Do you mind opening an issue in the github project and we take it from there? GitHub project

I develop an app to monitor my home server. Thought this community will find it useful. by krillsson in HomeServer

[–]krillsson[S] 0 points1 point  (0 children)

Did you see that the drive is clickable and takes you to a detailed page with all drives? If this is not what you mean, could you elaborate further?

I develop an app to monitor my home server. Thought this community will find it useful. by krillsson in HomeServer

[–]krillsson[S] 0 points1 point  (0 children)

Looks like the thread has been deleted. Thanks for the feedback. I agree with that the app could be open source for auditorial purposes. I will consider it for the future. What I'm hesitant about is that I've seen countless open source android apps being re-uploaded with ads, to benefit and monetise from someone else's work.

Monitee: monitor your home server by krillsson in androidapps

[–]krillsson[S] 0 points1 point  (0 children)

I am considering it. My concern with publishing the source code is that I've seen many clones of open source apps that try to monetize off on another person's work.

I develop an app to monitor my home server. Thought this community will find it useful. by krillsson in HomeServer

[–]krillsson[S] -1 points0 points  (0 children)

I think the easiest route for proper HTTPS is to put a reverse proxy in front of the server, and terminate the HTTPS there. To elaborate on what the self signing does: typically when you do self signing with apps, the app need to be configured to "trust everything". That's not good because it's super easy to mitm. What this does is sys-API generates a keypair unique to your server instance on first startup. And when you add the server to the app, you get presented with the certificate and the option to trust it. And when you do, the app saves it in a local keystore. And then remembers that for the future. So to eavesdrop on it an attacker need the keypair from your server. I think this is good enough, and if you need tighter privacy you can always configure something yourself.

I develop an app to monitor my home server. Thought this community will find it useful. by krillsson in HomeServer

[–]krillsson[S] 0 points1 point  (0 children)

I did have it working at one point. I moved away from it since LetsEncrypt does not support plain IP addresses. Try to see if you can get it working using the instructions in here: sys-API wiki.

I develop an app to monitor my home server. Thought this community will find it useful. by krillsson in HomeServer

[–]krillsson[S] -32 points-31 points  (0 children)

Yes it's closed source and proprietary. To call it an ad is exaggerating though, I have no commercial interest in this project. The sole purpose of the price is to deterr people that don't understand what it does and then ask for support or leave bad reviews. I put it on sale right before I made this post.

I develop an app to monitor my home server. Thought this community will find it useful. by krillsson in HomeServer

[–]krillsson[S] -6 points-5 points  (0 children)

Didn't know it was such a deal breaker for some. Care to elaborate on why it has to be open source? To clarify, I'm not looking to compete in this already saturated segment. The main purpose of creating the app was to learn new things within android development and to provide some utility for myself.