DevOps as a profession and software development for fun. Admin of lemmy.nrd.li and akkoma.nrd.li.

Filibuster vigilantly.

  • 1 Post
  • 68 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle


  • Honestly it depends on what your experience level with running software is and what you want out of it. For me things have been rather smooth sailing as I already host a number of things for myself (so know all about domains, DNS, servers, reverse proxies, docker, etc.) and I am the only one actively using my instance right now so (local or admin-level) moderation isn’t really an issue either.








  • Asklemmy isn’t really a place to ask about lemmy, it’s for asking general questions to users of lemmy, jut like you wouldn’t ask for Reddit support in /r/askreddit.

    Regardless, this question gets asked and talked about in the !selfhosted@lemmy.world community fairly often, here is a (slightly edited) comment I made a while back.

    You will need a domain name, you can buy one from a registrar such as hover or namecheap (for the love of all that you consider holy do not use godaddy).

    You will need a way to expose the server that you set up via port forwarding or similar on your network.

    You will need to set up DNS records on the domain you buy to point to your home IP. You may want to figure out a different way to avoid just handing that information out, cloudflare can help with that. You will want to make sure the DNS records get automatically updated if your IP address changes, which is not uncommon for residential ISPs.

    You will need to figure out how to get an SSL certificate, Let’s Encrypt will issue them for free, cloudflare gives you one if you use them as a reverse proxy.

    Some of this would likely be easier to do on a cloud provider like digitalocean or linode and could be done reasonably cheaply.

    These are all common things for setting up any website, so lemmy docs won’t cover them. In addition to those (this answer was just addressing “how to get a URL”) you will need to install and configure lemmy, lemmy-ui, postgres, and pictrs somewhere (the join-lemmy docs cover this well).

    If you want your instance to send emails you will have to figure out how you want to do that (too many options to cover in this answer).

    When 0.18.1 gets released if you want captcha you’ll probably have to figure out an mCaptcha provider or set that up yourself.

    Not to mention thinking about backups, high availability, etc, etc.

    As far as hardware to host on you could get away with like ~$10/mo on most any cloud provider, run it on a Mini-PC in your closet, etc. My instance uses 1-2 GB of RAM, ~13GB of disk (and growing a few hundred MB per day), and ~30% of a CPU (an old i5).

    Best of luck.







  • I understand that urge, and in my ideal world it would a whole new option of “Suggested” feed rather than a replacement for “All”, like how that other site has a /all but defaults to a more curated selection of content that has broad appeal (and IIRC even some things are excluded from /all over there). For now I’d just take being able to filter the “All” view of the most objectionable stuff that I only want to allow users of my instance to explicitly opt into by seeking out those sorts of places.

    Also, unless your instance is purposely seeking out and subscribing to every community in every instance the moment they are created “All” is never going to actually be all posts from everywhere… I imagine larger instances may approach that, but I am certain there is a ton missing from smaller instances like my own.






  • There are a few completely fair points in there calling out what they are legally allowed to do (e.g. they are not directly violating GPL) and are doing (contributing changes back upstream, they claim “always”), that’s about the only “right” this reader found.

    Have some quotes that demonstrate the “wrong”:

    I feel that much of the anger from our recent decision around the downstream sources comes from either those who do not want to pay for the time, effort and resources going into RHEL or those who want to repackage it for their own profit. This demand for RHEL code is disingenuous.

    Ultimately, we do not find value in a RHEL rebuild and we are not under any obligation to make things easier for rebuilders; this is our call to make.

    Simply rebuilding code, without adding value or changing it in any way, represents a real threat to open source companies everywhere. This is a real threat to open source, and one that has the potential to revert open source back into a hobbyist- and hackers-only activity.