Starfighter, starfighter@discuss.tchncs.de
Instance: discuss.tchncs.de
Joined: 3 years ago
Posts: 1
Comments: 24
Posts and Comments by Starfighter, starfighter@discuss.tchncs.de
Comments by Starfighter, starfighter@discuss.tchncs.de
Got it working thanks to your troubleshooting tips now. Also found a very neat way to handle secrets from another comment.
I tend to run a DB instance per service as that makes backup restoration much easier for me. An idle postgres sits at around 50MB which is a cost I’m willing to pay.
Thank you again for your help :)
Managed to get it working by passing in env vars from a secret now.
ArgoCD has a really handy web UI that allows you to quickly see what kind of resources get deployed.
Especially for learning k8s I found that much easier to visualize than raw kubectl outputs.
Passing in the secrets once via the global: section is very neat. Got it working now with a few of the other tips and stole your trick for my secret handling. Thank you :)
Did you also have to set all these env vars by hand?
I am wondering if it might have something to do with rendering Helm Charts under ArgoCD.
I’ll give it another try with your recommendations.
And should I get it working finally, I will obviously switch back to using Secrets.
I only removed them to reduce possible points of failure.
As for blueprints, that’s a task for future me xD
OrcaSlicer has things like Adaptive Cubic or Lightning patterns that have more infill near the walls.
The other members of that slicer family (BambuStudio, PrusaSlicer, etc) likely have them too.
Indeed
Losing both uv and ruff in one fell swoop sucks.
I’ve written my bachelors thesis with it.
You won’t get any official pre made templates for your thesis (yet) and if you require some obscure notation you probably won’t find a ready made package for it.
For my purposes I only needed some pictures and code blocks which works perfectly fine.
Also typst’s show rules are awesome.
Absolutely. Maybe a poor choice of words on my part. My intention was to state that this is not a thing you simply hang out in the wind and leave, but instead a vehicle that needs to be controlled to stay within its operational envelope.
I can imagine problems like tethers or lines getting crossed when the vehicle makes fast turns due to wind shear or frequent direction changes. You probably can’t operate it in those conditions.
You would think so but even normal ground-fastened wind turbines shut off when winds get too strong.
This being somewhat of an aircraft I absolutely expect them having to land it before storms roll in.
If you land it facing up- or downwards and deflate the balloon segments it would probably be fairly flat and compact for storage.
I have never used them but there are some tools that advertise being able to run GitHub Actions locally, like WRKFLW.
Und alle 39 der insgesamt 11 NichtsBS Nutzer sind hier
Also the normal and rpi versions are two completely independent implementations of the same software. So now the LLMs have twice the maintenance load.
I didn’t diff the two files but even the startup and control code appears to be custom for each version.
Its a fully electric drivetrain with a gas generator. When the battery runs low you can recharge it (even while driving) using the generator.
So you don’t have the complexity of a combined hybrid drivetrain, but instead a normal BEV one plus a power generator, both of which are very well understood problems.
Another benefit is that the generator can always run at its most efficient rpm/power point and is decoupled from the speed of the wheels.
Interestingly Wankel engines have been making a bit of a comeback for this purpose since they can be built more compactly for the same output power.
A drawback compared to hybrid drivetrains is that both components need to be built for “full” load, whilst a hybrid drivetrain can combine powers to reach maximum performance, meaning each of the motors only has to carry half (or part) of the total load.
Since projects of the same language often use the same tooling this makes it easier to clean up the whole directory by running something like this:
for d in ./*/ ; do (cd "$d" && somecommand); done
somecommand could be cargo clean if you’re in the Rust directory for example.
Depends on the exact system but there will be a method to switch to a newer release channel without reinstalling. Rinse and repeat every x years.
I assume you mean AVIF? Because AV1 is not an image (file) format but a video compression format (that needs to be wrapped in container file formats to be storable).
Metro Wolfenstein
Got it working thanks to your troubleshooting tips now. Also found a very neat way to handle secrets from another comment.
I tend to run a DB instance per service as that makes backup restoration much easier for me. An idle postgres sits at around 50MB which is a cost I’m willing to pay.
Thank you again for your help :)
Managed to get it working by passing in env vars from a secret now.
ArgoCD has a really handy web UI that allows you to quickly see what kind of resources get deployed.
Especially for learning k8s I found that much easier to visualize than raw kubectl outputs.
Passing in the secrets once via the
global:section is very neat. Got it working now with a few of the other tips and stole your trick for my secret handling. Thank you :)Did you also have to set all these env vars by hand?
I am wondering if it might have something to do with rendering Helm Charts under ArgoCD.
I’ll give it another try with your recommendations.
And should I get it working finally, I will obviously switch back to using Secrets.
I only removed them to reduce possible points of failure.
As for blueprints, that’s a task for future me xD
Authentik Helm woes
I’m currently in the long process of rebuilding my declarative homelab using k3s, ArgoCD and NixOS.
OrcaSlicer has things like Adaptive Cubic or Lightning patterns that have more infill near the walls.
The other members of that slicer family (BambuStudio, PrusaSlicer, etc) likely have them too.
Indeed
Losing both
uvandruffin one fell swoop sucks.Kree!
I’ve written my bachelors thesis with it.
You won’t get any official pre made templates for your thesis (yet) and if you require some obscure notation you probably won’t find a ready made package for it.
For my purposes I only needed some pictures and code blocks which works perfectly fine.
Also typst’s
showrules are awesome.Absolutely. Maybe a poor choice of words on my part. My intention was to state that this is not a thing you simply hang out in the wind and leave, but instead a vehicle that needs to be controlled to stay within its operational envelope.
I can imagine problems like tethers or lines getting crossed when the vehicle makes fast turns due to wind shear or frequent direction changes. You probably can’t operate it in those conditions.
You would think so but even normal ground-fastened wind turbines shut off when winds get too strong.
This being somewhat of an aircraft I absolutely expect them having to land it before storms roll in.
If you land it facing up- or downwards and deflate the balloon segments it would probably be fairly flat and compact for storage.
I have never used them but there are some tools that advertise being able to run GitHub Actions locally, like WRKFLW.
Und alle 39 der insgesamt 11 NichtsBS Nutzer sind hier
Indeed
Also the normal and rpi versions are two completely independent implementations of the same software. So now the LLMs have twice the maintenance load.
I didn’t diff the two files but even the startup and control code appears to be custom for each version.
Its a fully electric drivetrain with a gas generator. When the battery runs low you can recharge it (even while driving) using the generator.
So you don’t have the complexity of a combined hybrid drivetrain, but instead a normal BEV one plus a power generator, both of which are very well understood problems.
Another benefit is that the generator can always run at its most efficient rpm/power point and is decoupled from the speed of the wheels.
Interestingly Wankel engines have been making a bit of a comeback for this purpose since they can be built more compactly for the same output power.
A drawback compared to hybrid drivetrains is that both components need to be built for “full” load, whilst a hybrid drivetrain can combine powers to reach maximum performance, meaning each of the motors only has to carry half (or part) of the total load.
Since projects of the same language often use the same tooling this makes it easier to clean up the whole directory by running something like this:
somecommandcould becargo cleanif you’re in the Rust directory for example.Depends on the exact system but there will be a method to switch to a newer release channel without reinstalling. Rinse and repeat every x years.