it just seems to redirect to an otherwise Internet accessible page.
I'm using authelia with caddy but I'm guessing it could be similar, you need to configure the reverse proxy to expect the token the authentication service adds to each request and redirect to sign in if not. This way all requests to the site are protected (of course you'll need to be aware of APIs or similar non-ui requests)
I have to make an Internet accessible subdomain.
That's true, but you don't have to expose the actual services you're running. An easy solution would be to name it other thing, specially if the people using it trust you.Another would be to create a wildcard certificate, this way only you and those you share your site with will know the actual sub domain being used.
My advice is from my personal setup, but still all internal being able to remotely access it via tailscale, so do you really need to make your site public to the internet?Only if you need to share it with multiple people is worth having it public, for just you or a few people is not worth the hassle.
I don't actually have daily notes per se, I just have a way to add a note for the day when I need it.So, in "my daily notes" I have stuff to remember later about what I did that day.
For actually daily changes to a note I have dedicated notes for project documentation and dedicated ones for "working on" scratchpads-notes which are a way to quickly copy something and modify it while testing it.
I'd say it depends on your threat model, it could be a valid option.Still, how are you going to manage them?
A password manager? You'd still be posing the same question: should I keep my accounts in a single password manager?
Maybe what you can do is use aliases, that way you don't expose anywhere the actual account used see your inbox, only accounts to send you emails.But I tries this and some service providers don't handle well custom email domains (specially government and banking which move slowly to adapt new technology)
Use a reverse proxy so you can even have two different domains for each instead of a path. The configuration for this would change depending on your reverse proxy.
You can change the config of your pihole in /etc/lighttpd/conf-available/15-pihole-admin.conf. In there you can see what's the base url to be used and other redirects it has. You just need to remember to check this file each time there's an update, since it warns you it can be overwritten by that process.
Are you sure your IP is only used by you?AFAIK ISPs usually bundle the traffic of users to a few public IP addresses, so maybe the things you see are just someone else in your area going out from the same IP your ISP provides.
But I'm not actually sure if this is how it works, I might be wrong.
Inside that folder were all the DB files, so I just copied that into the new folder I created for ./postgres
I thought there would be issues with the file permissions, but not, everything went smoothly and I can't see any data loss.(This even was a migration from 1.94 to 1.102, so I also did the pgvecto-rs upgrade)
I've been using https://github.com/mbnuqw/sideberyIt also suggests you a way to hide the top bar, it can be dynamic or permanent depending on how you configure your userChrome.css
It provides you a way set up snapshots, although I haven't tested the restore functionality hehe.I'm not sure how you can export them and back them up.
The one I know works for restoring your tabs is https://github.com/sienori/Tab-Session-ManagerBut if you use sidebery to have your trees, panels, and groups, this one won't restore them, you'll get back on long list of tabs in a single panel, with no groups or trees.
I already had to restore a session with this one because I changed computer.
It has a way to backup your sessions in the cloud.
You can use GPSLogger to record it in local or send it to whatever service you want.If you're into selfhosting you can use traccar which is focused into fleet management so it's easy to get reports on the trips made.
As for your second point, I wouldn't trust the GPS for this, it can say you weren't moving since it only checks every so often to record the data, or maybe it says you actually were speeding because the two points it used to calculate the data weren't the actual points you were at that time.A dashcam would be better suited for this. I'm not sure how they work, but most probably they can be connected to read data from your car which would be more trust worthy to whoever might decide if you were actually speeding.
I've been using https://kolaente.dev/vikunja/vikunjaIt has options for sharing and assigning people to a task, but I only use it for personal stuff so haven't checked properly those features.
I'm not sure how the integration experience would be since I'm not familiar with calDAV.
I wish for it be like this for all the articles as some of the articles that load in full I’m not always interested in, and end up having to scroll through the whole thing
To skip to the next article you can configure the shortcuts native to FreshRSS, I think the default ones are h for the next unread article and k for the previous article. (I think these are the defaults because I haven't changed them and I see these in my config screen)For mobile I'm using the touch control extension in here https://github.com/langfeld/FreshRSS-extensions
I'm not sure what you mean by articles not loading properly.I haven't had any issues with FreshRSS' UI showing all the data.
Have you checked the feed sends all the article in it?For example ars' feed sends a few paragraphs and includes a link at the end with Read the remaining X paragraphs404media's does send all the article content in their feed.9to5google's only send you a single line from the article!!
So, it depends on what you need.
If you want to see the full content probably you need an extension which either curls the link of each item in the feed and replaces the content received by the feed with the one received bu the curl, or one which includes an iframe with the link so the browser loads it for you.IIRC there are two youtube extensions which do something similar to change the links for invidious or piped, one replaces the content with the links, and the other adds a new element to load the video directly in the feed.
The port for your postgres container is still the same for other containers, what you did was just map 5432 to 8765 for your host.
You don't need to change the port or the host the immich services try to access within the network docker compose creates.
You still have container_name: immich_postgres so you didn't change anything for the other containers.
What you did was change how to write the command to up or down the container.
From docker compose up database to docker compose up immich-database (which normally you won't use since you want to up and down everything at once).If you do docker ps you'll still see the name of the container is immich_postgres
Same, I have multiple services running in some machines and I've never had the need to modify the ports inside each docker-compose network.
Just the exposed ports are the ones I've changed, and just for integrating with external services or the reverse proxy.
And expert or someone knowledgeable may not have the time to invest in a community. A mod is a volunteer who helps ensure rules are followed and we can have a place to discuss about a topic.
But a mod insulting the community is a different problem. It's doing something which they should be helping mitigate.
I've been using traccar (https://github.com/traccar/traccar).It's mostly for fleet management, but I've been using it as a replacement for Google maps timeline.Its android apps ara basic but haven't had any problems with them.
Or if you find a service which doesn't provide a client you can use this app https://github.com/mendhak/gpsloggerIt allows you to send the gps data to different services with their specific formats at the same time. I was using it to send the data to traccar while also saving it in a local file.
I'm using authelia with caddy but I'm guessing it could be similar, you need to configure the reverse proxy to expect the token the authentication service adds to each request and redirect to sign in if not. This way all requests to the site are protected (of course you'll need to be aware of APIs or similar non-ui requests)
That's true, but you don't have to expose the actual services you're running. An easy solution would be to name it other thing, specially if the people using it trust you.Another would be to create a wildcard certificate, this way only you and those you share your site with will know the actual sub domain being used.
My advice is from my personal setup, but still all internal being able to remotely access it via tailscale, so do you really need to make your site public to the internet?Only if you need to share it with multiple people is worth having it public, for just you or a few people is not worth the hassle.