Hey! Last week I tried off and on to get Lemmy running on an Azure subscription, it’s been tricky.

I still haven’t gotten it working correctly. So far, I’ve tried to run the docker-compose on an ACI and Container app, but I’ve had the most success on a Web App for Containers of all things with the configs uploaded directly on the app service through FTP (yeah…).

I’m running the Postgres as a separate Flexible server instance (set it to v15, default is v13). And I’m running the pict-rs container as a separate ACI with a mounted storage account.

Right now the backend doesn’t want to run db migrations fully, but I’m not sure why, otherwise the rest seems to work as intended and can scale independently. Running up to a projected $52/month with everything on the lowest possible SKU

I will publish a bicep once I get the whole thing to run reproducibly.

Have you guys tried it out? What other approaches have you tried or would you try?

  • nibblebitOPMA
    4·
    2 years ago

    My wish for Santa:

    • A simple non-isomorphic front-end that that could run on a SWA.
    • The diesel.rs devs would implement a SQLServer adapter or move to MongoDB (to hook up to Cosmos)
    • Backend loses most of the websocket stuff and uses http (and moves to signalr)🅰 Then you could host the whole thing almost for free!
    • starman
      1·
      1 year ago

      Correct me if I’m wrong, but since cors issue was fixed in lemmy 0.18.1, frontend could run as static web app (I mean not the actual frontend, just theoretically)

  • sloth
    1·
    2 years ago

    Install docker on a VM then run compose probably. You don’t need to get complicated

    • nibblebitOPMA
      1·
      2 years ago

      I get that. But then I have a VM that I have to run and support and put effort into CICD. The nice thing about native stuff, is that they can scale independently, don’t need updates, integrate with the ecosystem, and for the standard tiers can run on the cheap :)