• 0 Posts
  • 17 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.



  • Yeah this is just noticeable because most products weren’t even resealable, they just expected you to seal em yourself with a clip, twist em, put em in a container, etc.

    Now they are adding cheap resealable zips to the bag, which is nice in theory but the bag material has to be strong enough to support it.

    Actual ziplock baggies themselves are made of thick plastic that can take a bit of abuse.

    But cheap paper plastic hybrid materials a chip bag us made of can’t handle that sort of load, so it becomes the fail point.


  • 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 👍







  • 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:

    1. That client requirements can’t easily be 100% covered day one (But you still need to get as many as you can!)

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



  • From my experience the only big changes I’d say I made overtime are:

    1. Font size bumped up

    2. Switched to neovim from visual studio, which took like a year to relearn my entire workflow (100% worth it though)

    3. Switched from multiscreen setup to one single big screen (largely due to #2 above no longer needing a second screen, tmux+harpoon+telescope+fzf goes brrrr)

    4. Switched to a standing desk with a treadmill, because I became able to afford a larger living space where I can fit such a setup.

    If I were to do this meme though it’d mostly be #1, there just came a day when I had to pop open my settings and ++ the font size a couple times, that’s how I knew I was getting old.


  • or quickly closing or not reopening after a carefully written argument

    Thats where I think the misunderstanding was, if you look at the dates, many of the closings happened months after the issue was opened and no one posted anything on it, so it would clearly look to be a stale issue, so its reasonable to give a quick “Im closing this because of x” comment.

    Often in those cases the person is doing a bunch of cleanup and has to close dozens of stale issues, so writing a multi paragraph response on every single one is a lot of time to put into it.

    Then later the issue is re-opened again because it actually isnt stale, it just looks stale, and the cycle repeats as it continues to sit on the backburner.

    This is all very normal on any larger project, its pretty common to see issues get closed and re-opened if they are very low priority and sit on the backburner for literally years, and its common to see they have a bunch of short “Im closing this because x” responses as a result.

    But, if you look at the dates, you go "Oh, I see, these comments are months apart and not even really a “convo” but more just documentation.


  • Looks like snowe missed the fact that each of those close/reopens were months apart, so it’s clear the issue would ge re-opened, still not addressed after many many months, then closed to clean up the backlog, then re-opened because it actually still has value.

    Snowe it seems interpreted this as two people fighting and not just normal stuff that happens on giant repos with many devs.

    What he did wrong was comment about behaviors/edicit on a PR, which is not the appropriate place to have that convo.

    PR comments are for talking about the PR, not for having meta convos about comments on PRs.

    I don’t even participate in this repo, but I can say that snowe was off topic here.

    However the owner’s reaction of a whopping seven day ban and “learn your lesson” comment was also abrasive and unreasonable.

    Both sides fucked up here, get ya’lls shit together and apologize to each other yo.


  • Building and running my own server for self hosting multiple tools for my home.

    • Bitwarden Password manager, now sharing logins/passwords for stuff my fiance and I both use is easy, and every single website we use has its own unique randomly generated password so when one site gets breached, our logins aren’t compromised anywhere else

    • Plex, it’s like your own self hosted Netflix. My file copies of any movies/TV shows go on here and it parses em all, keeps it all grouped together, streams in 4k.

    • Shinobi, for my security cameras. Self hosted free CRTV application, works with any open spec cameras. Has movement detection and tonnes of other open source options for plug-ins.

    • Deluge, handy UI for downloading torrents onto my server. Conviently added presets to it that let me download to the very folders Plex scans… cough cough.

    • Kavita, self hosted server for books/pdfs. Some e-readers can even connect to it. A couple popular manga reading apps also work with it. Can also just use its own browser web interface as an e-reader, it has multiple options for styles (infinite scroll, page swiping, left/right click, and even supports right to left mode for manga!)

    • Nextcloud, pictures/document storage. Sort of like a selfhosted filesshare/file backup. Has a mobile app that can automatically backup every picture/video you take on your phone!

    • Gogs, open source super lightweight git repo. Has only the bare minimum of features, basic web hook, authorization, permissions, simple web ui to edit. It does the job I need it to and that’s good enough.

    • OpenVPN, self hosted VPN so I can securely access all the above stuff without exposing it to the internet.

    • Also I host my own websites on it, publicly exposed. Blog, a writing project, nothing terribly fancy.

    Eventually I plan to add some more stuff to it. Migrate my smart home dependencies over to Z wave and install Home Assistant, so I don’t have to rely on sending my info to google/amazon/etc to do basic smart home stuff.