linux mouse pointer dynamically adapt to background
gnome tweaks and mouse (pointers)
You need a complete “cursor theme” in your /usr/share/icons directory. This (at least, so far as I’m aware) means all of the mouse pointers, not just the one you want to change.
All mouse cursors have to be in the “X11 Mouse Cursor” format, with the extension lopped off.
The primary mouse pointer is called “left_ptr”
GIMP can save directly to that format.
Mouse pointers can be as big as you want them to be.
So here we go. You’ll need GIMP, and Gnome Tweaks.
Begin by creating a new subdirectory of /usr/share/icons. You’ll need to sudo this.
Next, find an existing theme in /usr/share/icons that has a cursor.theme file and a cursors subdirectory, and copy them into the directory you just created. You’ll need to sudo this as well.
Then, get your image of choice, and load it into GIMP. Get it into a square format, at least 24x24. I started with 32x32, then tried 64x64, then settled on 48x48.
Save it as an “X11 Mouse Cursor” (xmc) file. You’ll get a dialog asking you how big (the size to which you scaled your image), and where to put the hotspot. In my case, the hotspot was at (0,0).
Now, once it’s saved, rename it (assuming you’re changing the primary mouse pointer) to “left_ptr” (lopping off the extension in the process).
Now, copy this into the “cursors” directory of your theme (in my case, /usr/share/icons/Willard/cursors).
Finally, go into Gnome Tweaks, go to Appearance, and change the cursor theme to your new one, and if everything went OK, it should take effect immediately.
install caddy
Caddy webserver static site Markdown rendering
Caddy offers support for static file service as well as reverse proxy. So if you have a static site written in Markdown, you can actually use Caddy to do the Markdown rendering. Caddy provides a template system that can handle on the fly conversion of content. So no need to convert your Markdown to HTML before uploading it to the server.
curl localhost:2019/config/
This is not your website:
the administration endpoint at localhost:2019 is used for controlling Caddy and is restricted to localhost by default.
which caddy => /usr/bin/caddy
which Caddyfile => no Caddyfile in (/root/.local/bin:/root/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin)
sudo mkdir /etc/caddy
sudo chow -R root:www-data /etc/caddy
DNS A record for your domain (i have none)
cat /etc/caddy/Caddyfile
https://caddyserver.com/docs/caddyfile
root * /usr/share/caddy ? => root * /srv/www
/srv should already exist
mkdir /srv/www
linux /var versus usr/share =>
/usr is for constant data and /var for variable data,
Most of the web servers I’ve worked with have their files in /var/www/ (mostly apache , but not standarized)
/srv – this directory should contain data that is served by the system
/srv/www/
chown -R caddy:caddy www on the /www folder
touch index.html
file in root
nano index.html
PKS site
WIP
nota.IT nota.wm scriptaafter these changes : systemctl restart caddy