This is a 5-minute guide on how to allocate the code under version control and automate its deployment.
Import an existing website to a new Buddy project
Working with Buddy is based on projects which consist of:
- The Git repository with the source code of the website.
- The delivery automation pipelines.
Create a new project and use the import from an FTP server option. You are required to enter the FTP server information and the path, and Buddy will download the files and move them into the repository.
Below you will see how to do it:
Playing with the Git repository
Upon completion of the import process, the code will come up under Code tab. Here you can browse the contents of your repository, create and handle branches, view commit history and edit files in a handy code editor — all most popular Git features available with just a click of a mouse button.
Running Your First Pipeline
While importing the files from an FTP location, Buddy automatically sets up a continuous delivery pipeline for you. This pipeline will deploy every single change you make to the code to the FTP server, according to the data introduced by you for the source code import process.
Now let’s give the pipeline a try by following a few steps below:
- Go to code tab
- Change what you need in the code and save changes (in this example we shall change index.html).
- Go to Pipelines and run the continuous delivery pipeline created by Buddy.
- View the site in the browser.
When you’re ready with the modifications, the only thing that remains is clicking the Run button and Buddy will automatically deploy your changes — you didn’t have to choose the files manually, upload them, enter login data or complete any other tedious and time-consuming task.
Like it? We have good news for you — you can arrange as many pipelines as you want! Pipelines — the core of Buddy — are flexible and simple to use and will help you completing any tasks that can be possibly automated.
Other Things To Keep In Mind
Editing files online is cool as long as you’re dealing with small fixes. If you want to work on new features, it’s much better to build them locally. In order to do it, you just have to clone the repository, commit the changes and push them to Buddy. More info, on how to move on with Git, you can find here.
Also, the application under development usually requires some testing and building. Only after carrying out these actions it’s ready for the delivery. Buddy is the key to automate them— see the following guides:
- How to Use Buddy to Automate Gulp Tasks and Generate Webfront from SVG Files..
- How to Automate Tests and Deployments of Node.js Apps with Buddy..
- How to Set Up a Continuous Delivery to Heroku.
What's Next
This is just a brief compendium of what Buddy offers regarding version control, development, and deployment. If you are interested in our solution, you can read more about Buddy in other guides.
If you need any further assistance, don’t hesitate to contact us at support@buddy.works or simply register for the trial version and have a look at Buddy.
Thanks for your attention!