Closed htmlandbacon closed 3 months ago
We should look at how we are currently building (docker), hosting (aws) and deploying (gitlab) and work out what we want to do moving forward.
If the assumption is we are moving to a static site, then how we are the running the site might not be the best way (s3 bucket).
We should also look at what we can do to make our deployment more robust.
We should investigate the options for each stage and decide what we want to split out as tasks/close off.
Part 1:
Part 2:
Part 3:
Agreed next steps, and tickets to work towards it.
@jonhurrell, @simoneduca, @htmlandbacon
Let's use the disco board to highlight questions or knowledge gaps from the documentation to start to form a plan.
We may need to start thinking about registering alternative domains like:
What
We should look at how we are currently building (docker), hosting (aws) and deploying (gitlab) and work out what we want to do moving forward.
Why
If the assumption is we are moving to a static site, then how we are the running the site might not be the best way (s3 bucket).
We should also look at what we can do to make our deployment more robust.
We should investigate the options for each stage and decide what we want to split out as tasks/close off.
Done when
Part 1:
Part 2:
Part 3:
Outcomes
Agreed next steps, and tickets to work towards it.
Who needs to know about this
@jonhurrell, @simoneduca, @htmlandbacon
Related Stories