Link to security variables section in "Getting started"

[alyssadai]

Since our getting started instructions currently do not include changing the graph store user/admin credentials, if a deploying user wants to change the passwords after node initialization, they will have to remove the entire volume for the graph store, since the admin password cannot be changed automatically using our current script (they will need to provide the current admin password to modify it, whereas our startup script assumes that the admin password is not yet set). This is not very convenient, and means that setting up a secure deployment always incurs additional work from the user (vs. being the recommended default).

Instead, we should link to instructions to change the passwords right when first setting up a node. This is related conceptually to the optional step under "Getting started" for users who already have data, as providing the info up front will hopefully save more prepared users unnecessary extra steps during deployment.

Steps to implement

• In the getting started steps, link to section in node configuration docs on changing security variables including credentials
• On the "Getting started" page, add/update an info box with something like "If you already have generated Neurobagel graph-ready data (JSONLD files), follow the steps to configure your deployment for your data before launching the stack" that links to the section in the first bullet point (already addressed in [ENH] Add example config for deploying a node behind NGINX and clarify data uploading #240)

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
  apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
  label in the future. Use sparingly!

[surchs]

Making this a someday issue as we have much improved the getting started docs

[surchs]

Hey @alyssadai just a meta-comment: I'd say it's cleaner to close this issue because the original point of "add link for people who have .jsonld" has already been addressed in ff0919f - and to then open a new issue for the point about the credentials. Otherwise some of the context no longer makes sense