Open rgilman opened 6 years ago
Robert and all.
What I've done personally is:
This now allows me to interact with Git as I normally would and have the changes automatically flow into the dev env. Would love to hear what others think about this setup.
@robertdavidwest that sounds like how I have my local dev env setup as well. Perhaps we could also be managing the theme on the Digital Ocean site with git but I'm not clear on how to do that.
At the moment though, I think I've sorted out the customization changes needed to switch the DO site from bfcom-theme to bfcom and thereby able us to use GitHub Updater to bring the DO site into sync with this repo.
I don't feel there is any need to bring our local dev sites into sync with the DO site quite yet. I'd like to give it a little more time to see if there is anything I missed in the customization. Once the dust settles it likely would be good to bring them into sync which can likely be done through a database sync.
Here's what I've done so far in getting bfcom to match the customizations of bfcom-theme:
Under Appearance>CBOX Theme Options: Layout>Background Image> Disable Image (checkbox) Footer>Background Color> #ffffff Footer>Background Image> Disable Image (checkbox)
Under Appearance>Widgets: Remove all widgets under Footer Left, Middle, Right, Homepage Top Right, Center Homepage Left -> (bbPress) Recent Replies; max 5, show author Homepage Middle -> (BuddyPress) Members Homepage Right -> (BuddyPress) Groups
On Homepage: sort Members and Groups by Active
With subversion we used webhooks to keep dev versions synced with latest updates. There must be something similar for Github. I'll make a note here of some links to research
https://developer.github.com/webhooks
https://gist.github.com/noelboss/3fe13927025b89757f8fb12e9066f2fa
https://github.com/scriptburn/git-auto-deploy
I've installed GitHub Updater on the DO dev site with the intention of creating a streamlined (although not quite automated) process for updating bfcom on the dev site. It's not yet working as smoothly as I would like because GitHub Updater requires the repo name (bfcom in our case) to be the same as the theme folder name (currently bfcom-theme).
My current plan is to bring these into alignment by changing the theme folder name to bfcom. This turns out to be not quite as simple as switching themes because the cbox-theme parent has settings attached to the name bfcom-theme.
I'll report back once I get this sorted out.
Also, if you have ideas for a potentially better way to streamline or even automate the updating of dev sites whenever the master branch is updated here in the repo, please let us know.