a beautiful robot, dancing alone · showgirls über alles: kylie, angèle · masto · last.fm · listenbrainz · https://www.lovekylie.com/keyoxide

  • 22 Posts
  • 29 Comments
Joined 1 year ago
cake
Cake day: June 5th, 2023

help-circle




  • Prerequisites

    • Internet-facing web server with reverse proxy and domain name (preferably SSL of course)
    • Server behind the reverse proxy with Rust environment

    Installation

    • Don’t bother downloading the source code to your server; installing it that way gives you a big debug executable
    • Instead just cargo install mollysocket
    • Move the mollysocket executable if desired
    • Run mollysocket once so that it will emit the default config

    Configuration

    • Fish the config file out of .config/mollysocket/default-config.toml and copy it somewhere.

    config.toml

    • In the new file, replace the allowed_endpoints line with allowed_endpoints = ['*']. The default 0.0.0.0 config appears to be a bug; this setting controls access to endpoints within the app, not IPs from outside. Leaving the original value causes mollysocket to reject everything.
    • Put a proper path in the db = './mollysocket.db' line rather than just having it land wherever you’re sitting.
    • Delete the mollysocket.db that was created on first run (even if it’s already where you’re intending to put it). This is just to make sure the web server creates it and has the correct permissions.

    Run script

    • The environment variable ROCKET_PORT must be set or the server will sit and do nothing. It’s best to create all of the environment variables mentioned in the README, whether that is in a user profile script or in a shell script that wraps startup. You can change any of these values, but they must exist.
    • export ROCKET_PORT=8020
      export RUST_LOG=info
      export MOLLY_CONF=/path/to/your/config.toml
      

    Proxy server

    • You’ll need to proxy everything from / to your mollysocket server and ROCKET_PORT.
    • Exclude anything that you may need served from your web server, such as .well-known.

    Things to know



















  • looks great! the catch for me is that my current host doesn’t have docker support. your dependencies don’t look crazy so in theory i could burst it and install directly to the host environment, but at that point i’m giving myself grocy-level headaches.

    reading about docker-capable hosts, i was surprised to see them starting at 1GB RAM - i couldn’t run pac-man in that. what would be a reasonable expectation for kitchenowl?


  • pootriarch@poptalk.scrubbles.techOPtoSelfhosted@lemmy.worldgrocy *bangs head*
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    4
    ·
    1 year ago

    i haven’t tried the docker route - it seems fairly new. it also doesn’t seem like it would fix the issues i ran into. containerization is great for insulating the app from external dependency hell and environmental variation. but the problems i’ve had involve its own code and logic, and corruption of a sqlite database within its own filesystem; wrapping issues like that in a docker container only makes them harder to solve














  • is that somewhat new?

    it’s somewhat… janky.

    you can ‘migrate’ an account, to use the masto term that will make it easier to search. this:

    • makes it so your old account can’t post
    • puts a ‘pointer’ on that account so that you get its mentions (i think)
    • puts a note on that profile that you’re really you-at-new-place now
    • causes all accounts following you to auto-follow the new place

    it does not:

    • remove you-at-old-place from other people’s follower·ing lists; old you eventually shows as dormant, but you’re still in their lists until and unless they clean house
    • take any posts with you; you-at-new-place starts with an empty profile
    • copy over any profile information
    • copy over any post filters

    i’m not clear on how long your old posts linger at old-place, and you might have to export/import your following list.

    it’s possible, i’ve seen lots of people do it, but it gets more unappealing the longer you’ve been actively using the account. unless you’re like me and have posts set to self-destruct within days. and you can imagine the difficulty of actually moving the posts - if i were an avid shitposter and i moved house to noshit·social, then all my garbage would be dumped in the yard in violation of policy.