Thanks! So much for my reading skills/attention span 😂

Which Debian version is it based on?

RE Go: Others have already mentioned the right way, thought I'd personally prefer ~/opt/go over what was suggested.

RE Perl: To instruct Perl to install to another directory, for example to ~/opt/perl5, put the following lines somewhere in your bash init files.

export PERL5LIB="$HOME/opt/perl5/lib/perl5${PERL5LIB:+:${PERL5LIB}}"
export PERL_LOCAL_LIB_ROOT="$HOME/opt/perl5${PERL_LOCAL_LIB_ROOT:+:${PERL_LOCAL_LIB_ROOT}}"
export PERL_MB_OPT="--install_base \"$HOME/opt/perl5\""
export PERL_MM_OPT="INSTALL_BASE=$HOME/opt/perl5"
export PATH="$HOME/opt/perl5/bin${PATH:+:${PATH}}"

Though you need to re-install the Perl packages you had previously installed.

beyond acceptable use

Since literally every aspect of lemmy-meter is configurable per instance, I’m not worried about that 😎 The admins can tell me what’s the frequency/number they’re comfortable w/ and I can reconfigure the solution.

You can hit the endpoint /api/v3/site for information about an instance including the admins list.

Exactly what I was looking for. Thanks very much 🙏

Thanks for the link. Had no idea about that.

That was my case until I discovered that GNU tar has got a pretty decent online manual - it’s way better written than the manpage. I rarely forget the options nowadays even though I dont’ use tar that frequently.

TBH I use whatever build tool is the better fit for the job, be it Gradle, SBT or Rebar.

But for some (presumably subjective) reason, I like GNU Make quite a lot. And whenever I get the chance I use it - esp since it’s somehow ubiquitous nowadays w/ all the Linux containers/VMs everywhere and Homebrew on Mac machines.

That single line of Lisp is probably (defmacro generate-compiler (...) ...) which GCC folks call every time they decide to implement a new compiler 😆

Thanks all for the input 🙏

I did a quick experiment w/ the APIs and I think I have identified the ones I’d need. Obviously, all is open source (GPLv3) available on github: lemmy-clerk

As the next step, I’m going to expose that data to Prometheus for scraping.

I still haven’t made up my mind as to what is a good interval. But I think I’ll take a per-endpoint approach, hitting more expensive ones less frequently.

So far I can only think of 4-5 endpoints/URLs that I should hit in every iteration as outlined in the post above.

web/mobile home feed
web/mobile create post/comment
web/mobile search

I think those will cover most of the usecases.

Thanks. Yes, lemmy-status.org was where I got the initial idea 💯

automatic list

For the website I’m thinking about, I’d rather keep it exclusively opt-in. I don’t wish to add any extra load since most of the instances are running off of enthusiasts’ pockets.

I agree w/ you RE posts looking horrible 👍

Though I’d say for one-liners like this, it’s mostly OK. It gets really messy when folks post more complex posts and mention and tag a bunch of times.

I’m afraid I can’t be of any help 😕

Any error logs? Try launching things from the terminal and note down any messages that are printed there.

That’s a good question 💯 In my case too, it took me some time (read years 😂) to figure out what I’m comfortable w/.

I can think of 3 major ways that you can navigate the filesystem while being able to drop to a shell when you need it:

• If you’re familiar w/ Emacs, you can either:
  • Use dired and tramp on your machine to access/navigate the target machine.
  • Install Emacs (emacs-nox) on the target machine, SSH and then run emacs-nox and voila! No need for tramp in this scenario.
• Use Midnight Commander (mc) which offers a TUI pretty much like Norton Commander (nc) from the days of yore.
• Get used to the semi-standard structure of the file system and just use plain Bash (cd, pushd & popd) to move around. That is
  • Understand what usually goes into common directories (like /usr/share or /opt) and try to follow the same pattern when rolling your own software installations.
  • Learn how to use your distro’s package manager to query packages and find out where things, like configurations and docs, are stored. Something as simple as rpm -q --list is what you usually need.

HTH

messing with the partition any more than I already have

Running fsck is a harmless and actually pretty useful operation, esp if you boot using a USB stick.

But yes, never hurts to have backups - easier said than done 😂

I’m not on a Debian-based system but a recent experience w/ packaging a software as a DEB was quite eye-opening 😅 The format and the build process felt too cluttered (to me) and it wasn’t easy for me to wrap my head around it.

I’m happy that folks are working on alternatives ✌️

Have you tried booting into recovery mode and perform a fsck on the drive - using the grub menu? Or you could boot via USB and try the procedure.

I wanted to say “I’m not sure. I’m not on Ubuntu” but then I remembered about distrobox 😄

It took only a few minutes to confirm that the links I shared earlier (https://lemmy.ml/comment/3090571) do NOT install the snap version.