pageuppeople-opensource/microservice-bootstrap

Get started with Microservices using dotnet core

microservice-bootstrap's Issues

Upgrade dotnet framework & tools

Use netcoreapp1.1 supporting vs2017

Bring back deployment

There were a few questions about deployment enablement

1. Would this bootstrap repo continuously deploy?
   or
2. Would it enable people to set up continuous deployment?

Of course, option 1 encompasses the option 2.

The question is, whether option 2 can be achieved without going through 1, what are the merits & demerits.

I am kind of looking at serverless YAML file for example where a hell a lot of things are comments, though it enables us pretty quickly.

On the other end, why not just deploy it if that is alright.

No right or wrong here, I guess.

Include the vertical test stories and the fail whale

Should the image go into DC2 only and out from there, or into each region?

localisation and culture support

Web roles should be using the culture from incoming request in absence of which it should default

Should worker use the default culture or be configurable?

setting thread culture?
Using OS culture on ECS cluster? how do they work?

docker compose overrides are includes in any command by default

This may cause the override to accidently go to production

Convert web role to use dotnet core

Support for hypermedia built in

Use multi stage docker build

https://docs.docker.com/engine/userguide/eng-image/multistage-build/#use-multi-stage-builds

Separate kinesis from this bootstrap repo

While the capability to consume and produce kinesis streams is a wonderful bootstrap set up, It is a good idea to separate the kinesis consumer itself into a separate NuGet package and consume it from here.

I am referring to the KinesisNet folder in worker service

@jimmyp

The deployment scripts should clean up the task definitions, 10 maximum

Travis build uses after_success to deploy, which gives a false success

In the commit 258f13f , I had to change from deploy to after_success before deploy did not support an array.

This is reported as a bug in travis ci travis-ci/travis-ci/issues/4673

Need to fix this back to deploy step or any step between script and completion without compromising on the output.

Can multiple regions be deployed asynchronously?

Fix the principles of microservice image

Readme used to have an image of principles of microservice image and a link to video by sam newman. It is broken at present

Ensure the deployment scripts have the appropriate execute permissions for Travis

The deployment scripts couldn’t find ‘function’ because they are running in a minimal bash shell… they needed to be executed with ‘bash’ to work. Clear documentation on how to deploy

Update readme post tools upgrade

move to ecs deploy

ecs deploy

Encrypt repository locations with Travis and pass through to deployment scripts

Repository locations are stored unencrypted in the source code, these contain our account number and should not be public.

Is dockercompose port mapping needed?

Dockercompose was mapping port 4000 -> 4001 and baking that into the docker image, we have to make it 4000->4000 to get it to work. Notes around why this port mapping exists and how it works (maybe a container/stack diagram of ports)

microsoft dotnet onbuild is cool, but not optimal with restore command

onbuild forces dotnet restore, irrespective of project.json file changed or not. This can be avoided.

microsoft onbuild dockerfile