What is Buddy?
Who uses Buddy?
Why developers like Buddy?
Here are some stack decisions, common use cases and reviews by companies and developers who chose Buddy in their tech stack.
I use Laravel because it's the most advances PHP framework out there, easy to maintain, easy to upgrade and most of all : easy to get a handle on, and to follow every new technology ! PhpStorm is our main software to code, as of simplicity and full range of tools for a modern application.
Google Analytics Analytics of course for a tailored analytics, Bulma as an innovative CSS framework, coupled with our Sass (Scss) pre-processor.
To deploy, we set up Buddy to easily send the updates on our nginx / Ubuntu server, where it will connect to our GitHub Git private repository, pull and do all the operations needed with Deployer .
CloudFlare ensure the rapidity of distribution of our content, and Let's Encrypt the https certificate that is more than necessary when we'll want to sell some products with our Stripe api calls.
Asana is here to let us list all the functionalities, possibilities and ideas we want to implement.
We use Buddy because it's extremely easy to start working with, because of the powerful GUI which let you configure pipeline in minutes, but also let you switch to the YAML based pipeline, and have full control over your pipeline and deploy cycle. I also appreciate the support by the Buddy team, they are an extraordinary focused team, which are able to act and think as a developer, and this is extremely important!
When I first built my portfolio I used GitHub for the source control and deployed directly to Netlify on a push to master. This was a perfect setup, I didn't need any knowledge about #DevOps or anything, it was all just done for me.
Over the weekend I decided I wanted to know more about how #DevOps worked so I decided to switch from Netlify to Amazon S3. Instead of creating any #Git Webhooks I decided to use Buddy for my pipeline and to run commands. Buddy is a fantastic tool, very easy to setup builds, copying the files to my Amazon S3 bucket, then running some #AWS console commands to set the
When I made these changes I also wanted to monitor my code, and make sure I was keeping up with the best practices so I implemented Code Climate to look over my code and tell me where there
other issues I've been super happy with it so far, on the free tier so its also free.
I did plan on using Amazon CloudFront for my SSL and cacheing, however it was overly complex to setup and it costs money. So I decided to go with the free tier of CloudFlare and it is amazing, best choice I've made for caching / SSL in a long time.
I use Buddy because I don't have time to do things manually as I did a decade ago. I have more work, more clients, more responsibilities because Buddy takes out the wasted time doing manual tasks. Don't work like its 2008. Work like its 3018!
I started my continuous intagration with Buddy. This is very good tool to start with. Easy configuration, many options and integrations, everything configurable via web page interface. My build proccess was configured in few minutes. Then I tried CircleCI and I like it. After you read documentation, it is easy to configure. Builds are faster. I can store/share artifacts, test result. Build wolkflow description is stored in repository. Now I prefer to use CircleCI
- Automatic deployments on push to branch
- Docker-based builds and tests
- 10-minute setup of complete environment
- Integrates with GitHub, Bitbucket & GitLab
- DevOps and website monitoring actions
- Clear and telling UI/UX
- Supports all popular languages and frameworks, including PHP/Laravel, Node.js, Rails, Python, Java, .NET Core, Elixir and Go