Online, accountless, password-protected collaborative document editor/storage
Your .env file should be in the root of the repository, and should contain two values. First, REACT_APP_FIREBASE_CONFIG should contain the stringified JSON object of a firebase config. Secondly, REACT_APP_BASE_URL should contain the base URL of the web app. See the .env file in the repository for an example.
yarn startwill run the app in development mode. Open http://localhost:3000 to view it in the browser.yarn buildwill build the app
The app is currently hosted on Netlify. See the _redirects file for getting Netlify working with react-router. Besides that, the environment variable for the firebase config needs to be set in the control panel of Netlify.
The app was previously hosted on Firebase.
To use, run firebase init and select hosting, selecting build as the serve directory.
Then, run npm run build, then firebase deploy to deploy.
The app was previously hosted on Google App Engine.
Using the Google Cloud SDK, run - gcloud init, and create a configuration using the desired project - gcloud app deploy to deploy to web.
To update an already deployed app, run gcloud app deploy again
- Refactor code editor settings bar to a centralized separate component
- Add accounts, and keep track of each account's documents.
- Add password protection
- Get a single collaborative document working locally
- Using React for frontend
- Firepad for the actual document
- Backed by Google Firebase
- Figure out how to host multiple firepads at different URL endpoints
- Again, using react and random hashes to query a database and see if a document exists
- Password-protect URL endpoints
- Probably just something basic, like storing a salted+hashed password in the firebase database that we verify against before populating the text editor
- Add accounts support.