The domain is a brand new domain we've been switching to and we've hit a fun snafu with the DNS configuration recently - looks like some email got mixed up in that. It should be working now, or you can try the same email address at joinzest.com as well.
Hi, the project is not open source yet. I'd like to decouple the application itself from the backend code that handles the Stripe integration, emails and other application irrelevant functionality first - then open source it and get more eyes on the code. Hypothetically, if the whole back-end was open source ATM - you could run it locally or somewhere like on Vercel - with no problems, you'd just need to set the ENV variables for things like Stripe and other services to an empty value.
I'd say that the most important part of the infrastructure is the signaling server (websocket server), and the STUN/TURN server used in WebRTC connection forming.
One interesting fact about the currently running application; the application itself is client-side rendered. If you would download the application bundle that you get when you open the application in your browser, you could use it if you would mock networking requests - this would basically simulate the way it works now when the PWA is offline. With the application being client-side rendered - every user gets the same code.
Hi, my name is Avery. I graduated over a year ago with a BS in computer science. I've worked some short jobs and contracts doing web development, system administration (Nginx, knot, sqlite, MySQL, CGI), C, Python, Go and Bash programming/scripting for automation, testing and working with Linux kernel APIs.
The response from the remote server was: 554 5.7.1 : Client host rejected: Address locked or deactivated; see http://mail.messagingengine.com/docs/locked.html