ltgcgo/mint

## Documentation
Read before deploying Mint to your desired platforms.

### Configuration
* [Environment variables](env.md)

### Deployment
- [x] [Deno](deploy/deno.md) (Deno)
- [x] [Node.js](deploy/node.md) (Node)
- [x] [Cloudflare Workers](deploy/cloudflare.md) (Service Worker)
- [x] [Deno Deploy](deploy/denoDeploy.md) (Deno)
- [x] [AWS Lambda](deploy/lambda.md) (Node)
- [ ] [Azure Functions](deploy/azure.md) (Node)
- [ ] [Netlify Edge](deploy/netlify.md) (Node)
- [ ] [Vercel Edge](deploy/vercel.md) (Node)

### FAQ
#### I want to run Mint with X on Y, is it possible?
|      | ix86 | amd64 | armv7 | arm64 | riscv |
| ---- | ---- | ----- | ----- | ----- | ----- |
| Deno | ✓    | ✓     | ✕     | ✕     | ✕     |
| Node | ✓    | ✓     | ✓     | ✓     | ✕     |

#### What's platform persistency?
Platform persistency means, that serverless instances are run continuously, until the platform decides to shut them down. This is critical for active health checking and proper WebSocket support.

Persistency status is available at the beginning of deployment guides.

#### Does all persistent platforms support WebSocket?
Not really, it depends on how the platforms implement serverless functions.

WebSocket support status is available at the beginning of deployment guides.

#### If WebSocket isn't supported by the platform, what should I do?
To provide support for duplex communications on platforms not supporting WebSocket, Meek-based solutions are advised. Meek is a solution that reconstructs a stateful duplex communication over stateless messages, and is often used to bypass platform restrictions.

We offer our own Meek implementation, [Ditzy](https://github.com/ltgcgo/ditzy/).