this post was submitted on 10 Nov 2023
1685 points (94.1% liked)

linuxmemes

21222 readers
134 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] zeppo@lemmy.world 19 points 1 year ago (3 children)

    I wouldn’t expect running a publicly accessible server on the internet to be easy or a great idea for someone not familiar with the OS they’re using. Great way to learn, though.

    [–] Bakkoda@sh.itjust.works 9 points 1 year ago (1 children)

    Yeah I've got a proxmox cluster and I've been using Linux for decades but I wouldn't dare host something that a LOT of users are going to access. I don't know nearly enough about netsec and I can guarantee my vlan practices probably aren't perfect, etc.

    [–] Nobsi@feddit.de 4 points 1 year ago

    I have a solution for you. Just don't have your Internet facing things on the same /24 as your home stuff. Why vlan if you can just separate them by network and switch.

    Or: just do it anyways. I learned most shit after everything broke. Not before.

    [–] xantoxis@lemmy.world 2 points 1 year ago (1 children)

    And how do you learn, then, from this project, if people are shitty about your questions?

    I'm a sw engineer. I've been doing every kind of application management, development, and systems design for 25 years, nearly all of that in Linux, and I still need things answered about running apps in proxmox. I'm not coming to a Lemmy community for those answers, I'll tell you that.

    [–] zeppo@lemmy.world 0 points 1 year ago

    I haven't tried to get community tech support on Lemmy, so I wouldn't know what it's like firsthand. If people are really that difficult, sure, that sucks. But it sounds like the person asking needs to work on more fundamental linux skills than something specific to running a Lemmy instance, and the internet is full of information about that.

    [–] ZMonster@lemmy.world 1 points 1 year ago (1 children)

    I get that, but here we are. It's something I want to do. I've been at it for 6 months and I've managed to get the site working twice, but am still struggling with SMTP. Digital ocean blocks smtp and send grid breaks the site.

    ¯\_(ツ)_/¯

    [–] zeppo@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

    SMTP in general is a pain to configure. I ran my own mail servers for a while and finally gave up and used a 3rd party service. Too many problems with antispam restrictions, and things like I’d finally get it configured, upgrade postfix or whatever and then it would all be screwed again.