[-] [email protected] 1 points 2 years ago* (last edited 2 years ago)

I thought about this solution, as it is the "cleanest", however I need on total 4 firefox derivatives. Unfortunately, when looking deeply into the options, i haven't found 4 that are similarly trustworthy, well maintained etc. Also i have my firefox config fully figured out, it works and is as private as i want them, without some maintainer forcing their opinion on my use cases. Plain firefox is the easiest to configure, as it's like a blank start. However i might be wrong here and am open to suggestions :D

[-] [email protected] 1 points 2 years ago

Unfortunately that is not what I am looking for. I am already using named profiles. Like i stated in my original post as well as my answers below, this only works from Inside Firefox, however from the operating system pov it is still treated as the same application. Which means:

a) When i share the work profile, i also share all other profiles, as they are all Firefox b) When I quick access firefox via spotlight, i end up at the nearest, random profile / instance of firefox. c) There is no way to differentiate the profiles on an application level. d) I can not assign the instances to different desktops, as they are all Firefox.

[-] [email protected] 1 points 2 years ago

Good choice, however the number of supported languages is limited to things with language server or treesitter support. Meaning languages without this, like asciidoc, is not supported and might never be

[-] [email protected] 1 points 2 years ago

I recommend to start with kickstart if you prefer to customize https://github.com/nvim-lua/kickstart.nvim or Lunarvim for a full IDE experience to see what's possible and go from there https://www.lunarvim.org/de/

Most works out of the box then. Start there and customize further to your needs

[-] [email protected] 1 points 2 years ago

That looks promising, especially since my current status bar is also just a collection of shell scripts, so that might be easier to switch

[-] [email protected] 1 points 2 years ago

Thanks for the hints, this definitely helped, however it did not solve the issue.

What i did:

  1. I changed via omv-firstaid the omv port from 80 to 8081.
  2. I confirmed with ss -ltn that this change was successful and i see the listening port 80 vanished, while this now popped up:

State Recv-Q Send-Q Local Address:Port Peer Address:Port

LISTEN 0 511 0.0.0.0:8081 0.0.0.0:*

  1. I tested locally via ssh from the pi the connection via curl http://mylocalip:8081/ and it works, i get the html back
  2. I tested from my laptop (connected to my router via WiFi, where the raspberry is meshed into via the repeater in between) and i still get the timeout.
  3. I tried tunneling again via ssh ssh -L 8081:localhost:8081 [email protected] and i did not get any errors this time. However when i open the local url in the browser i get a connection reset and my terminal shows me channel 3: open failed: administratively prohibited: open failed. However this just says that TcPForwarding is disabled, which is fine, so that tunneling issue should not be the main problem, i assume.
[-] [email protected] 0 points 2 years ago

Can you recommend some devices? Most of the ones i saw had good prices, but not performance relative to power usage. The N100 with its 4 efficiency cores is actually quite good for the price and power usage. Unfortunately most mini pcs with it have limited ports.

I also think, that 2 ssds might be sufficient for the beginning. I'm even thinking of just adding 2 external ssd's and call it a day for the beginning (one as backup), but that does not scale well.

[-] [email protected] 0 points 2 years ago* (last edited 2 years ago)

The jbod idea sounds good to explore further, as it tha home server and storage would be separated. However it would add an additional device to the power bill.

However i don't need the full amount of all disks at all times. If i'd want to unplug via shell script, i'd need to plug it manually in person back in for storing things. I actually do not need it running all the time, as the home server ssd can cache most of what i need recently in access. The jbod is then more an archive.

i'm mainly looking for a way to power down the inexpensive hdd's. I could use the raspberry pi as the jbod controller, but it does not properly support wake on lan, so thats also not an option

view more: ‹ prev next ›

cloudwanderer

0 post score
0 comment score
joined 2 years ago