I maintain a rule that all files above the repo must be inside a folder, with one exception: a README file. Including the code
folder, this typically results in no more than 5 folders; the project folder itself is kept organized and uncluttered.
Just a random person who likes building software and configuring Linux.
I maintain a rule that all files above the repo must be inside a folder, with one exception: a README file. Including the code
folder, this typically results in no more than 5 folders; the project folder itself is kept organized and uncluttered.
They are the project’s subfolders (outside of the Git repo):
code
contains the source code; version-controlled with Git.wiki
contains documentation and also version-controlled.designs
contains GIMP, Inkscape or Krita save files.This structure works for me since software projects involve more things than just the code, and you can add more subfolders according to your liking such as notes
, pkgbuild
(for Arch Linux), or releases
.
I tend to follow this structure:
Projects
├── personal
│ └── project-name
│ ├── code
│ ├── designs
│ └── wiki
└── work
└── project-name
├── code
├── designs
└── wiki
I recommend Peer Calls as an alternative. Peer Calls uses peer-to-peer communication similar to Jami. You can check out Peer Calls on Github for more info.
So, in short, the things I really like about it:
I wonder sometimes if the advice against pointing DNS records to your own residential IP amounts to a big scare. Like you say, if it’s just a static page served on an up to date and minimal web server, there’s less leverage for an attacker to abuse.
That advice is a bit old-fashioned in my opinion. There are many tools nowadays that will get you a very secure setup without much effort:
And of course, besides all these tools, the simplest way of securing public services is to keep them updated.
I’ve found that ISPs too often block port 80 and 443. Did you luck out with a decent one?
Rogers has been my ISP for several years and have no issue receiving HTTP/S traffic. The only issue, like with most providers, is that they block port 25 (SMTP). It’s the only thing keeping me from self-hosting my own email server and have to rely on a VPS.
If you want a similar editor on Linux, then I suggest Kate. If Vim and Emacs didn’t exist, I’d be using Kate.
Notepad++ is a fabulous software program that had no complete alternatives on Linux. I used it for scripting, text manipulation, note taking, dumping and editing thoughts. Scintilla-based equivalents Geany, SciTE exist, but do not come close.
Really? No alternatives on Linux? Have you tried Emacs? I think Emacs with Org mode blows Notepad++ out of the water in all the uses you just mentioned.
First of all, doesn’t Navidrome have authentication? So, I don’t see why exposing it to the public is a problem.
Second, some reverse proxies support basic auth. This way, you can password-protect some services and is useful if the service does not have its own authentication. Here as an example snippet for Caddy:
example.com {
basic_auth {
# Username "Bob", password "hiccup"
Bob $2a$14$Zkx19XLiW6VYouLHR5NmfOFU0z2GTNmpkT/5qqR7hx4IjWJPDhjvG
}
reverse_proxy myservice:8000
}
You’ll have to look up the docs for other reverse proxies.
Probably or probably not. The only way to find out is to try. I’ve installed RetroPie on a number of old laptops; the oldest one being a 2002 Toshiba laptop. I got to play GBA games just fine with it.
If you need S3-compliant storage for testing and development, you can use an S3 mock server. I’ve tried the following for use in web development and CI environments, they are lightweight and configurable:
There is also Localstack. I found this one to be a bit more complex than the ones above and ended up not sticking with it.
Pretty much the same for me: bleeding-edge Arch for my workstation, rock-stable Debian for my server.