A 7-minute overview on deploying to different environments on Core dna.
Schedule a one-to-one consultation with your product specialist
Here’s what you can expect:
- Walkthrough: An introduction of the Core dna platform
- Analysis: Personalized recommendations based on your business needs.
- Case studies: How other businesses have used Core dna to scale more efficiently
Video transcription: How to Deploy to Different Environments on Core dna
So in this video we're going to see how development is done on coordinate by front end teams. The coordinate platform is completely decoupled from the UX. So front end development teams can actually build complex front end users lined interactions for customers while being able to use standardized language to talk to Core dna.
I've just logged into an IDE, just a normal IDE. And what you'll notice about this on the left hand side is a structure of how this particular site, this demonstration site that we're working from, is structured.
You'll see that it has assets that are there. It'll have the modules which are the Core dna applications that are being used. It will have a templates directory where we have the base templates. It'll have a template directory which is where the compile templates go.
It may have a web images directory. You'll see the node modules has been installed as we'll be using Gulp in this particular project to build out our JavaScript and we'll have our source JavaScript and then finally we'll have a distribution JavaScript.
So as a developer you can establish your own environment the way you'd like to work on it. And as long as you stay within the standards of the modules directory, the web images and the template directory, then your site should function normally.
In addition, what you'll also notice down the righthand side here is that this site is connected to the Git repo. And it's a very straightforward approach to once you have either use ours or use your own repo, you're able to look at all the remote branches, all the different branches that have been developed for this website, and you're able to create new branches and check out branches.
So Core dna has complete integration into Git and offers you the ability to push your changes to a QA environment for testing and then to merge those changes into production. But before you kind of get into the QA environments and pushing to the repos and all that, most developers just want to be able to quickly develop.
And what Core dna has is a SFTP environment development environment that we've established. And it's very simple to configure. You go down to deployment, you can go down to configure and you can establish your connection to the host.
You can set up your mappings for how you want the site to map, and you can then establish it as a connection. So really, to deploy to those environments is very simple. You make a change to a site. So I'm going to go into a site here, and I'm going to update this tag here to say Sam was here, and all we do is save.
And you'll notice that the changes are sent instantaneously to our dev server. And when we look at the environment, we can see here that if we press refresh on the dev environment, all of a sudden now Sam was here on the dev environment, and if we want to remove it, it's a simple case of just removing the content.
And it will automatically transfer and then just press refresh and the change will be gone. So in this way, developers can quickly create UX's and themes and solutions for their customers in a very localized approach.
And then when they're ready, they can then push those changes into production. And so we have here the production version of the Media Center and you'll notice that it has a number of similar directories.
You'll see here is the source files we can return and then we have the all JS files. We then have the modules that are being used and they generally mimic the modules that are here. Now, once a developer is ready to push their changes into testing, they're able to then come to their IDE and do a commit and a push.
And what happens then is through the use of webhooks, Core dna is able to then apply those changes to the production environment. If we take a longer look at the repo itself, we're able to see that this keeps all the commits that you do.
And so this hasn't been updated in a number of months, but we can actually go into those commits and have a look at what were the changes, what exactly changed, and if we want to, we can actually back those changes out.
In addition, we can see all the branches that are currently available and at what progress these branches are in terms of the master branch. So we can actually switch between them. We can also see the pull request that have occurred and so on.
So all the sites that you work on actually can be found here and you're able to navigate between them. You could do a you can go into a site, clone the site, pull it down, it then becomes available in your IDE, and you can begin work either by doing a deploy to your deploy environment or by doing a commit and push for small changes straight through to your Bitbucket account. The IDE itself supports the inclusion of Git. It's very simple to set up and also includes the ability to deploy. So as long as your server or your ID can support it, you can then use Core dna to develop out of the box.
Related posts
