-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changing values in an existing deployment. DB, File System etc. #234
Comments
ChrisLopezUK
changed the title
Changing values in an existing deployment. DB, Files system etc.
Changing values in an existing deployment. DB, File System etc.
Feb 19, 2021
@SorraTheOrc and @UmakanthOS any chance you know the answer to this? It might also play into #238 . Let me know what you find out and I will update the docs so other people can reference them. |
Flagging with @naioja for a quick look. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi All.
I am looking at a number of ways to take a copy of my Production. This is mainly for DR and any other scenario where we might need to create a copy of our existing environment.
I am using Azure NetApp Files. So in my deployment I am choosing nfs-byo. I can take a snapshot of my existing NetApp volume and restore it to a new Volume.
To change the mount point for the controller is relatively easy. I understand I can just amend /etc/fstab. However, I am having some difficulty trying to work out how to do this for the VMSS.
I understand on creation of a new instance the VMSS creates /var/lib/cloud/instance/moodle_on_azure_configs.json with all the relevant values. However after the first deploy, where are all the values stored? How would we edit them if we needed to?
The text was updated successfully, but these errors were encountered: