• dan1101@lemmy.world
    26·
    1 year ago

    I actually ran a moderately active (like 20,000 hits a day) small business site from a laptop for a couple years. Of course one of the first thing I did was put a “SERVER DO NOT SHUT DOWN” sticker on it, and set the power settings so closing the lid did not shut down or sleep the computer. It was a Dell 7000 series with 16GB IIRC, it did great.

    • Eugene@lemmy.ca
      11·
      1 year ago

      Not advertising here, but with this low traffic you could be in a permanent free tier with AWS with all the availability guarantees. It doesn’t work with EC2, but for serverless solutions (ApiGateway, Lambda, DynamoDB) they have something like “we start charging after 1M calls per month” (don’t quote me on this exact number). I have a couple of pet projects working this way

    • iso@lemmy.blahaj.zone
      2·
      1 year ago

      They’ve upgraded due the IPO, they now also have a fake serverroom with a bunch of blinkenlight generators

      Those Blinkenlight generators are obviously trained by AI to make it look more realistic

    • Demonen
      5·
      1 year ago

      I used to work for a notebook manufacturer, and it was a non-trivial part of the cooling strategy that the lid is open under load.

      I hope they’ve changed, but megacorps usually don’t.

      • NathanUp
        2·
        1 year ago

        My ASUS work laptop absolutely screams if the lid is closed while I’m working on my other monitor. It drives me nuts.

  • User Deleted@lemmy.dbzer0.com
    14·
    1 year ago

    What specs do I need to run a lemmy instance for, say a small group of 1000 people? Cpu, Ram, Amount of Electricity needed, Minimum Internet Speed, Storage? Assuming that I would be federating with the top lemmy instances.

  • whoharold@lemmy.world
    14·
    1 year ago

    This looks like my old laptop - Lenovo Y510P. Even down to the slight abrasion below the mousepad from the user wearing a watch with a metal band.

    It had SLI GPUs in a laptop through the ultra bay. It was a beast for about 20 minutes until the heat built up.

    • Boforn
      1·
      1 year ago

      I came here to comment something similar. This machine is a beast.

    • StickBugged@kbin.social
      9·
      1 year ago

      I’m actually thinking about doing this exact thing with my own rpi b rev2 from 2012. I’m not sure it’ll even run a kbin/Lemmy instance though

  • SeeMinusMinus@lemmy.world
    11·
    1 year ago

    I have a minecraft server running on a laptop like this. Sadly I don’t have any friends that want to play minecraft right now ):

  • Gresham's Law
    104·
    1 year ago

    Please use an ethernet cable, you gonna need to keep that connection spotless and WiFi are vulnerable no matter which protocols, better turn it off.

    If I may also add a secure systems (Harden its configuration), a custom firmware on your router(Rec. Tomato series most updated)/hardware firewall(Rec. pfSense) with a VPS if the network is used for other means, they will help you in the long-term.

    It should go without saying if you can’t secure a server, don’t host one. You’re responsible for anything that happens to it & us.

    Gpt-4 Prompt using Forefront.ai (Worth taking a note):

    Q: Recommendations on the levels of security that need to be taken into account for self-hosting a decentralised community
    A: Self-hosting a decentralized community involves a number of security considerations. Here are some recommendations:

    1. Secure Server Configuration: Ensure that your server is configured securely. This includes using strong, unique passwords, disabling root login, and setting up a firewall. Also, consider using a security-focused operating system like SELinux or HardenedBSD.

    2. Data Encryption: All data, both at rest and in transit, should be encrypted. Use protocols like HTTPS for web traffic and SFTP for file transfers. For data at rest, consider using disk encryption technologies like BitLocker or LUKS.

    3. Regular Updates and Patches: Keep your server and all software up-to-date. This includes the operating system, web server software, database software, and any other software you’re using. Regularly apply patches to fix any known vulnerabilities.

    4. Backup and Recovery: Regularly backup your data and test recovery procedures. This will help you recover quickly in case of a data loss event.

    5. Access Control: Implement strict access control measures. This includes limiting who has access to your server and what they can do. Use technologies like two-factor authentication (2FA) to add an extra layer of security.

    6. Intrusion Detection and Prevention Systems (IDS/IPS): Use IDS/IPS to monitor your network for suspicious activity and automatically block or alert you of potential threats.

    7. Secure Application Development: If you’re developing your own applications, follow secure coding practices. This includes input validation, output encoding, and proper error handling. Consider using a security framework to help with this.

    8. Privacy Protection: As a decentralized community, your users will likely value their privacy. Use technologies like Tor or VPNs to help protect user privacy. Also, have a clear privacy policy and follow it.

    9. Auditing and Logging: Keep detailed logs of all activity on your server. This can help you identify and investigate any security incidents. Also, regularly audit your security measures to ensure they’re working as expected.

    10. Education and Awareness: Educate yourself and your community about security best practices. This includes things like recognizing phishing attempts, using strong passwords, and being cautious with downloads and attachments.

    Remember, security is not a one-time thing but a continuous process. Always stay informed about the latest threats and security best practices.