v1.4.0
Search…
⌃K
Links
⏫

Upgrade guide

See discussion in Github issue.
Version updates can be a bit of a manual process. A boilerplate is meant to be a starting point for you to build from - rather than a framework like Phoenix. However, it is possible.

Options

Copy your files into a fresh project

If you haven't changed too many existing files and added mostly new ones, you could start a fresh project with the latest Petal Pro and migrate over the work you've done from the previous project. This is likely the easiest route. If you want to keep your git history, then you could try copying the .git folder from the previous project into the new one.

Attempt a git merge

git remote add petal_pro [email protected]:petalframework/petal_pro.git
git fetch petal_pro
git merge petal_pro/main --allow-unrelated-histories
Comment from a Pro user:
  • Use rename_phoenix_project.sh to rename back to PetalPro
  • rsync -r --delete --exclude=.git ~/code/petal_pro-1.3.0/ ~/code/your-app
  • git checkout HEAD path/to/files/rsync/deleted/but/shouldnt/have (I used --delete with rsync so I'd know about files that were removed, for example, I think some of the org stuff was moved, and I don't want cruft)
  • git add -p
  • Use rename_phoenix_project.sh to rename back to your app name

Git diffing

Comment from a Pro user:
The easiest way for me is to create a fresh project from the updated petal_pro, rename it to the same name as your existing project, and then run a diff tool like Araxis merge against the root directories. As long as you have mostly added your own files and not modified the template files much it doesn't take too long. You can either merge the template changes into your existing project (better for git history) or merge your customizations into the fresh project.
​
​