Devops is a meaningful term
Devops is a meaningful term
Your current setting is the “loopback” address. You’re listening for traffic to this address, and the only thing that can send to the loopback is yourself. This is a safe default, it means only the computer running the software can talk to it. Generally 0.0.0.0 listens on all available addresses. If that doesn’t work, use your local / internal ip.
This ui smells like it’s trying to hide the implementation details, but that makes things extremely difficult when troubleshooting
I have a nectar. It’s extremely meh. I don’t think it’s real memory foam.
You can reduce doorknob turning dramatically by running on a non-standard port.
Scanners love 80 and 443, and they really love 20, but not so much 4263.
I used to run a landing page on my domain with buttons to either the request system / jellyfin viva la reverse proxy. If you’re paranoid about it, tie nginx to a waf. If you’re extra paranoid, you’ll need some kind of vpn / ip allow-listing
That looks promising. Just keep in mind that this will take a very long time to run. I believe there is a *arr out there that can manage this / show progress, but the name escapes me
Adding - triple check / proofread / rephrase the ai output. Assume the words may be used against you. If your manager is close with whomever reads the feedback, they could ask for “evidence” of any claims. You either need strong evidence, or to avoid any concrete claims. More vague more better / more defensible.
When dealing with children, the “oreo cookie” method works well - start with something nice, offer a “suggestion for improvement”, and then finish with something nice as well.
You’ll want to submit the politically correct version through official channels for traceability. After it’s submitted there, you can give a copy over slack. Don’t let anyone make any claims about what you supposedly said over slack dm. Leave a paper trail.
You’ve already been PIPed, so they have reason to look at you. Play nice and check the boxes; I would do the feedback even if the submission is entirely “yeah it was fine” level bs.
All of the above is playing it safe. Offer to provide additional feedback / “discussion” over a voice call as well, and ask what they’re looking for. If they’re building a case against your former manager, you can be honest.
If they just want “general” feedback, or they want it over text (“no time for a call”), or there are multiple people in the room, or the call is being recorded, then fall back to the politically correct version you already submitted.
Your nuclear button is to claim the PIP was retaliation for (something; you can make this up, just make it realistic), but you don’t press that button unless you’re about to be fired. It makes things extremely complicated.
I really hate office politics, but half of being promoted is knowing how to play this stupid game :(
It is not too hard and you can definitely do it! It’s like a puzzle - you will get stuck at times, but if you keep going then you’ll get there.
APK files are just zip files, so you can unzip it to see its contents. From there, a java de-compiler get you a version of the source code. It will have random variable names and no comments, so it will take some digging to find and reverse the api layer.
Or, who knows, you could get lucky and find an openapi spec file and auth.txt. Worse apps have been developed.
Hey! Best of luck, I’m actually going down the same road at the moment :)
I would build it yourself - it’s more fun, and is cheaper than renting over a shorter-than-you-would-think time period.
The first thing to know is whether or not you can port-forward / if your isp has you behind nat.
Exposing virtual disks is relatively straightforward, or even just storage quotas on a single disk. I’m about to jump into the wide world of zfs; I need to glue together 4+ disks into a single storage array.
If you want everyone to have a separate VM, you’ll need some kind of hypervisor underneath. Could you grant everyone a user account in a single system, and use docker for separation?
It sounds like the others will be connecting remotely - make sure you use ssh keys (not passwords) and disable root over ssh. Once ssh is exposed to the internet, you’ll see a lot of failed login attempts
The VPN catches all network traffic and puts it far away - you can’t be on vpn and see local network resources (casting targets) at the same time.
If your vpn has an app, check your settings for something like “local network access”.
Otherwise, start reading about split-tunnels and/or default gateways
I gave their protocol page a look; it’s extremely in-depth. I have no idea what a vector clock is but now I get to learn. I like how they explain why blockchain isn’t a good fit.
I’m a touch worried about the extensability of the protocol, but I haven’t given it a deep read yet. I very much appreciate the share!
At EoL, corporate security tells the IT department to uninstall it.
Windows works great because MS tapes it back together slightly faster than it falls apart.
When EoL hits, those devices are either trashed, firewalled into oblivion, or assimilated into the kube.
Wanna come configure optimus for me?
I think we’ll see some very cool stuff start to happen once Veilid’s block storage is off the ground
I have a whole rant on this topic, but the short version:
It’s dentists.
The gnarliest mountain man, who hunts bears with his bear hands, can be brought to his knees with a toothache. The toothache never sleeps, can’t be fought, and always eventually wins. Even basic dentistry is life saving - even another human with a pair of pliers and some moonshine - but I’d much rather have novocaine.
Yes - the nodes are obsidian pages (markdown files), this view is a napkin-type layout thing that is built in; I haven’t played much with it
You’re running docker inside a vm? Why?
The first thing I would do is learn the 5-layer OSI model for networking. (The 7-layer is more common, but wrong). Start thinking of things in terms of services and layers. Make a diagram for each layer (or just the important layers. Layers 3 and up.)
If you can stomach it, learn network namespaces. It lets you partition services between network stacks without container overhead.
Using a vm or docker for isolation is perfectly fine, but don’t use both. Either throw docker on your host or put them all in as systemd services on a vm.
This will go about as well as broadcom’s acquisition of Symantec (not well).
If you can get rid of vmware, you will have to, and if you can’t, you’ll ship buckets of benjamins to broadcom and in return they might keep your company alive.
I recently picked up a pipe. It has all the rituals and escapism of a cigar, without the hour-long commitment.
That being said, sometimes being”occupied” for an hour is part of the appeal. Each has their place ime.