Default config is defined in the firmware. It can’t be deleted or changed (well, easily. I think there is a reseller option to have a custom default config).
The “no default config” means the default config will not be applied after the reset.
If you reset it again without checking “no default config”, then the default config will be applied.

“No default config” is very useful for applying your own config script. It gives you a blank canvas, making scripting a lot easier!

I have my “config.rsc” file that has the required configuration. And I have a “reset.auto.rsc” file that only has the command to reset the mikrotik with no defaults and to run the “config.rsc” script after reset.
“filename.auto.rsc” will be executed as soon as it gets FTPd (it’s a feature of mikrotik).
I use a bash script that FTPs the config.rsc file to the mikrotik, then the reset.auto.rsc file.
Makes it trivial to tweak the config then apply it, and I get all the config for the devices in easy to edit/diff script files.

To me, something like visual studio is an ide.
Out of the box it can run and debug c# programs. I can step through line by line, I can add breakpoints, I can watch variables.
It is a great experience for developing c#.

To get vscode to do that requires a lot of configuration.
Sometimes all that config is done by only 1 plugin.
The fact that there are really well made plugins for so many different languages and frameworks is vscodes power. I don’t just get a js/ts/node/deno ide, but it can be super tailored to Vue/react/svelte/quasar/nuxt/next/whatever.
All while in a familiar editor, and without having to install another program.

That’s what I mean by vscode not being an IDE.
Vscode has the ability to be an IDE, but it’s 3rd parties that actually do the work to achieve this.

Platformio is an IDE based on VSCode.
VSCode CAN be an IDE.
But it isn’t natively an IDE

The best thing is: if something doesn’t work, you tweak the compose file instead of having to retype or edit a command.

And you can have a GitHub of your compose files and any supporting config files.

I don’t get how some people can raw dog a docker run command!

I’d vote for the EU in a heartbeat.
I’d be fine with the euro, actually going full metric.

Brollywood is an excellent pun.

British Hollywood - a portmanteau.
Brolly Wood - brolly is an umbrella in British slang.

Sorry for dissecting this frog. I just want to make sure everyone can appreciate how delicious the pun is.

Which applies to EU countries.
Not sure if apple is going to do separate builds for separate regions

If you want remote access to your home services behind a cgnat, the best way is with a VPS. This gives you a static public IP that your services connect to, and that you can connect to when out and about.

If you don’t want the traffic decrypted on the VPS, then tunnel the VPN back to your homelab.
As the VPN already is encrypted, there is no point in re-encrypting it between the vps and homelab.

Rathole https://github.com/rapiz1/rathole is one of the easiest I have found for this.
Or you can do things with ssh tunnels.

For VPN, wireguard is very good

This is what “cutting red tape”, “smarter regulation” and “taking back control” means.

Like I said, impressive work.
Converting science to shaders is an art.

I guess your coding standards follows scientific standards.
And I guess it depends on your audience.

I guess the perspective is that science/maths formulae are meant to be manipulated. So writing out descriptive names is only done at the most basic levels of understanding. Most of the workings are done on paper/boards, or manually. Extra letters are not efficient.
Whereas programming is meant to be understood and adapted. So self-describing code is key! Most workings are done within an IDE with autocomplete. Extra letters don’t matter.

If you are targeting the science community with this, a paragraph about adapting science to programming will be important.
Scientists will find your article and go “well yeh, that’s K2”. But explaining why these aren’t named as such will hopefully help them to produce useful code in the future.

The fun of code that spans disciplines!

Edit;
Om a side note, I am terrible at coding standards when I’m working with a new paradigm.
First is “make it work”, after which it’s pretty much done.
Never mind consistent naming conventions and all that.
The fact you wrote up an article on it is amazing!
Good work!

Interesting.
I love creative applications of shaders. They are very powerful.

In my opinion only, but willing to discuss.
And I’ll preface this by saying if I tried to publish a scientific paper and my formulas used a bunch of made up symbols that are not standardised, I imagine it would get a lot of corrections on peer review.

So, from a programming perspective, don’t use abbreviations.
Basically working on naming.

I can read that TAU is the diffusion rate due to a comment. Then I dig further into the code as I am trying to figure something out and I encounter tau. Now I have to remember that tau is explained by a comment, instead of the name of the variable. Why not call it diffusionRate then have a comment indicating this is TAU.
A science person will be able to find the comment indicating where it is initialised and be able to adjust it without having to know programming. A programming person will be able to understand what it does without having to know science things.
Programming is essentially writing code to be read.
It’s written once and read many times.

Similar with the K variables.
K is reactionRate.
K1 is reactionKillRate.
K2 is reactionFeedRate.
Scientists know what these are. But I would only expect to see variables like this in some bizarre nested loop, and I would consider it a code smell.

The inboundFlow “line” has a lot going on with little explanation (except in comments). The calculation is already happening and going into memory. Why not name that memory with variables?
Things like adjacentFlow and diagonalFlow to essentially name those respective lines.
Could even have adjacentFlowWeight and diagonalFlowWeight for some of those “magic numbers”.
Comments shouldn’t explain what is happening, but why it’s happening.
The code already explains what is happening.
So a comment indicating what the overall formula is, how that relates to the used variables, then the variables essentially explain what each part of it is.
If a line is getting too complicated to be easily understood, then parting it out into further variables (or even function call, tho not applicable here) will help.
I would put in an editted example, however I’m on mobile and I know I will mess up the formatting.

A final style note, however I’m not certain on this.
I presume 1. and 1.0 are identical representing the float value of 1.0?
In which case, standardise to 1.0
There are instances of 2.0 and 2.
While both are functionally identical, something like (1.0, 1.0, 1.0) is going to be easier to spot that these are floats, as well as spotting typos/commas - when compared to (1., 1., 1.,).
IMO, at least

It’s from 2015, so its probably what you are doing anyway

I would say the more regular expiration and renewal of an LE cert is better.
It’s an ongoing check instead of an annual check.

At the homelab scale, proxmox is great.
Create a VM, install docker and use docker compose for various services.
Create additional VMs when you feel the need. You might never feel the need, and that’s fine. Or you might want a VM per service for isolation purposes.
Have proxmox take regular snapshots of the VMs.
Every now and then, copy those backups onto an external USB harddrive.
Take snapshots before, during and after tinkering so you have checkpoints to restore to. Copy the latest snapshot onto an external USB drive once you are happy with the tinkering.

Create a private git repository (on GitHub or whatever), and use it to store your docker-compose files, related config files, and little readmes describing how to get that compose file to work.

Proxmox solves a lot of headaches. Docker solves a lot of headaches. Both are widely used, so plenty of examples and documentation about them.

That’s all you really need to do.
At some point, you will run into an issue or limitation. Then you have to solve for that problem, update your VMs, compose files, config files, readmes and git repo.
Until you hit those limitations, what’s the point in over engineering it? It’s just going to over complicate things. I’m guilty of this.

Automating any of the above will become apparent when tinkering stops being fun.

The best thing to do to learn all these services is to comb the documentation, read GitHub issues, browse the source a bit.

Bitwarden is cheap enough, and I trust them as a company enough that I have no interest in self hosting vaultwarden.

However, all these hoops you have had to jump through are excellent learning experiences that are a benefit to apply to more of your self hosted setup.

Reverse proxies are the backbone of hosting and services these days.
Learning how to inspect docker containers, source code, config files and documentation to find where critical files are stored is extremely useful.
Learning how to set up more useful/granular backups beyond a basic VM snapshot in proxmox can be applied to any install anywhere.

The most annoying thing about a lot of these is that tutorials are “minimal viable setup” sorta things.
Like “now you have it setup, make sure you tune it for production” and it just ends.
And finding other tutorials that talk about the next step, to get things production ready, often reference out dated versions, or have different core setups so doesn’t quite apply.

I understand your frustrations.

I’ve been meaning to play with rust, and I’ve always enjoyed tinkering with various MCUs… Although I’m not very strong with firmware/embedded programming.

Do you think programming an ESP32 is a good project for learning rust?
Any suggested place to start? (Tutorials, YouTube Vida etc)

Nano is useful because it is everywhere.
There are better editors, but being familiar with nano and it’s shortcuts means you can edit files pretty much anywhere.
Same with knowing the basics of vim (like being able to edit, exit and save)

Oh, this looks great!
I’ve been struggling between customize and helm. Neither seem to make k8s easier to work with.

I have to try cuelang now. Something sensible without significant whitespace that confuses editors, variables without templating.
I’ll have to see how it holds up with my projects

If your windows computer makes an outbound connection to a server that is actively exploiting this, then yes: you will suffer.

But having a windows computer that is chilling behind a network firewall that is only forwarding established ipv6 traffic (like 99.9999% of default routers/firewalls), then you are extremely extremely ultra unlucky to be hit by this (or, you are such a high value target that it’s likely government level exploits). Or, you are an idiot visiting dogdy websites or running dodgy software.

Once a device on a local network has been successfully exploited for the RCE to actually gain useful code execution, then yes: the rest of your network is likely compromised.
Classic security in layers. Isolatation/layering of risky devices (that’s why my homelab is on a different vlan than my home network).
And even if you don’t realise your windows desktop has been exploited (I really doubt that this is a clean exploit, you would probably notice a few BSOD before they figure out how to backdoor), it then has to actually exploit your servers.
Even if they turn your desktop into a botnet node, that will very quickly be cleaned out by windows defender.
And I doubt that any attacker will have time to actually turn this into a useful and widespread exploit, except in targeting high value targets (which none of us here are. Any nation state equivalent of the US DoD isn’t lurking on Lemmy).

It comes back to: why are you running windows as a server?

ETA:
The possibility that high value targets are exposing windows servers on IPv6 via public addresses is what makes this CVE so high.
Sensible people and sensible companies will be using Linux.
Sensible people and sensible companies will be very closely monitoring what’s going on with windows servers exposed by ipv6.
This isn’t an “ipv6 exploit”. This is a windows exploit. Of which there have been MANY!

Ah, I think it’s like “keep track of 7 items, the 8th might push something else out” ( https://en.m.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus_or_Minus_Two ).

So like mind-map-complexity.
Like, when you are trying to figure out some bullshit OOP inheritance, you are 9 levels deep and have no idea what the original problem was, but you feel like you have made a connection to the solution, but now you have to backtrack everything (or figure out where your last edit was) to try and figure out what that connection actually means and what you have to do now