• 0 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: July 4th, 2023

help-circle

  • pixxelkick@lemmy.worldtoSelfhosted@lemmy.worldstatic website generator
    link
    fedilink
    English
    arrow-up
    27
    arrow-down
    1
    ·
    edit-2
    1 month ago

    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.

    1. Build a standard desktop gaming pc to your budget, setting aside ~$150, give or take.

    2. 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 👍






  • Nowadays it’s less of an issue with docker and whatnot.

    Just set the image to refresh every night at midnight and if they tried to make manual changes it’ll just revert back to its original state at midnight.

    Customers don’t really get direct access to deployed code now, it’s buried under like 4 layers of abstraction on most CDNs now.

    Simply deploying to azure already smears multiple layers of access control and RBAC overtop that it’s hard enough for me, the dev, to answer the question if “what is actually deployed atm?”, let alone for the customer to get in their and meddle.











  • pixxelkick@lemmy.worldtoGaming@lemmy.zipGet gud
    link
    fedilink
    English
    arrow-up
    43
    arrow-down
    2
    ·
    edit-2
    1 year ago

    What I would be really interested in, is how does it play out in reversed scenarios.

    How do inexperienced women react to a singular man commenting in a competitive area that is female dominated, do you see the sane sorr of vitriol from lower performing women, vs welcoming behavior from better performing women?


  • My understanding is “immutable” is a bit of a misnomer and avoids the “point” of using these distros.

    “Layered Distros” is a better terminology, where you can imagine the OS as multiple layers, and you can swap 1 layer out for another without modifying the others and still have a functional operational machine.

    Now some of those layers have to be immutable ones at runtime for this concept to work, so thats where that part of the name comes from, but thats an implicit result from the actual point/use case of these distros, not the selling point.

    So you can swap versions/releases of your OS very cleanly at boot, without modifying userland, and it will continue to function just the same. This lets you do stuff at the admin level like broadly releases a version update merely by having users just reboot their machines, and next time they boot up their machine will now be running on the new OS layer, with their local “user” layer being unchanged.