Paperless does support defining a folder structure that you can use to organize documents within that paperless media volume however you should treat it as read only.
OP could use this as a way to keep their desired folder structure as much as possible, but it would have to be separate from the consumption folder.
I don’t fully understand what you’re saying, but let’s break this down.
Since you say you get an NGINX page, what does your NGINX config look like? What exactly does the NGINX “login page” say? Is it an error or is it a directory listing or something else?
Also, the law requires that publicly traded companies be greedy
The law doesn’t actually state you need screw over your customers and maximize profit. It says that executives have a fiduciary duty, which means they must act in the best interest of the shareholder, not themselves.
That does not mean they have to suck out every single dollar of profit. Executives have some leeway in this and can very easily explain that napkins lead to happier customers and longer term retention which means long term profits.
It’s purely a short-term, wall street driven, behavior also driven by executive pay being also based in stock so they’re incentivized to drive up the price over the next quarter so they can cash out.
Then try something like:
Create Quanity unit of ml and a liter unit
In your product use: Unit stock: bottle or liter Unit purchase: bottle Consume: ml Price unit: ml
Set a product specific QU conversion of bottle to ml
Weirdly, the quick consume unit is based on the stock unit, not the consume unit. That seems like a bug.
The problem with Grocy is that going too fine grained means you’re unlikely to keep it up to date or it be accurate. I would not try to track your usage in ml. Just track it at the bottle level.
However you can still track the price per ml because grocy lets you independently set units. Just define a mapping between bottle and ml.
Will I still need to consider multicast DNS if my DNS server is on-prem (Pi-Hole + Unbound)
Multicast DNS is separate from DNS, so even if you have Pi-Hole, you’d still have devices using mDNS. It’s possible to route mDNS across separate IP networks seeing as how there’s mDNS relays across VLANs which would suggest Wireguard could support Multicast. Other things use Broadcast (e.g. WoL) which is a bit more challenging to forward across IP networks.
I’m not familiar with GRE so I couldn’t comment on whether it’s possible or not. I guess it all depends on how confident you are with your networking skills. If you get it working, you should definitely document it and share with others.
I didn’t quite do what you did, but I ran HA in a Kubernetes cluster which was logically a separate IP network. I had to setup the container with multiple network interfaces and specially craft the route table to forward broadcasts + multicast traffic to the correct network.
Tailnet appears to be Tailscale which is Wireguard underneath. This means it operates at layer 3 (IP). However a bunch of smart home stuff (mDNS, WoL, etc) all depend on layer 2 connectivity (same subnet).
That means some stuff won’t work correctly.
If you’re running Docker for servers not development, then you can make Hyper-V work. I used to do that before I got a separate Linux server and it worked out.
Just setup a network adapter that gets bridged to your Ethernet adapter, then create a VM that uses that bridged adapter. The Linux VM will appear like its another computer on your LAN and you can use Docker with host Network.
What is your threat model or goal? It could hide the device you use to connect to the instance, however a lot of actions you do on Lemmy, including all upvotes, are public to other instances.
Keepass2Android. I store everything in a KeePass database synced with OneDrive. I like KeePass because it serves as the storage for all my passwords, OTP, and even SSH keys because it can act as an SSH KeyAgent.
If I create a secondary config as you are suggesting, wouldn’t it create a conflict with the server blocks of default.conf
No, you can have multiple server
blocks with the same listen
directive. They just need to differ by their server_name
and only one server
block can contain default_server
; Reference
NGINX will use the server_name directives to differentiate the different backend services. This is a class virtual host configuration model.
There was an uncaught exception to boot gunicorn workers
That’s odd that it didn’t cause the Docker container to immediately exit.
What now? So now that it looks like everything is working. What is the best practice for the nginx.conf? Leave it all in /etc/nginx/nginx.conf (with user as root), reestablish the out box nginx.conf and /etc/nginx/conf.d/default.conf
My suggestion would be to create /etc/nginx/conf.d/mycooldjangoapp.conf
. Compared to conf.d/default.conf
, this is more intuitive if you start hosting multiple apps. Keep it out of the nginx.conf
because apt-get or other package managers will usually patch that with new version changes and again it gets confusing if you have multiple apps.
First the basics. Connection refused means that nothing is running on “http://192.168.0.2:8020/”
0.0.0.0/8082->8082
Confirmed upstream block container is running and on the right exposed port
What steps did you do to confirm that this is running?
Accidentally typo your password and get blocked. And if you’re tunneling over tor, you’ve blocked 127.0.0.1 which means now nobody can login.