Neos S3 Migration Best Practices

Using Neos & Flow
4

Perfect, then we are talking about the same thing :slight_smile:

In the scenario I described above, we did not even do a site:export. We just copied the Resources directly from the A-Environment to S3, using the resource:copy command. Then we directly dumped the DB, transferred the dump to B and imported the DB on B-Environment. When you configure S3 on B the exact same way, it will find all resources in S3, without an import.

That’s basically the same process, of how you could move a non-S3 from A to B. (Dump DB, import DB on target and copy Resources-Folder).

You could also do it like:

  1. Dump DB on A and import it on B
  2. Copy Resources-Folder from A to B
  3. ./flow flow:cache:flush & ./flow resource:publish on B. (Now Neos should run exactly as on A)
  4. Configure S3-Package on B as secondary resource-storage.
  5. Flush Cache and do the resource:copy command on B to copy files to that newly configured resource-storage (S3).
  6. Switch configuration to the new Storage → cache:flush & resource:publish.

It’s basically the same procedure. Also without need to use site:export.

I’m not sure, who told me back then, but somebody said that site:export could cause a lot of trouble with mid- or large-sized setups. And I also had a bad experience with that.

Would that maybe be an easy alternative for you? Maybe just give it a try without activating S3 first and see how easy it could be :slightly_smiling_face:

1 Like