Starting my project from scratch again. I have used some of these before, but a few new players are coming to the game. We'll need a new solution for CMS. To avoid vendor lock in, I think I'll need something contained, like the o.g. application. Also, something that I ran into when I did this last time was issues accessing data from localhost...this is fixed using the loopback address instead.
What is coming over from my old tech stack:
React - front-end
Vite/Rollup - bundling/code structuring
Express - front-end web server
Newcomers:
Electron - deploying web app to desktop with native functionality using the chromium engine, built to work with any web framework
Capacitor - deploying web app to mobile platforms with native functionality, built to work with Electron
Typescript - all the syntactic sugar, typing, and professional development tools we'll need. I wanted to use this, but the errors prevented me from porting what I had already built for no toil
Still need:
[ ] #3 - The best thing could be a project-contained service, like postgres.
Nosql-type services are preferred, because like firestore they make set-based architecture most simple. I can't use firestore again unless no toil wants to set up their own account, but locally hosting seems to be their preference.
[ ] #4 - dockerizing the app will be great to make sure development on different platforms is standardized.
TODO:
[ ] #6
[ ] #7 - Implement the deployment solutions first, using a basic hello world application and the CMS to make sure the tech stack can function for all our platforms
[x] #8
[ ] #9
[ ] #29
Edit
More todo:
One more newcomer will be this issues tab in the repository.
TODO: is there a place on github where all my open issues assigned to myself can live? I'd personally love to organize my todo lists in one place with this being integrated into it. Can Jira or Asana integrate into this? As a developer, this issues tab is the best solution, but it would be nice to have one go-to list for everything.
Tech stack
Starting my project from scratch again. I have used some of these before, but a few new players are coming to the game. We'll need a new solution for CMS. To avoid vendor lock in, I think I'll need something contained, like the o.g. application. Also, something that I ran into when I did this last time was issues accessing data from localhost...this is fixed using the loopback address instead.
What is coming over from my old tech stack:
Newcomers:
Still need:
TODO:
Edit
More todo:
One more newcomer will be this issues tab in the repository.
The nice thing is that they can be updated automatically by referencing the issue no. in commit messages: https://github.blog/2013-01-22-closing-issues-via-commit-messages/