Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)HL
Hellmo_luciferrari @ Hellmo_Luciferrari @lemm.ee
Posts
12
Comments
342
Joined
2 yr. ago

  • I will likely go back and try that. I however know just like in other email clients, if I have thousands of emails per account its bound to be slower. I did clean out each box. I plan to use Thunderbird again once I clear out all of those emails and consolidate to one email address.

    I will have to investigate which directories to purge.

  • To get Nvidia working on Arch here is what I did:

    During installation of Arch when it asked if I wanted to chroot into my distro I did. However if you enter commandline by hitting CTR+ALT+

    <F1 or F2 or F3>

    to change to a virtual console. If you are doing this from a chroot environment you don't need sudo.


    edit the mkinitcpio.conf

    sudo nano /etc/mkinitcpio.conf

    In the MODULES=() section I added "nvidia nvidia_modeset nvidia_uvm nvidia_drm" without quotes. So it looked like this:

    MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)

    Afterwards I updated my initramfs images by running:

    sudo mkinitcpio -P

    Then I edited my grub config:

    sudo nano /etc/default/grub

    Find the line that says "GRUB_CMDLINE_LINUX_DEFAULT="""

     
        
    GRUB_CMDLINE_LINUX_DEFAULT="nvidia-drm.modeset=1" 
    
      

    Then I updated grub

     
        
    sudo grub-mkconfig -o /boot/grub/grub.cfg
    
      

    Note: I use the Nvidia Proprietary drivers


    Resources: Arch Wiki


    I do not recommend Manjaro especially if you are going to be using the AUR (Arch User Repository) as it can cause things to break.

  • I was using Thunderbird, but I have had a number of issues with it. Crashing seems to happen whether I use the Flatpak or install from AUR.

    I have switched back to using web clients for my mail for the time being.

  • I ran into an issue where I changed nothing, and all of a sudden none of my SSL certs worked on top of most of the hosts were not working through the reverse proxy. I had not even changed ip addresses on any of them. I am not sure what was going on.

    It was more of a "I didn't want to troubleshoot" and gave up, so I shut down my servers.

  • Using SMS through signal defeats the purpose of signal...

    The UI is fine, what more do you expect out of it? It has a list of chats, a menu button with menu options, like it's a messaging app not a social media platform akin to discord or telegram.

  • Today I learned about Linkwarden, and I am so excited to check it out. Thank you!

    NPM I did use, however it was ultimately the catalyst as to why I quit homelabbing. But when it did work, it was simple even for SSL cert renewal.

  • I appreciate that mentality though. When things break, if your understanding of your setup is there, it's less to deal with.

    I am forgoing the Portainer route this time. I am going to strictly use Docker Compose for my containers. I had too many issues with Portainer to consider using it.

    For reverse proxy, I just need/want it for simple ip:port to sub.domain.lan type addresses locally. Anything I need outside of my home will be tunneled through wireguard.

    I always quite liked Dozzle. It was handy, and has helped me comb through logs in the past.

  • I will likely dabble with Logseq.

    I used NGINX Proxy Manager for a while, then had some issues that ultimately killed my homelab setup, so not sure that I want to go down that route again, or if I want to investigate Caddy, Traefik, or another.

  • I think I am going down the docker compose route. When I started using docker, I didn't use compose, however, now I plan to. Though, Ansible has been on my list of things to learn, as well as nixOS.