• 0 Posts
  • 27 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle





  • AbouBenAdhem@lemmy.worldtoSelfhosted@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    2 months ago

    If you didn’t map a local config file into the container, it’s using the default version inside the container at /app/public/conf.yml (and any changes will get overwritten when you rebuild the container). If you want to make changes to the configuration for the widget, you’ll want to use the -v option with a local config file so the changes you make will persist.


  • Rather than starting from scratch, would it make more sense to make an ActivityPub plugin for the open-source MediaWiki software Wikipedia runs on? MediaWiki already has some “interwiki” functionality that such a plugin could expand on, and you’d have the advantage of being able to fork content from WP and other MW projects without having to re-format it. Plus you’d be able to leverage other MW plugins—Semantic MediaWiki in particular could add a lot of useful functionality to federated wikis, like articles that could query and aggregate information from other federated articles rather than just linking to the text.





  • Was it RAID 0 (striped), or RAID 1 (mirrored)?

    In general, a mirrored RAID is best for minimizing data loss and downtime due to drive failure, while separate volumes and periodic backups is best for recovering from accidental file deletion or malware. (I.e., if a RAID gets told to write bad data, it’ll overwrite the good data on both drives at once.)

    If you want the best of both worlds with just two drives, try zfs—you can mirror the drives to protect against drive failure, and make snapshots to protect against accidental data loss. (This still won’t protect against everything—for that you should have some kind of off-site backup as well.)



  • This way when lemmy.world is down its not a big deal because posting to any news community federates to all of the communities instead of barely having people see your post.

    I thought that’s more or less how it’s supposed to work now: if someone on instance A subscribes to a community on instance B, the community gets cached on instance A; and users there can post to it locally (and see each other’s posts) even if it temporarily can’t re-sync with instance B.

    Is that not how it works in practice?