4 ms·
Take payments in browser extensions: https://extensionpay.com https://extensionpay.com - $5/month Digital Ocean server - HTTP server: pm2 / Node / Express -
by Glench 5y ago
Take payments in browser extensions: https://extensionpay.com https://extensionpay.com
- $5/month Digital Ocean server
- HTTP server: pm2 / Node / Express
- Database: SQLite (because it's fast and needs fewer resources and less configuration than others)
- Front/backend - custom full-stack Svelte framework.
- Analytics: GA
- Email: Mailgun
- Uptime monitoring: Nine9s (https://nine9s.cloud/ https://nine9s.cloud/ from another solo dev I believe)
The Svelte framework I made is really cool. It makes it really easy to have server-rendered pages (for search engines and fast initial page load), pre-compiled static CSS, code-splitting per page, and automatically generated JSON APIs per page that re-render the Svelte component, as well as lets me use Svelte on the front-end which makes development much easier for me. Example code here: https://github.com/Glench/full-stack-svelte-prototype/ https://github.com/Glench/full-stack-svelte-prototype/
The tech stack has basically no effect on success as far as I can tell except that it's fast for me to develop.
- pyros2097-dev 5y agoThis is pretty good. I like the concept where api and ui is in the same file. Different from sapper and nextjs but pretty interesting.
- Glench 5y agoThanks! Yeah, I wanted a way to simplify/unify the front and back-ends while retaining flexibility to implement anything I need to. And of course it needs to be fast and have a small bundle size (thanks Svelte!). It's pretty close to SvelteKit with a few more assumptions baked in. Some people balk at having both back and front-end code in the same file but I like it since most of the time the code for both needs to be pretty tightly-woven in my experience. Also you can always put the back-end code in a separate file and import it for cleanliness :)