3 ms·
Not exactly a starter kit, but something I think could be useful during early development: Noop Workshop [1]. Full disclosure I work @ noop. One of the primary
by noop_joe 3y ago
Not exactly a starter kit, but something I think could be useful during early development: Noop Workshop [1]. Full disclosure I work @ noop.
One of the primary benefits is you can quickly explore what Cloud components you need (locally) before purchasing them. We also built a bunch of templates in different languages that act as application boilerplate.
If it works the way you want in Workshop you can launch right to the cloud. If not it's easy to find alternative hosts for the different components. After all, Noop uses many AWS services under the hood.
The interface for local development is almost identical to the cloud interface, so it will give you a pretty clear idea of what the experience will be like in deployed environments.
1. https://noop.dev https://noop.dev
- ikoichi2112 3y agoI love what I see! Noop looks great for local development, and deployment to cloud services. I'll give it a try as soon as possible. These are the pain points I'm looking for: - avoid vendor lock-in (avoid using Vercel, also for bandwidth cost) - continuous deployment (push to git) - let's encrypt certificates auto-renewal - scaling? (might be not necessary TBH)