echo-bravo-yahoo / breadbox Goto Github PK

• Add user interface to create new files

• Publish container to dockerhub
• Move to docker swarm for deployment

• Move to monorepo model
• Styling and layout

• Error-handling, lol
• Fix ag/rg not working in vim
• Replace pbkdf2-password with node:crypto

• Migrate from dbName 'users' to 'breadbox'
• Secure mongodb instance with auth
• Fix production deploys
• Fix breadboxPath messiness in docker-compose.yaml
• Fix hostPort messiness
• Upgrade session store for express-session
• Fix local development
• Wrap fetch, needs to handle server-side redirects becoming client-side routing
• Set up docker for local development
• Containerize application for single host use
• Create repository
• Add markdown view/edit
• Add a database
• Add auth for users
• Add support for multiple users (split files/fs)
• Symlink my existing recipes in for my user
• Automatically log users in after they register
• Server hot reload
• Move server dependencies from top level package.json to server/package.json

For local development, docker compose --file ./compose-dev.yaml --env-file "./secrets.env" up. This will use the containerized database, webserver, and vite webapp server. It watches and hot reloads both the webserver and the webapp. The recipe filesystem is written to ./fs/. The web application and API are both available at localhost:3000; vite serves the web app, and vite proxy forwards api requests to breadbox-server.

For local testing of a production build, first build a fresh docker image with docker build --tag breadbox --file Dockerfile .. Then, run docker compose --file ./compose-prod.yaml --env-file "./secrets.env" up. This will use the containerized database and webserver, and serve the web application from the webserver, available at localhost:3000. Since it uses built artifacts, neither the server nor web app hot reload.

Great question, more info coming...