Adds Initial Service to Get Posts

[HyperTHD]

Issue This PR Addresses

This PR address #1735

Type of Change

• Bugfix: Change which fixes an issue
• New Feature: Change which adds functionality
• Documentation Update: Change which improves documentation
• UI: Change which improves UI

Description

This PR is a work-in-progress, meant to work on adding a Post Microservice. This microservice parses posts from user's feeds and returns them. There's a path that returns the 10 latest posts, and you can also retrieve information about a specific post using it's ID.

This PR includes files that are being used by other microservices. I recommend getting those PRs in first before this one so that I can update the docker-compose file to use those services. This would allow me to remove the files those services used and only keep what I need for my microservice. In particular, this would be the User Microservice, The Post parsing microservice (#1828), and possibly the Feed Parsing microservice (#1833).

UPDATE: Screenshot of successful loading of this route along with network tab open as proof

Checklist

• Quality: This PR builds and passes our npm test and works locally
• Tests: This PR includes thorough tests or an explanation of why it does not
• Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not (if applicable)
• Documentation: This PR includes updated/added documentation to user exposed functionality or configuration variables are added/changed or an explanation of why it does not(if applicable)

[HyperTHD]

This PR is not tested btw. I'm still working on the Docker related stuff. I will post screenshots of the output when I get it working

[humphd]

I did a first read through and left some feedback.

There's a lot of code in here that can be removed and done in #1828 by @c3ho (e.g., all the feed handling stuff).

Eventually I want to have the feed service use this service to get/set/update/delete posts.

[HyperTHD]

UPDATE:

• I added the docker code to create the posts image. I may have done it wrong, but I needed to include redis and elasticsearch inside the docker-compose.yml file since it needs both to function.
• I added the redis and elasticsearch information to all 3 env example files for reason specified above.
• I modified the redis and elasticsearch host names so that they use the container names. Since we're running them off the container instead of localhost, it makes the most sense to do this.
• Lastly, I refactored the code to remove the bin folder completely.

Running the posts service atm loads the right page, however, NO POSTS ARE LOCATED AND YOU GET AN EMPTY ARRAY AS A RESULT. I feel this is because of the changed host names, since the redis data is locally served instead of via the cloud. I'm not too sure about this one. Otherwise, I feel good about this service and can move to add in the extra routes.

As for adding test cases for this microservice, I plan on filing another issue to handle that. I want this PR strictly for porting this microservice over

[humphd]

I wonder where we should put volumes related to the microservices. The root is one option for sure, but maybe we should have a dedicated directory where we can find these things. cc @manekenpix, @raygervais.

[manekenpix]

@humphd this is how we currently do it on prod and dev:

Directory Structure

[manekenpix]

I need some clarification for this PR. I thought this microservice was going to answer requests (serving posts), but I see a lot of code here related to processing feeds and posts. Shouldn't all that be part of a different microservice?

@HyperTHD @humphd

[humphd]

@manekenpix I left a similar review comment, a lot of this code can get deleted.

[HyperTHD]

@manekenpix @humphd The main problem with removing that code is that there's no way for me to really know if the service works or not. The files related to my service also require the other files needed for feeds as well. Since we don't have those other services up, I can't realistically remove those extra files without breaking CI

[raygervais]

Why not test using mock services to pass in hypothetical data @HyperTHD ?

Requested changes were completed, awaiting final review