Docs: How to run SDA stack

[nanjiangshu]

Related issue(s) and PR(s)
This PR closes #1153

Changes made

• Fixed some bugs in the Makefile
• Moved the instructions to run the SDA stack from GETTINGSTARTED.md to README.md and updated the instructions.

[jbygdell]

Commit 282896d can be removed in it's entirety since the --remove-orphans in the compose down command will do just that.

[nanjiangshu]

Commit 282896d can be removed in it's entirety since the --remove-orphans in the compose down command will do just that.

The problem is on Linux Ubuntu, the exited container for the integration test is not removed by --remove-orphans and that prohibit the removal of volumes.

[jbygdell]

Commit 282896d can be removed in it's entirety since the --remove-orphans in the compose down command will do just that.

The problem is on Linux Ubuntu, the exited container for the integration test is not removed by --remove-orphans and that prohibit the removal of volumes.

How come then that I haven't seen this issue on Ubuntu for the past several years.

[nanjiangshu]

Commit 282896d can be removed in it's entirety since the --remove-orphans in the compose down command will do just that.

The problem is on Linux Ubuntu, the exited container for the integration test is not removed by --remove-orphans and that prohibit the removal of volumes.

How come then that I haven't seen this issue on Ubuntu for the past several years.

No idea. I have problems on two of the VMs with Ubuntu 22.04, but another VM with Ubuntu 18.04 actually works. I will remove the commit but keep it only locally.

[MalinAhlberg]

Good work to document all this @nanjiangshu 👏 !
I have added some comments/suggestions. I also wonder if it would make more sense to keep most of this in the GETTINGSTARTED and link it from the README? Since it's so detailed (which is very good but maybe a bit too much for the readme). And in that case also update the help text of the Makefile.

[nanjiangshu]

Good work to document all this @nanjiangshu 👏 ! I have added some comments/suggestions. I also wonder if it would make more sense to keep most of this in the GETTINGSTARTED and link it from the README? Since it's so detailed (which is very good but maybe a bit too much for the readme). And in that case also update the help text of the Makefile.

That's a good point. However, as I discussed with @jbygdell and @viklund in one of the standups, we believe that a shorter README might lead people to overlook these instructions. Currently, the text isn't too long, but I agree that if it grows in the future, we should consider making it more structured and moving the detailed instructions elsewhere. We can probably create a refactoring issue for the development instructions and move some of the instructions to https://github.com/neicnordic/sensitive-data-archive/blob/feature/manual-go-run/DEVELOPMENT.md

The base branch was changed.

[jbygdell]

Just one tiny thing.

[nanjiangshu]

Hi @jbygdell and @MalinAhlberg , committed some tiny formatting changes to the docs and the PR needs your re-approval. Thank you.