I do have nightly off-site backups, that’s true. Still, having the git repo be on the same machine doesn’t seem right to me.
I do have nightly off-site backups, that’s true. Still, having the git repo be on the same machine doesn’t seem right to me.
That would fill the same role as watchtower I guess? I’ve previously tried to have a look at having portainer manage the docker compose stack that it’s running inside but at least back then it seemed to be a dead end and not really what portainer is meant to do. I’m not interested in moving away from docker compose at this time.
I’d be a bit concerned with having the git repo also be hosted on the machine itself. If the drives break it’s all gone. I could of course have two remotes but then pushing changes still becomes a multi step procedure.
Oh for sure for sure. I just know that a lot of people use their homelab to learn skills that they can put on their resume when looking for a job. It’s totally fair to over engineer your self hosting setup if that’s your goal.
You should definitely figure out some infra as code system now while it’s manageable. Normally I’d recommend docker-compose as it’s very easy to learn and has a huge ecosystem, but since you’re using proxmox you might need to look at ansible like the other commenter said. Having IaC with git makes it so much easier to test new stuff, roll changes back, and all that good stuff, in addition to solving your original problem of forgetting what is running where.
Just find the simplest IaC solution possible. Unless you are gunning for a job in infrastructure you don’t need to go into kubernetes or terraform or anything like that, you just need something reproducible that you can easily understand and modify.
While this sounds right, it is probably a path to depression. At this point I’m pretty much qualified for any web dev job I want, and I know I’d be one of the best hires they ever made, but I also know the interview gods are fickle bastards. I can easily see myself getting a string of rejections and taking a hard hit to my mental health.
An interview is not a fair assessment of your skill and fit, it’s just the best tool we have for the job. Therefore, don’t let the outcome of interviews tell you how good you are or what you’re ready for. Imo you kinda just know these things.
As for OP, sounds like they’re maybe still learning rule 1 of software development; the job is 90% figuring out how to do shit, it’s not actually so much about what you already know, although that certainly helps with the figuring out part. Once you’ve figured out how to figure out most of the problems that come up in your job, you’re more than ready for a new challenge, if you want one.
Is it still confusing after my new explanation? The posts are hidden because they’re marked as read for me, and I’m trying to clear the read posts for a community so they won’t be hidden anymore.
No, I didn’t say that. I’m unsure where the confusion arises so I’ll start from the beginning. And try to clarify my problem.
Let’s take a specific community, doctor who @ lemmy.world. This community is the main reason I’m having a problem, because usually I’ll see a post on my feed from there before I watch an episode, so I want to read it later, but when I scroll past the post it gets marked as read. Now once I’ve gone and watched the episode, I’d like to go back to the community to read the post I skipped before. Of course that post is hidden, because it got marked as read when I scrolled past it. That’s when the button from point 3 seems like it should allow me to unhide the post, but it doesn’t work. I can verify that the post does still exist if I just visit that community in a web browser instead of in boost.
It’s a setting you can turn on where it doesn’t show posts you’ve already read
I feel like this wasn’t even that long ago? I was quite surprised when my content suddenly started being sponsored by them again.
I’ve accidentally opened enormous single line json files more than once. Could be lsp config or treesitter or any number of things but trying to do any operations after opening such a file is not a good time.
Respectfully, no. Rust is great for some things and Python is great for other things. Switching to rust is not a solution to missing exception linting in another language.
That’s way harder to ask for. A docstring solution is fine so long as the linters know to pick it up.
Well at least php has it, which is a JITed scripting language just like Python. Although saying php has it is wrong, it’s just a special doc tag that the linters pick up. Which is exactly what I want for Python. The only other scripting language I’m very comfortable with is typescript, which can also support @throws
via jsdoc and eslint.
So to answer your question, I don’t know if it’s common, but from my minimal sample pool it’s at least not unheard of.
You may not know this (just guessing because you commented on the nature of scripting/interpreted languages) but static analysis of dynamic languages has come really far and is an indispensable part of any reasonably sized project written in them these days. That’s another reason why I’m so surprised and frustrated by the lack of this in Python.
Except if it’s a single line file, only god can help you then. (Or running prettier -w
on it before opening it or whatever.)
I believe raises is the de facto Python version of throws
, but no tools seem to exist to actually handle it.
Day 598 of asking for a way to tell which functions throw exceptions in Python so I can know when to wrap in try catch. Seems to me that every other language has this, but when I’ve asked for at least a linter that can tell me I’m calling a function that throws, the general answer has been “why would you want that?”
How am I supposed to ask for forgiveness if it’s impossible to know that I’m doing something risky in the first place?
That’s a very good point!
Ignorant question: isn’t alt text primarily for visually impaired people? If so, what is the point of including info about color?
I’m sorry but this is hilarious. You spent less money and you got less food? Fascinating 😄