I cannot fathom what a respectable website would need with a port scan. They should normally just be listening to/broadcasting on 80/443. Is it looking to see if the normal html ports are remapped? That's the only reason I could imagine.
Yeah you can copy and paste images into a note just fine.
Joplin is great. It can't do the handwritten notes like onenote as far as I know, but otherwise I think it's got pretty good feature parity. You can sync it using an existing nextcloud, WebDAV, or even onedrive or dropbox if you don't want to deal with the hassle of self-hosting at all.
Ansible, become: yes, and granting access to specific sudo commands without a password
Is there a good way to use the "become: yes" for the needed escalation to sudo for a handful of commands which need it while limiting the user's access to passwordless root? I've added this line to /etc/sudoers.d/$USER
(username) ALL=(ALL:ALL) NOPASSWD: /usr/sbin/omv-upgrade, /usr/sbin/reboot
Which should allow my user to use the omv-upgrade script (which does some apt stuff) without a password prompt for sudo. This allows it to perform the needed apt commands for an upgrade without actually giving full apt access to install whatever. Likewise with reboot, though I'm not sure which command ansible will actually try with these:
``` - name: Check if a reboot is required. ansible.builtin.stat: path: /var/run/reboot-required get_md5: no register: reboot_required_file
- name: Reboot the server (if required). ansible.builtin.reboot: when: reboot_required_file.stat.exists == true ```
I presume it's that reboot, but maybe it'll try the systemctl one instead. Is there a better method to give the user the needed passwordless sudo actions without the security risk of opening everything up to that user (which I don't want to do at all)
I run everything on local hardware. 1 Synology NAS, one old desktop (Ryzen 5 5600X) which has been repurposed to a Proxmox node, and a second Proxmox node (i5-6500T). I use Open Media Vault with Docker as my primary host, and I have a CoreOS secondary host that I have a couple of Podman containers on. I'm planning moving stuff to Podman eventually, but I was mostly focused on moving the bare metal OMV host to a vm recently. I have a media share on my NAS that some containers rely on. I also have a NFS share on it that I use for larger data pools (like nextcloud, download folders for torrents).
- Everything is: Bare metal Proxmox -> VMs -> Containers. No services running directly
- I use Docker (mostly) and a couple of podman containers, moving to podman going forward
- Only orchestration is docker-compose (for docker) and systemd (for podman)
- No central log server, haven't needed one
Lemmy Follow Bookmarklet. GitHub Gist: instantly share code, notes, and snippets.
I made a bookmarklet (with some ChatGPT help to troubleshoot) which will redirect you to your own instance’s URL for a foreign Lemmy community to easily subscribe to it.
This will not correctly redirect you if you are in a topic already. It will only work if you are on the base community page. If someone wants to tweak it (or redo it entirely) to work in a bigger variety of instances please feel free. My skills with JavaScript are… minimal.
Lemmy Follow Bookmarklet. GitHub Gist: instantly share code, notes, and snippets.
I made (with some ChatGPT help to troubleshoot) a bookmarklet which will redirect you to your own instance's URL for a foreign Lemmy community to easily subscribe to it.
This will not correctly redirect you if you are in a topic already. It will only work if you are on the base community page. If someone wants to tweak it (or redo it entirely) to work in a bigger variety of instances please feel free. My skills with JavaScript are... minimal.
Also, if you want to actually learn, I would strongly recommend against using Docker containers for everything. Besides being stuck with what the developers prefer, all the work of installing things is already done.
I really disagree on this point. You should use docker or podman (preferably Podman) to containerize your applications on your server to keep them ephemeral and separated from the host OS wherever possible. This improves security, makes setups reproducible, and eases backup and restore procedure. If you want to build from source do so with a containerfile/docker file to keep your build environment fresh and clean.
you can also self-host a language tool instance and point the extension to that instead of their official instance.