Where we’re going, we don’t <del>need<del> have fuses.
Where we’re going, we don’t <del>need<del> have fuses.
Where we’re going, we don’t <del>need<del> have fuses.
It was the former. This unit had 8 12v batteries VERY snuggly placed within it. I didn’t pay attention to all the leads and their locations when dissembling the old batteries. I’m professional IT and hubris was nearly the end of me.
Yeah these are the small, closed cell 12v batteries. Just make sure you have the circuit open until the very last step. Additionally, if you have an array of batteries, make sure you’re paying attention to their configuration.
Oh no. Half of this post is me making fun of myself. Mistakes were made. When you have a large array of batteries, it’s important to wire them up correctly when replacing them. I definitely closed the circuit on some of the batteries when I shouldn’t have.
I see how it could be confusing, and in the spirit of sending the correct message, I have added a clarifying edit.
The same front end? Nah it has it’s own menus and such. If you’re familiar with the anatomy of the conf files you can piece each sub-menu within the plugin to it’s corresponding section in the conf. Not everything that I need was represented. There is a way to inject custom blocks, but it’s pretty cumbersome.
Honestly? I’m considering going back to a dedicated nginx host for two reasons. Firstly it’s just easier to configure. Secondly, I’m sending internal traffic to the public DNS addresses for some of the services and I’m not 100% positive those fuck-heads over at Comcast aren’t charging me for the hairpin route. If I had a local, internal proxy, I could avoid that.
My family and I really like it. I invested in a small, physical scanner capable of network file sharing that we have plugged in and always ready to scan. When we get documents or receipts, we scan them and they’re immediately added to the database. I also have it checking an email address (mine is custom, but you could really have it check any address) and any time a PDF or such is sent, it gets consumed and that email them gets sorted.
There are a few downsides, however. As mentioned in other posts, turning your physical stack of documents into a digital stack of documents is just trading one pile for another. At least with a digital pile, you can sort a little quicker, but you still have to sort the consumed documents and check them to make sure the engine, which is supposed to be learning, has elected to sort the documents correctly.
The compose stack is pretty easy to use, but it does benefit from a little knowledge in Docker/containers. Especially when the main container decides it’s not healthy. I wouldn’t recommend it to a first time Docker user, is all.
Additionally and also previously mentioned, if you’re keeping important documents in it, encrypted storage with encrypted back up is important.