I’m involved with an org that needs to set up a public wishlist for supplies for a project. The rough requirements are as follows:

  • Public webpage with a static URL
  • Can be easily edited by non-technical people
  • Editing requires authentication
  • Avoiding corporate services, especially avoiding tracking of both users and admins
  • As cheap as reasonably possible
  • As quick to set up as possible

Nice to have:

  • Hosted under a custom domain
  • Supports users “reserving” items so multiple people don’t all supply the same stuff

One option I considered would be running something like wishthis in a VPS under our own domain, but this is kinda expensive, complex, and I don’t trust wishthis’ auth. A different option could be just having a static page in something like Notion or Github pages, which would be free but relies on corporate services we don’t trust.

Is there a middle ground between the two previous options? Or a better solution that fits most of the requirements?

  • krakenfury@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    0
    ·
    6 months ago

    What is more expensive for your organization: time or money? In general, your options that cost less take more time to setup, and vice versa.

    It seems like cheap is more important, so I would roughly do:

    • SSG like Hugo or MkDocs
    • store the content in S3
    • serve with a CDN like Fastly or CloudFront
    • authentication via VCL or a Lambda using OAuth
    • andscape@feddit.itOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      6 months ago

      This is way too overkill for what we need. I’m sorry, I’ve been intentionally vague about the context for this but I guess it’s too unclear. We’re an activist group planning a protest. We might have to get this set up literally tomorrow and every penny comes out of (mostly my) pocket. We’re also all paranoid about opsec and anonymity, which is why the requirement about avoiding corporate services is there. Perhaps I should have posted this in a privacy focused comm instead, I apologize.