So, you need a unix time value followed by 000?
That first part you can calculate with date +%s -d '2024-07-02 12:00'
.
So, you need a unix time value followed by 000?
That first part you can calculate with date +%s -d '2024-07-02 12:00'
.
That’s just sloppiness.
The information that familiarity gives you is “WTF does this field means”, and it’s the only thing that’s actually there. How you get a value and how a value is formatted are things no amount of expertise will save you from having to tell the computer, and thus you can’t just forget about.
(And let me guess, the software recommended install is a docker image?)
I’m just not sure what the middle guy would be saying
“I hate inheritance! I hate inheritance! I hate inheritance! I hate inheritance!”
But well, inheritance goes brrrrrr.
“Log” is the name of the place you write your tracing information into.
Let me introduce you to syslogd.
But well, it’s probably overkill, and you almost certainly just need to log on a shared volume.
The sheer number of people that do not expect a joke on this community… (Really, if you are trying to learn how to program pay attention to the one without the Humor
on the name, not here.)
Well, I guess nobody expects.
That *++
operator from C is indeed confusing.
Reminds me of the goes-to operator: -->
that you can use as:
while(i --> 0) {
Hum, no. The last thing I need on the world is a piece of non-working hard to maintain software.
I’d write something before trying Nextcloud again.
Personally, I’d really like if it could have different users on its management interface, with their own file shares.
It’s understandable why they don’t bother, but I would like to share my NAS without running several instances.
I’ll second people here in pointing that you are better allowing calls from your family during the “Do Not Disturb” than trying to set-up things not to call you during that time. Your phone almost certainly has a setting that allows “favorite contacts” or something like it.
It has a better configuration orthogonality :)
Yeah, that’s not a good reason.
It’s much easier to authorize a key than to input your password on every kind of interaction.
This is the internet. If you poke the bear, somebody will come-up with a completely reasonable use case of password authentication that happened once somewhere on the world.
If you don’t have any good reason not to, always set your SSH server to only authenticate with keys.
Anything else is irrelevant.
Oh, sure, the bloat on your images requires resources from the host.
There is the option of sharing things. But, obviously that conflicts a bit with maintaining your environments isolated.
FileZila has relied in a distribution channel that has turned untrustworthy a while ago.
Since then, they migrated the project. But somebody that doesn’t know what they are doing isn’t sure to get a good version of it.
Just about this part:
Or you might set up an sFTP service to accept a GUI connection from a client like FileZilla.
FileZilla has been a troublemaker for decades (not because the software itself, but the OP won’t get it right), and sFTP requires an extra service.
I’d recommend he get WinSCP or another scp client.
Do not run databases in Docker unless you know really well what you are doing.
It’s completely possible to run them correctly in Docker. But it’s far from trivial, and if you need to ask this, it means that you probably won’t be able to.
Hetzner. But it looks like the problem is created by the pair (hoster, ISP), and neither of them have a problem by themselves.
I get the throughput I brought from my ISP. But latency to my VPS is 260ms.
It probably means you can complain any time about a manufacturing defect, but not anything else.
Anyway, the terms should be printed somewhere on the box or in a paper inside.