shatteredspace
Ansible - Deploying VMs on-prem and in the cloud, creating a managed-k8s cluster in the cloud, deploying k8s on-prem, possibly bare-metal server provisioning. Configuration of resources for all of the above.
Nomad - Alternative to K8s from Hashicorp (supposed to be simpler, I wouldn't know as I've never used it).
Tailscale - VPN provider
Where would you use these tools your day-to-day? If you aren't deploying VMs, containers, bare-metal servers, or making configurations to the above - you would probably be looking to pick these tech stacks up as a hobby.
Resources - While I always check the sources first, I'm not a fan of the Ansible getting started docs. The list I run down for resources after the source (based on cost and quality)
- Online resources provided by a local library - was able to find a good Java reference for a recent project.
- Getting started books ( your OReillys, Manning Pub, Starch Press, etc)
- MOOCs
- Pluralsight, LinkedIn Learning ,etc.
- Youtube - CodeCamp, etc
What's a root could be a link you click on to give more information than a special x value when both side of the equation line up (a root is when the graph of a function crosses the x-axis).
I like imagery and the clicking to progress to the next portion. What would be fantastic in my opinion is to take the step-by-step approach of something like WolframAlpha and apply it to defined topics with a set of defined examples rather than hey provide us an answer and if you get it wrong we will take you through a rudiment branch that will take us back to the main branch.
What will the Code playground block be for (compilation?, interpretation? of code?).
I see playground and sandbox to be very similar, so it might be beneficial to change CodeSandbox to CodeEditor in the future.
In terms of flexibility, have you thought about allowing non-YouTube video links within the course material (Vimeo or otherwise)?
I see it as all about use-case, staffing, and what kind of instance you are using. Cloud-based? A-lot more freedom in being able to just deploying a cluster and not worry about much, on-prem based? Well dang now you've opened up having to be the one to update those nodes yourself - hope that you are a systems admin as well and have the time to perform said updates.
Situation A - I'd like to introduce you to Docker Swarm.
Secret management - sure K8s can do it, but I'm almost certain your organization as well as mine has accepted a vault of some sort that is not in K8s for end users and services to use. Now you just have to write your applications to use this.
Network policies - while K8s can do this, I don't know if this is the strongest argument to use K8s or just a nice cherry on top. It feels like just a shift in responsibility or adding more granularity from your network security team.
When does the situation call for it (in my opinion)? Your company has embraced the methodology of work with staffing for it and you have more than a handful of apps on more than a handful of nodes.
So while other software that isn't Microsoft most certainly has memory safety bugs, this blog doesn't speak for those, only Microsoft's.
The only part that Mozilla is indicated is in reference to Rust.
'terraform refresh' may be what you are looking for. This will update the state to match current configurations that may have been done outside of Terraform.
All that a plan does is evaluate what is going to change in the current Terraform state by performing a dry-run of the Terraform code that you have supplied.
If you would actually like to make changes to the Terraform state based on what the Terraform code evaluated then you run a Terraform apply - which will, for the resources deployed via Terraform, update the configurations themselves and update the Terraform state by using the Terraform code as the instruction set.
You can actually see this in action with plan and apply as the output will show you +,-, and ~ where ~ is settings that are going to change but are not new configurations or configuration to be removed.
Edit: Learned from some other comments that Terraform has a 'refresh' command that will take deploy+n time configurations done outside of Terraform and sync those configurations with the state. This might be what you ideally are looking for after deployments?
I wanted a platform that I could log into, that was fast, non-intrusive, that I could link my own domain to, and that was 'stuck' in 2005. I don't need anything shiny and honestly, for most things people blog about, a site that exists in circa 2005 is more than enough.
Maybe to you pluggable means an output object from a utility being the same input object as another utility? In this case, Unix isn't pluggable at all.
Let's say I have the client-side pick up the bill for logic/computing for form validation. Now for security reasons would I also want validation on the server-side as well due to the fact that client-side JavaScript can be manipulated? Or am I totally off-base in this line of thinking.
I'm personally opposed to how much logic happens on the client-side but I'm open to having conversation and changing my opinion on that.
I use my personal blog as my note taking location ([link redacted]). It uses blogger because I just wanted to get content published and available without worrying about theming.
Why do I need to fire up the terminal? Your OS doesn't do things via GUI like you do, so you need to validate that what it needs is available in the manner it will use.
Too damn hard and too opaque.? How did you learn that Node js was even a thing? You weren't born with the knowledge and everything has a learning curve to it, very few things are truly easy to do starting at the very bottom.
I agree that things need documentation and onboarding. I think we can view the Node js docs similar to a shop manual at a auto repair shop - it will expect you to know what tools are what and how to do certain things.
Should Chrome have Node JS loaded into it during install? I don't do web-dev so my answer is no.
Should there be browsers made for those learning web-dev that come with these? By all means, sure. Go nuts.
This also might sound elitist but I would expect the kind of person that takes an interest in coding to be able to google what $PATH is or hell take the complete instruction "add <dir> to $PATH"