Day 830
Yunohost
I’m very impressed by it! Makes everything really easy, I remember the last time I had to install stuff manually. After 48h 9/10, some things surprised me (removing root ssh access…) but they were always mentioned in the relevant docu I hadn’t read.
Official docu is quite okay, but rarely appeared when I was googling my problems. My instinct is to Google the problem instantly - sometimes they should actually be to find and check any existing official documentation/README first, then google. (An even better instinct would be to skim any official documentation before starting, as religiously as I do it for unknown real-life 3D things.)
Adding subdomains for Yunohost
This took me too long to find, has info about correct DNS records: DNS and subdomains for the applications | Yunohost Documentation
By trial and error the complete process is:
- Add DNS record for subdomain like last examples here:
@ A XYZ.XYZ.XYZ.XYZ @ AAAA 1234:1234:1234:FFAA:FFAA:FFAA:FFAA:AAFF * CNAME mydomain.com. agenda CNAME mydomain.com. blog CNAME mydomain.com. rss CNAME mydomain.com.
- Add new domain to yunohost, input the domain with subdomain (
subdomain.my.domain
) as it if were new - Do a diagnostic, which does DNS checks too, which are needed for Letsencrypt
- Install letsencrypt certificate from the usual Yunohost panel
I kept messing up NAME and DATA of the CNAME records because I was following more the other ones Yunohost created, a row of
Name: xmpp-upload.my.domain
Data: @
For subdomainname.my.domain I needed this (kinda-sorta-reversed from the above; as usual, dots are significant):
Name: my.domain.
Data: subdomainname
Random / colored fonts generator / CLI
cfonts is like figlet, but with many more settings (colors and alignment blew my mind!)! Link has a lot of colorful examples. I might get a nice colorful motd and/or banner soon. :)
Setting a new hostname linux
There’s a command for that: hostnamectl set-hostname new-hostname
Symbolic links and ~/.local/bin
I like the idea of having ~/.local/bin
in my $PATH
, and putting there symbolic links (ln -s TARGET LINK
) to my usual folder where I have programs/executables. I’d even have a separate thing in $PATH
for shell scripts and binaries, which will get rid of so many stupid CLI aliases I have whose function is to point to a single executable with a long path.
TODO - look at my aliases and commands I run often and see how many of them can I symlink