joshuabelden / pandemic-memorial Goto Github PK

Register, Login, and Logout all need to be wired up.

The backend needs a way to send emails.

The current service and front-end app are using a let's encrypt cert, but installation was rather wonky and I barely got it working. Also, I had to split the service out into a separate droplet because I couldn't get express and apache to work together as far as ports and https on both website and service.

I'd really like to get them back on to a single droplet. I think that we should get both front-end and back-end working with docker and have a streamlined process for updating the cert.

Also, we should ditch apache and go with nginx.

The site needs an ssl cert and to be running on https.

www.pandemicmemorial.com is not responding.

We need to create an actual secret for the production app and handled in a way that it is not in source.

The backend express service and MongoDB need to be containerized to make deployments easier for release. Ideally, docker-compose will be used to manage both images.

Users need a way to register with the site. There are currently auth, user, and profile endpoints that can be called, but nothing on the front-end to make the calls.

In an effort to get a site up immediately, the front-end app is displaying static content. We need articles displayed in the front-end to be loaded from data in the back-end.

There is currently no front-end service to talk to the backend, so that will be necessary.

Also, we need to think through a way to manage articles in the backend, perhaps that's a different issue.

As a developer, I need to understand how to get up and running locally so I can test my changes.

Currently, articles on the dashboard are static and entered manually. These need to come from the database. Images should be loaded remotely.

After a user registers, they should be able to update their profile.

Users should be able to post articles for their current locale. There is an article endpoint to accept article create requests, we just need the UI to send the requests. This is a rather large issue because there's the maintenance of those posts to deal with as well.

Additionally, we're going to want to add additional tracking schema to the backend API to track who posted what.

Users should be able to search through articles on a set of filter criteria, which is currently not defined. Also, we should allow users to see articles posted in a radius of their current location.

Front-end can't talk to back-end in production because of CORS policies in the browser.

The dashboard newsletter signup section needs to be wired up to a database. We will need unsubscribe capabilities.

The production database will be a mongodb database running in a docker image. Nightly backups need to be taken.

Individual articles need to be queried from the backend.

After a user registers, we need to send them a confirmation email, so we can mark their profile as not spam.