Skip to content
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

Add documentation on what configuration is stored in Fastly and what is stored within Magento #458

Open
braders opened this issue Jun 15, 2021 · 0 comments

Comments

@braders
Copy link

braders commented Jun 15, 2021

I am currently working on a new Magento site, and due to our requirements we will be moving the current staging database to the production server before going live. Currently staging and production environments are pointing at independent Fastly instances.

I understand that any changes made to the Fastly configuration eventually become Fastly VCL. However, it looks like some of this data is also stored as configuration within the Magento database: https://github.com/fastly/fastly-magento2/blob/master/etc/adminhtml/system.xml

This makes me unsure what will happen if we copy from staging -> production (or vice-versa) and re-upload the VCL. It's unclear if:

  • All the configuration (including things like custom VCL snippets) is stored within Magento, and a fresh VCL will be generated based on the Fastly config values
  • All the configuration is held within Fastly, and pulled out of Fastly in order to be shown on the Magento configuration panel
  • Some mixture of the above.

I know that the Fastly API credentials will need re-configuring. It's all the other configuration that I'm unsure about.

I think it would be great if the above were documented within the /Documentation folder. I can't believe I'm the first person to have wondered this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant