Example site deployment refresh
andypiper opened this issue · comments
Worth deciding on a cadence for refreshing the Glitch-hosted example / showcase site for Postmarks. Especially with the UI improvements from #122 and related PRs, it is noticeably out of date at the time of opening this issue.
Questions:
- should it always be postmarks.glitch.me
- I think that's fine (it aims to be a simple single-user app that can run on something like Glitch); but maybe another location would be another option
- should there be more than one showcase site we link out to
- should this be nightly / on push / driven by GH Actions
- would this make more sense to be based on actual versioned releases
- related #116
- may also be a good idea to show commit hash in a UI-visible version field.
- related #116
this is a good idea, and will dovetail nicely with me documenting some things around how to update your deployment when you've got it hosted somewhere with a git repo connected to it. (I did just go ahead and update the example deployment to grab the sweet new look, though, thanks!)
On a related topic, I deployed a Postmarks on Replit to confirm it is a straightforward thing to do. I imagine Glitch might be the main suggested deployment target, but I’ll write up the Replit instructions at some point, possibly on the wiki rather than adding n+1 deployment targets to the README.
for the record, I don't necessarily want Glitch to be the primary deploy target, I just want one that results in instructions that are as simple as possible, and I knew Glitch best to understand the ergonomics of how to do things like have a functioning demo site + make the SQLite db not copy over on remix.
I don't know Replit super well, but I did read that they're going to be winding down their always-on tier. Do they still have a wake-on-request tier like Glitch's free version?