Releases: fortrabbit/craft-copy
v1.0.8
v1.0.7
v1.0.6
v1.0.5
v1.0.4
v1.0.3
v1.0.2
Happy New Year bug fix release:
see https://github.com/fortrabbit/craft-copy/blob/master/CHANGELOG.md
v1.0.1
v1.0.0
🎉 We are finally released Craft Copy 1.0.0, after it was first introduced two years ago. This release marks the first fully stable version for us. Thanks to our clients who gave us the required feedback to make this production-ready.
Notable changes to RC12
With this release, we are closing all issues and enhancements with Milestone 1.0. It actually contains some bigger changes to RC12 originally not anticipated:
New volume handling
In previous versions of Craft Copy (up until RC12) it was assumed that there will be a folder called web/assets where all your volumes will be stored. craft copy/assets/up (or down) would rsync that whole folder.
Now there is a new command called craft copy/volumes/up which you can use to sync specific or all volumes up. So Craft Copy will actually look for certain volumes you have setup with Craft CMS and sync these folders then. That's more reliable and open for different kind of setups.
In addition, there is also a new command called craft copy/folder/up where you can specify the folder you want to copy. This is still useful for static assets that are not in a volume.
The old assets/up is not working anymore. Either use the new volume command or continue with the folder command.
Smarter setup
Craft Copy now better catches certain states while setting it up. There are better more meaningful error messages. The configuration files for certain stages are stored in config/craft-copy.
Ready for Composer 2.0
The plugin is also compatible with Composer 1 and 2. This means composer install will be much faster once we switch to Composer 2 on our deploy service in the near future.
Next steps
- Fully integrate Craft Copy with the official fortrabbit help guides.
- Milestone 1.1
v1.0.0-RC12
- Dependency bump