This is how we’re currently setup:
- I run the docker command to clone my environment
dotcli instance
to the remote instance i just cloneddotcli pull
to get the files locally in a better folder structuredotcli instance
to switch to my local instancedotcli push -w
to push changes i’m making to vtl and js files “live”- Refresh the dotCMS page in my browser to view my changes
I make changes and when I’m finished I commit them. Currently, we’re manually keeping our remote in sync with GitHub, but I’ll setup GitHub actions to do this soon.
Pros:
- This lets me have the entire instance run locally. This is vital since it lets me use the IDE tools and snippets we’ve already created
- “migration” seems as easy as
dotcli config
ing another remote instance anddotcli push
ing
Cons:
- dotcli push -w 1 seems to be the fastest “sync” i can get, and sometimes i refresh to see my changes before it’s finished pushing
- /files directory also contains images, videos, and other media used on the site. We can use
git lfs
for those or just ignore them
This largely supports the direction given in this article.
Is there anything I’m making more difficult for myself? Anybody have something drastically different?