akongstad / devops-group-p Goto Github PK

Remove 'Tag' from tag name

Remove 'Release' from release name

• Remember to do TDD
• Add atleast 1 test for each method

Refactor the Timeline.html to .js format (React)

docker-compose should be placed in project root directory

What do you guys want to do?
Travis like the exercises?
I think github actions will be a lot easier

Server did not rebuild containers on-release

If SimulationAPI works using Postman well call this a header problem with the module

This would really speed up development!

Any takers?

see this

• Maybe other relevant information if needed

this line

docker-compose -f compose.prod.yaml down

takes down all containers.

Lets find a way to rebuild only the necessary containers

Frontend is initialized from DOTnet template which is a fork of create-react-app. Should work out of box and fixing it is out of scope.

Nice tutorial here

• eventually separate into its own branch

I dont want to remove them yet as it would create annoying merge conflicts, when done before your branches are merged to main

• Stop using routes for all parameters -> Take a DTO object instead of a username password and email fx
• Optional: Split into 2 separate controllers (Message and user)

When testing the API running inside a container using the following method:

response = requests.get(http://localhost:5229/minitwitsimulation/msgs)

I receive this error:

ProtocolError: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))

API however works with dotnet run but with various warnings.

I have a feeling this might this might have something to do with an HTTPS redirection middleware in the backend which caused a similar problem earlier.

• use DTO's
• repositories

something like this in github workflow

- name:  'Automated Version Bump'
  uses:  'phips28/gh-action-bump-version@master'
  env:
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
  with:
    tag-prefix:  'v'

Do it in frontend

Everything mentioning the following does not belong in the backend and could cause problems in the future:

• SPA (Single Page Application)
• node
• npm
• react (excluding filenames and foldernames written by us and corresponding path-references in source code)

We need to get the data out of the container, but we can't restart it(?)

• Seed more data in test files

Reference should be MinitwitController GetPublicTimeline

migrate from latest tag to more descriptive tags

• refactor
• style
• after refactor backend to EF - connect end-points

• AzureSQlEdge
• Postgres