Lander is a preact app which serves up landing pages. Landing pages are configured in src/config/lander.json.
It serves a dirt simple page with some roughly templated values based on a campaign ID in the query string which serves to accept signup email addresses.
Lander, found in the ./lander directory, is a digitalocean functions package which accepts signups from landing pages and stores them in a digitalocean space, keyed against a downcased/ base64'd email address (to avoid double signups)
Lander exists in a directory of its own, with a frankly mental nesting strategy, because that's how the abysmal digitalocean CLI expects it. We must use that tooling because:
- There are no digitalocean docs explaining how to upload to the DO API directly for serverless
- We can't do manual deployments (which honestly would be fine- that's how hateful the official tooling is) because the fucking serverless thing
- Builds your function in digitalocean (you can't give it a binary)
- Isn't smart enough to create a dummy module and do a go get to pull in non-inbuilt packages
Originally, we had a top-level main.go in this repo holding the function which was manually deployed, with the frontend app living in a subdirectory (which is mainly due to some backend bias of mine)
The rationale behind that direction may be found in DIGITALOCEAN_RANT.md