These are chat archives for collectiveaccess/support

29th
May 2018
bowbot
@bowbot_twitter
May 29 2018 12:02
Is there a way to use GIT to update an instance once it is installed? The only detailed upgrade process I have seen involves manually removing and replacing files within the instance?
Julia
@juliaweist
May 29 2018 13:22
@bowbot_twitter yes you can simply do a git pull to update after install. Just make sure your config files, theme changes, etc. are localized
@sheggen what does the import log say? Try setting the lot_status_id via the parameter "objectLotStatus" instead of inside the attribute parameter
bowbot
@bowbot_twitter
May 29 2018 13:38
@juliaweist excellent—when I search for localize git, lots of translation options come up, can you say that in a different way?
Julia
@juliaweist
May 29 2018 14:44
@bowbot_twitter for example any changes you make to the files in /app/conf in your Providence directory should be stored in /app/conf/local. The /local folder is ignored by git so your edits to app.conf, for example, don't read as a conflict during the pull.
bowbot
@bowbot_twitter
May 29 2018 16:10
@juliaweist Thankyou—great tip--was not showing up in documentation. let me give this a try. Will a GIT changes automatically ignore setup.php, media folders and files, import mappings and the like?
@juliaweist I am more familar with SVN
Julia
@juliaweist
May 29 2018 17:38
@bowbot_twitter you can do a "git status" and this will show you everything "modified" that you need to worry about. Import mappings, etc. should show up as "untracked" which won't create conflicts with git. Make sure you keep a copy of setup.php-dist and you won't have a git issue with the modified setup.php