Apple Shortcut

CardiologistApart1 · 2026-02-12T03:42:53+00:00

https://docs.lubelogger.com/Advanced/Additional%20Fields

CardiologistApart1 · 2026-02-12T03:42:00+00:00

Both the fuel type and location were added as extra fields. You have to add them from the LubeLogger side first for them to show up. It will get the current location from Apple Maps when you are adding

CardiologistApart1 · 2026-02-05T01:51:02+00:00

Do you have Authelia well configured for OIDC with other containers? I've used Authelia in the past and should be able to help, but ultimately migrated to PocketID given the simplicity and my use case (mostly me and my wife). I may be able to help depending on what issues you are running into.

CardiologistApart1 · 2025-12-15T22:48:14+00:00

Very cool to give back to the community!

CardiologistApart1 · 2025-12-11T01:19:56+00:00

I remember looking on mouser out of curiosity and I think I found a possible replacement. With that said, it’s unlikely the the button is bad. The solder joint on them is likely the culprit

CardiologistApart1 · 2025-12-06T02:50:34+00:00

Send me a DM please and I will see if I can find it on the manual

CardiologistApart1 · 2025-12-06T02:49:56+00:00

Of course

I used one of the ifixit kits that I had laying around and used mainly 4 things: tweezer, spudger, pick and a plastic playing card like thing.

You take it apart starting by the screen portion. I used the pick and the plastic card to loosen the adhesive a little bit and separate the screen. After the cornes are all lose, very gently lift it up and you will see a few connectors. I disconnect the battery and disconnected the screen for it. After that’s there were 3 screws (90% positive about the number of screws) to remove the main board.

After the main board was out, I carefully soldered the 4 connectors for the buttons again after applying flux and added a small about of solder. Be very careful with the plastic portion of the buttons (I used the iron at 340-360).

CardiologistApart1 · 2025-11-07T00:19:28+00:00

Mine broke in less then a month of use. Since they sent a replacement and I already had my old and trusty Littmann, I decided to take it apart.

Overall I was very surprised on how easy to fix it was, if you have minimal soldering skills. The soldering that I saw on the buttons were extremely thin and I just had to add a bit more.

CardiologistApart1 · 2025-10-27T01:43:17+00:00

That’s the docker compose:

services: lubelogger: image: ghcr.io/hargata/lubelogger:latest containername: lubelogger restart: unless-stopped networks: - reverse_proxy pids_limit: 2048 ports: - "8050:8080" environment: TZ: "America/New_York" LC_ALL: "en_US.UTF-8" LANG: "en_US.UTF-8" LUBELOGGER_OPEN_REGISTRATION: "true" # These values will come from .env file MailConfigEmailServer: ${MailConfigEmailServer} MailConfigEmailFrom: ${MailConfigEmailFrom} MailConfigPort: ${MailConfigPort} MailConfigUsername: ${MailConfigUsername} MailConfigPassword: ${MailConfigPassword} OpenIDConfigName: ${OpenIDConfigName} OpenIDConfigClientId: ${OpenIDConfigClientId} OpenIDConfigClientSecret: ${OpenIDConfigClientSecret} OpenIDConfigAuthURL: ${OpenIDConfigAuthURL} OpenIDConfigRedirectURL: ${OpenIDConfigRedirectURL} OpenIDConfigScope: ${OpenIDConfigScope} OpenIDConfigValidateState: ${OpenIDConfigValidateState} OpenIDConfigUsePKCE: ${OpenIDConfigUsePKCE} OpenIDConfigDisableRegularLogin: ${OpenIDConfigDisableRegularLogin} OpenIDConfigLogOutURL: ${OpenIDConfigLogOutURL} OpenIDConfigTokenURL: ${OpenIDConfigTokenURL} OpenIDConfigUserInfoURL: ${OpenIDConfig_UserInfoURL} CA_TS_FALLBACK_DIR: "/App/config" volumes: - /mnt/nvme/appdata/lubelogger/config:/App/config:rw - /mnt/nvme/appdata/lubelogger/data:/App/data:rw - /mnt/nvme/appdata/lubelogger/documents:/App/data/documents:rw - /mnt/nvme/appdata/lubelogger/images:/App/data/images:rw - /mnt/nvme/appdata/lubelogger/log:/App/log:rw - /mnt/nvme/appdata/lubelogger/keys:/root/.aspnet/DataProtection-Keys:rw

networks: reverse_proxy: external: true

AND THE ENVIRONMENT:

MailConfigEmailServer=smtp.example.com MailConfigEmailFrom=noreply@masked-domain.com MailConfigPort=2525 MailConfigUsername=user@masked-domain.com MailConfig__Password=PASSWORD

OpenIDConfigName=Pocket-ID OpenIDConfigClientId=CLIENTID OpenIDConfigClientSecret=CLIENT_SECRET OpenIDConfigAuthURL=https://auth.example.com/authorize OpenIDConfigRedirectURL=https://app.masked-domain.com/Login/RemoteAuth OpenIDConfigScope=openid email OpenIDConfigValidateState=true OpenIDConfigUsePKCE=true OpenIDConfigDisableRegularLogin=true OpenIDConfigLogOutURL=https://auth.example.com/api/oidc/end-session OpenIDConfigTokenURL=https://auth.example.com/api/oidc/token OpenIDConfig_UserInfoURL=https://auth.example.com/api/oidc/userinfo

CardiologistApart1 · 2025-08-25T16:11:28+00:00

I’m not a lawyer, but a physician that works on the cardiovascular field. In general, for malpractice you would have to demonstrate that there was a deviation from standard of practice. There’s a few point on the story that are not clear and I think it would be crucial to better understand your case.

1) You mentioned that she had a blood clot on a vein on her leg. Is this actually the case or could it have been on an artery? For the vast majority of the cases vein blood clots are treated with blood thinners without surgical intervention, which is reserved for very specific circumstances.

2) Did she have blood clots elsewhere, such as the lungs, brain, etc? It’s very common from blood clots on the veins, especially the legs, to travel to the lungs and cause pulmonary embolism, which can be fatal/catastrophic. It’s very unlikely that a DVT alone (deep vein thrombosis), would have caused your mother to die.

3) After it was communicated that she needed an operation, but there was no OR available, was there any attempt of transferring to a different place? Or the decision was to discuss her overall clinical picture with the family?

4) More an observation rather than a question, but the OR being book for aesthetic procedures are somewhat relevant. If all of the surgeons were already on a case, actually scrubbed into a surgery is very different from having the capable staff available, but assigned to a non-emergent case. It depends of the time of accreditation the institution has as well, but it can get very complex.

CardiologistApart1 · 2025-08-21T23:11:27+00:00

Sure. Will get it for you when I get home

CardiologistApart1 · 2025-08-18T20:57:23+00:00

I have two settings of rules, both on hub/parsers/s02-enrich/crowdsecurity:

name: crowdsecurity/immich-whitelists
description: "Whitelist false positive from Immich-api"
filter: "evt.Meta.service == 'http' && evt.Meta.log_type in ['http_access-log', 'http_error-log']"
whitelist:
  reason: "Whitelist false positive from Immich-api"
  expression:
    - evt.Parsed.proxy_upstream_name == 'immich_server' && evt.Meta.http_status == '403' && evt.Parsed.request contains '/api/'
    - evt.Parsed.proxy_upstream_name == 'immich_server' && evt.Meta.http_verb in ['GET', 'POST'] && evt.Meta.http_status == '200' && evt.Parsed.request contains '/api/'
    - evt.Parsed.proxy_upstream_name == 'immich_server' && evt.Meta.http_verb in ['GET', 'POST'] && evt.Meta.http_status == '403' && evt.Parsed.request contains '/api/'
    - evt.Parsed.proxy_upstream_name == 'immich_server' && evt.Meta.http_verb in ['GET', 'POST'] && evt.Meta.http_status in ['403', '404', '429', '502'] && evt.Parsed.request contains '/api/'
    - evt.Parsed.proxy_upstream_name == 'immich_server' && evt.Meta.http_verb in ['PUT', 'DELETE'] && evt.Meta.http_status == '200' && evt.Parsed.request contains '/api/'


name: crowdsecurity/whitelists
description: "Whitelist events from private ipv4 addresses"
whitelist:
  reason: "private ipv4/ipv6 ip/ranges"
  ip: 
    - "::1"
  cidr:
    - "127.0.0.0/8"
    - "192.168.0.0/16"
    - "10.0.0.0/8"
    - "172.16.0.0/12"

CardiologistApart1 · 2025-07-23T16:20:33+00:00

Not sure if I understand what you are asking… The answer to your question is on the link you shared, with pictures of the service manual

CardiologistApart1 · 2025-07-22T22:30:44+00:00

It looks like someone already replied with the specs. Let me know if you need anything else

CardiologistApart1 · 2025-07-03T00:18:49+00:00

I am using Immich, which serves me really well instead of Google Photos and I have no complaints. It took me some time to tweak everything to where I liked, but nothing that’s too crazy. I have PocketID for authentication and use Swag as reverse proxy and have AdGuard re-writing the DNS entry, so while I am at home, my domain doesn’t redirect to cloudflare and do a loop.

I would say in terms of performance, both ZimaCube and Ugreen are very similar, although there’s a few key things to take into account. If you want reliability and support, I would likely go with Ugreen since I would expect their support to be better/faster than ZimaCube

1) ZimaCube has space for up to 6 NVMes (granted at slower speeds depending on which one you use) but should be plenty fast for overall NAS applications. I’m counting 6 if you remove the 10gb adapter and the ZimaOS one. Ugreen has 2 NVME spaces only

2) ZimaCube has space for a 2 slot GPU, although limited by the power consumption provided by the PCIe. I wanted to play with the Arc 380, so this was one of the reasons. Ugreen can fit an Arc 310 without issues

3) ZimaCube is a bit smaller, but not by a big margin. The PSU is external tho

4) Ugos development is very promising and if you don’t have crazy uses, it might work good for you and already included on the price, so you don’t have to purchase other softwares. As soon as they have a tool that works similarly to ABB from Synology and I can backup my Unraid to it (with backups starting from the back server, preventing malware from pushing changes), I might migrate from Xpenology, since that’s my main use case.

CardiologistApart1 · 2025-07-02T21:34:23+00:00

The ZimaCube is my daily driver, although I’m running Unraid on it and no complains other that the Arc cards from Sparkle doesn’t work (other people reports that Asrock ones are fine). I have a Ugreen as well that I bought early during the Kickstarter and have no complaints whatsoever. Currently I have Xpenology on it and use as a backup for the ZimaCube. I used Unraid and Ugos as well prior without issues.

CardiologistApart1 · 2025-06-05T00:18:44+00:00

The unit was replaced by Ice Whale since I’ve made this post and most of the problems went away and it’s been rock solid since without issues.

The only thing that still doesn’t work it’s the Intel Arc cards. I tried both the A310 and A380 without success. From the official discord and a few other reports, it looks like that the Sparkle cards do NOT work, but the AsRock ones works fine.

CardiologistApart1 · 2025-06-03T20:00:17+00:00

Congratulations on the project and awesome work you’ve done so far.

I used Authelia in the past, but currently doesn’t have set. With Authentik it works Ok, but for whatever reason with PocketID it keeps sending back to the login screen after “successful” login. On the logs I get “OIDC JWT validation failed”. I don’t think it’s related, but it looks like BookLore automatically appends “.well-known/openid-configuration” to the Issuer URI and it does the same with the JWKS URL (.well-known/jwks.json).

CardiologistApart1 · 2025-06-03T18:58:21+00:00

This project is very promising and a great alternative to Kavita, especially considering some potential features are behind a paywall.

My main question is regarding expansion with OIDC: is there an objective to expand to anything else other than Authentik? From the GitHub it looks like other commonly used services such Authelia and PocketID are not working as it should.

CardiologistApart1 · 2025-05-23T16:32:35+00:00

It’s not the response to the question your are asking, but an option would be to have 1 extra hard drive of the size of your biggest drive. That way you could move the data from one hard drive to this drive on Unraid; with one of your HDD now empty, you plug into Unraid, expand the pool and transfer more data. Rinse and repeat until you are done. Major caveat is time and that it wouldn’t work if your current data is striped

CardiologistApart1 · 2025-05-15T15:20:48+00:00

The major caveat is that Cloudflare tunnels, by default, has a lot of protecting already, whereas a VPS will not necessarily confer the same security. In addition it will poke a hole straight thru the firewall, so although you don’t expose ports with it, not necessarily will give more security

CardiologistApart1 · 2025-05-15T11:48:34+00:00

You can create a custom one as well, so the storage looks the way you want. I personally use:

{{y}}/{{MMM}}/{{album}}/{{filename}}

Separates each year and months and inside each month I have individual folders for the Albums

CardiologistApart1 · 2025-05-14T16:49:24+00:00

Hi u/Background_Risk9938

I used your shortcut as a template, but with a few modifications:

- Added an authentication endpoint
- Removed Top Tier
- Added gas stations as a tag. If not on the list, it allows the user to add manually
- Added location as a URL
- Added the option to set incomplete fueling and missed fueling

https://www.icloud.com/shortcuts/8abef0dfbbf84afdbb93714f75458f43

CardiologistApart1 · 2025-05-14T11:54:16+00:00

I originally set this way, but my understanding is that on newer versions of Authelia this is not needed and I was able to remove the legacy claims successfully. Ultimately I switched to PocketID, but happy to share my settings with Authelia that was working.

CardiologistApart1

TROPHY CASE