Timeline for How to use SIM to setup dev environment for existing Sitecore instance?
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 8, 2019 at 2:28 | comment | added | Don Cheadle | sorry Chris I moreso had in mind... if we copy the Prod DB's down to QA... then we'd know QA's Sitecore content correctly 100% matches Prod right? (ignoring website files, I know that's not part of DB. Just thinking of Sitecore items/versions) | |
| Sep 6, 2019 at 21:40 | comment | added | Chris Auer | Certainly could use SQL, but it is not optimum. When you are able to take a vanilla instance and deploy into it. Ending with a proper running website. Then you know exactly what it takes to make your site run. When you are just using SQL, you can't build trusted QA and UAT sites. Since they are just copies of dev. You don't know what is "really" in the DB. | |
| Sep 6, 2019 at 21:36 | comment | added | Don Cheadle | instead of knowing various packages to get the Sitecore items... why not just use a DB backup? I.e. pull down the master DB and restore it into your local dev DB? (for the 3 relevant Sitecore DB's) | |
| Jul 26, 2019 at 19:14 | comment | added | Don Cheadle | What do you mean by "items" and "packages" -- are you referring to items defined in Sitecore e.g. in the Sitecore admin side? And in turn are stored in the sitecore DB. | |
| Jul 26, 2019 at 19:00 | comment | added | Chris Auer | And you need to know what items you need. This is why you need to know from dev what needs to be installed. Code and packages. Just gettin all the missing dlls and files is bad practice. | |
| Jul 26, 2019 at 18:59 | comment | added | Don Cheadle | In that case, why not just use beyond compare to compare entire /Website/ folder against a Vanilla instance? I think it can also show files that are different/modified e.g. dll's. But maybe that'd get confusing. | |
| Jul 26, 2019 at 17:44 | comment | added | Chris Auer | No. You would need to know that from development. Any dlls or sitecore packages you will need. You could do a beyond compare for the bin folder and app_config vs a vanilla install to get an idea. But you really should know what it actually needed. | |
| Jul 26, 2019 at 17:41 | comment | added | Don Cheadle | Thanks so much Chris! But what if you inherit a Sitecore app, so all you have is the inetpub site running. Any suggestions for how you would identify the non-vanilla stuff that you'd need to put into CI or source? (since you don't just want to put the entire inetpub/asd/ site into source) | |
| Jul 26, 2019 at 0:59 | comment | added | Chris Auer | Deploy it with visual studio or CI. If your solution or CI is perfect, you can take any vanilla machine and deploy all it needs to run. | |
| Jul 26, 2019 at 0:57 | comment | added | Don Cheadle | Gotcha that makes sense. So basically copying around the vanilla instance inetpub folder to stick on other machines? Interesting. A bit unrelated... but how would you go about separating custom source code from vanilla install for a site that you inherited? E.g. it's already running somewhere in inetpub with custom code bundled on top of the base instance, and no up-to-date source code repo is available for the site. | |
| Jul 26, 2019 at 0:47 | comment | added | Chris Auer | Do the backup to a vanilla instance. | |
| Jul 26, 2019 at 0:45 | comment | added | Don Cheadle | So if I go this route... you're saying you basically copy the whole Sitecore inetpub folder and put it on another machine? But then how do you separate out the custom code from the rest of the inetpub files? (e.g. I believe usually you want to keep your custom source in a separate folder during development and then deploying into inetpub) | |
| Jul 23, 2019 at 14:37 | history | answered | Chris Auer | CC BY-SA 4.0 |