I use Hugo, it’s not super complicated.
You basically just define templates in pseudo html for common content (header, nav panel, footer, etc), and then you write your articles in markdown and Hugo combines the two and outputs actual html files.
You also have a content folder for js, css, and images which get output as is.
That’s about all there is to it, it’s a pretty minimalist static site generator.
Hosting wise you can just put it on github pages for free.
Regardless of budget, I have found the following setup has afforded me all the comfort upsides of mobility and console gaming, with none of the performance downsides.
Build a standard desktop gaming pc to your budget, setting aside ~$150, give or take.
Make sure it’s wired into your network and not using wifi. Setup Steam on it as usual.
3a. (Console experience) Buy a Google TV with Chromecast, or whatever it’s called now. Install Steam Link app on it and connect it to your gaming pc. Get a Bluetooth compatible Xbox controller, connect it to the chromecast. Enjoy a console experience with your gaming pc. If you have the chromecast on a wired ethernet lime you’ll have maybe 1ms of input lag, very playable.
3b. (Laptop experience), buy a dirt cheap laptop, install steam on it, use Steam Streaming fu ctionaloty to stream from gaming pc to laptop. If you plug the laptop into ethernet you should have sub 1ms input lag.
This let’s you get all the horsepower of a gaming pc, at gaming pc hardware prices, but the portability of a laptop and/or couch gaming comfort of a console.
And since it’s all centralized to your 1 “server” machine, of you make changes in setup A (ie change am in game setting or etc), it’ll persist even if you swap over.
IE if I change my settings or preferences on the console, I’ll persist that over on my laptop and won’t have to change it again.
Furthermore no network save game synching needed, no waiting for a game to download a second time, no need to update the fane multiple times, etc.
It’s all centralized to your own core machine and everything else is just a thin client.
PS: this works with the Steam Deck too, you can stream from gaming pc to steam deck and use it as a thin client 👍
Personally I’ve just being using Termux sideloaded in to SSH into anything I need to, with a bluetooth KB and Mouse.
Quest3 straight up supports Mouse+KB as is.
SSHd into my dev box I can pop open neovim in tmux multiplexer and have full access to my entire stack, so at that point it’s just full on cyber decking.
Only thing that could be nice is finding out how well the usb port on the Quest3 plays with Serial feeds.
It should work in theory, I just haven’t tried it yet, but theoretically android devices can use a usb port as a serial COM1 and there’s a handful of decent TTY serial IO apps on Android, any of which could be sideloaded in.
Or… use a TTY in termux maybe? I haven’t tried it yet but theoretically it outta work
Dunno why ppl are down voting you, this is 100% the way.
Architecture as code is amazing, being able to completely wipe your server, re-install fresh, and turn it on and it goes right back to how it was is awesome.
GitOps version controlled architecture is easy to maintain, easy to rollback, and easy to modify.
I use k8s for my entire homelab, it has some initial learning curve but once you “get it” and have working configs on github, it becomes so trivial to add more stuff to it, scale it up, etc.
Might wanna read it again, it’s right there :)
The best architectures, requirements, and designs emerge from self-organizing teams.
It’s an incredibly critical part companies love to completely ignore.
If you assign devs to teams and lock em down, you’ve violated a core principle
And it’s a key role in being able to achieve these two:
Agile processes promote sustainable development.
And
The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
This is talked about at length by the likes of Fowler, who talk about how locking devs down us a super fast way to kill sustainable development. It burns devs out fast as hell.
Note that it’s careful not to say on the same project
That’s actually a pretty important part of its original premise.
It’s a big part of why scrum meetings were a thing, as the expectation was any curious dev could just join in to see what’s up, if they like.
Not tying devs down to 1 specific thing is like the cornerstone of agile, and over many years of marketing and corporate bastardization, everyone had completely forgotten that was literally the point.
The whole point of the process was to address 2 things:
That client requirements can’t easily be 100% covered day one (But you still need to get as many as you can!)
To avoid silo’ing and tying devs down to specific things, and running into the one bus rule (“how fucked would this project be if <dev> got hit by a bus?”)
And the prime solution posited is to approach your internal projects the same way open source works. Keep it open and available to the whole company, any dev can check it out, chime in if they’re familiar with a challenge, etc.
One big issue often noted in non-agile companies (aka almost all of them) is that a dev slent ages hacking away at an issue with little success, only to find out far too late someone else in the company already has solved that one before.
An actually agile approach should be way more open and free range. Devs should be constantly encouraged to cross pollinate info, tips, help each other, post about their issues, etc. There should be first class supported communication channels for asking for help and tips company wide.
If your company doesn’t even have a “ask for help on (common topic)” channel for peeps to imfoshare, you are soooooooo far away from being agile yet.
I’ve literally never actually seen a self proclaimed “agile” company at all get agile right.
If your developers are on teams that are tied to and own specific projects, that’s not agile.
If you involve the clients in the scrum meeting, that’s not agile.
If your devs aren’t often opening PRs on a variety of different projects all over the place, you very likely aren’t agile.
If your devs can’t open up a PR in git as the way to perform devops, you aren’t agile.
Instead you have most of the time devs rotting away on the sane project forever and everyone on “teams” siloed away from each other with very little criss talk, devops is maintained by like 1-2 ppl by hand, and tonnes of ppl all the time keep getting stuck on specific chunks of domains because “they worked on it so they knpw how it works”
Shortly after the dev burns out because no one can keep working on the same 1 thing endlessly and not slowly come to fucking losthe their job.
Everyone forgets the first core principle if an agile workplace and literally its namesake us devs gotta be allowed to free roam.
Let them take a break and go work on another project or chunk of the domain. Let them go tinker with another problem. Let them pop in to help another group out with something.
A really helpful metric, to be honest, of agile “health” at your company is monitor how many distinct repos devs are opening PRs into per year on average.
A healthy company should often see many devs contributing to numerous projects all over the company per year, not just sitting and slowly be coming welded to the hull of ThatOneProject.
It does mean something.
The skibidi toilet “creatures” are considered the antagonists, and the word is associated with their traits.
Its an insult to and pretty much interchangeably with “creepy” with a splash of “cringe”
Often paired with “ohio” which means “bland” / " boring" / “mid”
Example:
“Yo he got that skibidi Ohio rizz”
Translation:
“This dude has zero game, in fact he is creepy and weird and has negative charisma, people find him repulsive and boring”
All the electronics inside are very much capable of combustion.
Your power supply inside the printer body for example can very much fail and burst into flames.
And tbh it’s not that uncommon for that to happen with 3d printers. They’re often made with very cheap parts and prone to cheap work on the inside bits.
Add on how much of a high wattage load they meed to handle for extended periods of time and yeah, sometimes the inner wiring bursts into flames and the whole thing goes up.
I always recommend keeping a cheap lil smoke alarm directly overhead any 3d printer, seriously. Those fuckers can very much spontaneously burst into flames lol
None of this stops the risk of fire.
Once a fire starts, the printer turning off won’t magically stop the fire from continuing to grow.
Printers can fail in all manner of ways.
Also, you should have a venting solution of printing ASA.
It’s pretty cheap to get a proper fire resistant heat cover for a printer.
Just get an emergency “space blanket”, they’re often only a couple bucks and quite good, but very fire resistant.
… no? I was asking a serious question.
Who tabled this bill, and who is supporting it?
Others have covered the fact it’s because of air pressure but haven’t fully answered why that is the way it is.
It’s simple really.
The force of gravity is also at play. As you go higher up, gravity gets weaker as you get farther from the earth’s centre.
And it is that gravitational force that increases the air’s density, same reason why if you keep going down in the water, the water gets denser.
For the heat to move around you need to be in a sort of goldilocks zone of density.
It needs to be dense enough that the fluid molecules can move around and spread the convection energy around… but not so dense they can’t move much either.
Furthermore there’s actually a couple different layers of our atmosphere.
First at our level is the troposphere, where heat is absorbed into the ground itself and radiated back out, as well as the perpetual heat from the earth’s core, and reflected off the ground too (visible light).
The troposphere is warm and gets colder as you get farther away from the earth’s surface, naturally. That heat is absorbed by the air itself so, as you get farther away it gets colder as it has more air to travel through.
Up higher is the Stratosphere, where it’s ice cold and the air thins out.
However we get a sudden uptick in temp as we go even higher into what is called the Stratopause, back to briefly warm temperatures between the Stratosphere and the Mesosohere. Why? How?
Simple, this is the little sweet spot Ozone molecules hang out, forming a protective convenient bubble around the earth. Ozone absorbs Ultraviolet light from the sun and turns out that stuff is HOT, so there’s a band of a hot zone right above and below the Ozone layer. Think of it as a toasty little bubble around us.
Above is the mesosphere which cools off again and gets back to being really frosty quickly, for the same reason the Stratosphere did, distance.
Then we hit the mesosphere, which is effectively the point when the atmosphere is so thin it stops protecting and is the “outside” of our protective blanket.
You can imagine this like earth being wrapped in a blanket, and the mesosphere is everything outside the blanket. Without any protection you are subject to the unbridled radiation of the sun which means you go back to being really toasty, as you get a bit higher you are effectively in space now and will soon enough hit temps that just cook you alive in a minute or two. Really bad sunburn zone.
So to answer the question overall:
Hot air rises… but only when there is air to rise.
Top of the mountains just don’t have enough air anymore for it to really rise much more. It still does but the hot air rising effect just gets weaker and weaker as the air gets thinner due to less gravity.
I have been using Reolink RC-522s outside in the harsh Canadian cold winters. Even at -40 they kept working and their quality hasn’t degraded.
I tried out q few options for NVR software, and I’ve settled on Frigate NVR, it was pretty painless to setup and “just worked”.
Shinobi I found worked at first but three times it shit the bed, silently failed one day, and just stopped working. I’d wipe and re-install and it’d just fail after awhile. Frigate has never had this issue so far.
I use Power over Ethernet for the cameras, so i only had to run 1 single cable (ethernet) to each camera outside, no need to run high voltage which makes it way easier to install.
I use a small mini itx PC as the NVR with a 960ti installed in it for transcoding.
I have a fancy managed 48 port gigabit poe switch which is overkill for just cameras (I have tonnes of other PoE devices on my network as well justifying it), but any “dumb” gigabit poe switch will work for you, as long as you have enough ports for your cameras.
I personally use kubernetes for my machines running self hosted apps, but for most folks that’s overkill abd you can just use docker compose!
I was about to write this but you took the words right out of my mouth, so I will just write “this ^”
Do people seriously still think this is a thing?
Literally anyone can run the basic numbers on the bandwidth that would be involved, you have 2 options:
They stream the audio out to their own servers which process is there. The bandwidth involved would be INSTANTLY obvious, as streaming audio out is non-trivial and anyone can pop open their phone to monitor their network usage. You’d hit your data limit in 1-2 days right away
They have the app always on and listening for “wakewords”, which then trigger the recording and only then does it stream audio out. WakewordS plural is doing a LOT of heavy lifting here. Just 1 single wakeword takes a tremendous amount of training and money, and if they wanted the countless amount of them that would be required for what people are claiming? We’re talking a LOT of money. But thats not all, running that sort of program is extremely resource intensive and, once again, you can monitor your phones resource usage, you’d see the app at the top burning through your battery like no tomorrow. Android and iPhone both have notifications to inform you if a specific app is using a lot of battery power and will show you this sort of indicator. You’d once again instantly notice such an app running.
I think a big part of this misunderstanding comes from the fact that Alexa/Google devices seem so small and trivial for their wakewords.
What people dont know though is Alexa / Google Home have an entire dedicated board with its own dedicated processor JUST for detecting their ONE wake word, and not only that they explicitly chose a phrase that is easy to listen for
“Okay Google” and “Hey Alexa” have a non-trivial amount of engineering baked into making sure they are distinct and less likely to get mistaken for other words, and even despite that they have false positives constantly.
If thats the amount of resources involved for just one wake word/phrase, you have to understand that targeted marking would require hundreds times that, its not viable for your phone to do it 24/7 without also doubling as a hand warmer in your pocket all day long.
Have the device treat those like wake words just like Alexa
You do understand how incredibly difficult this is right?
They genuinely looked identical to me.
Either way, gogs dies what I need it to, git server for backing up my code and super basic git web Hooks to trigger my build server.
Couldn’t ask for anything more.
Gogs and Gitea are very similiar, Gitea is a fork of Gogs with a bit more features as I understand it.
However when I tried to get Gitea working personally a year and a half ago, it had some rough issues with redirect looping onto itself infinitely, could never get it to work.
On the other hand Gogs didn’t have this issue, and was much more painless to stand up, so it’s what I use now.
I’ve been looking for th8s for awhile too.
Not a locally run tool, but a self hosted web app (that I wire up to my self hosted db) that has a web portal I login to, and then can manage my db with a nice slick UI to define tables, relations, etc.
There’s been some I’ve found but they vastly lacked basic features and were clearly in very early beta.