-
Notifications
You must be signed in to change notification settings - Fork 0
Project Goals
Handled is a scratchpad project that has productionalized dreams.
If it's something I can automate how do I track it here? This should give me a single location to store docker-compose files for deployments, while also giving me space to write custom code
Handled is a monorepo. This was chosen for several reasons:
- I expect high reusability between applications and libraries and wanted to make that as easy as possible
- I wanted to know what my ideal monorepo looked like
- Automatic upgrades? Why hello dependabot, did you bring any friends?
- Long term stability over fast fixes (but let's be real, there will be lots of fast fixes but I have high hopes)
- Repo should continue to work 3-5 years from now (late 2020) given normal refactoring
- Blazing fast development iteration cycles
- Strong CI/CD
Handled should leverage tech that it's contributors are familiar with. It should be fun to add new features, while seriously useful.
- Typescript is important for refactoring. However when needed for prototyping we will skip typing.
- Vue. It's just nicer than Angular or React
- Node.
BUT
It shouldn't exclude tech. While Javascript will be the primary binding tech in the repo, we should also support various tech stacks for maximum flexibility. Examples include projects where Javascript really isn't the best choice, microcontrollers that require C++ come to mind
- Fun is a first class citizen.
- Custom when required, but always keeping an eye on sharing externally
Long term knowledge tracking and referencing. Anything useful to Handled might end up in the wiki.