{"id":4910,"date":"2020-11-25T03:20:22","date_gmt":"2020-11-24T21:50:22","guid":{"rendered":"https:\/\/opstree.com\/blog\/\/?p=4910"},"modified":"2025-11-27T17:06:22","modified_gmt":"2025-11-27T11:36:22","slug":"buildpiper-a-saas-playground","status":"publish","type":"post","link":"https:\/\/opstree.com\/blog\/2020\/11\/25\/buildpiper-a-saas-playground\/","title":{"rendered":"BuildPiper – A SAAS Playground"},"content":{"rendered":"\r\n

\"Buildpiper<\/p>\r\n

As of late, I took a dive at setting up and connecting WordPress with the database using container services. I created a website but couldn’t figure out where and how to deploy it. I was looking for a way with less exertion, at least expense, and minimum time. At this point, I thought of a SAAS product by Opstree Solutions called BuildPiper. I’d been wanting to try it for some time now and this looked like a good opportunity. Going in, I thought I’d have to go through the usual chores of using a new product, tons of documentation, hit and trial, etc. before I could get the hang of it. I wasn’t expecting a functioning website until at least the end of the day. But as soon as I had signed up, the onboarding felt like a smooth stream. I was able to deploy my site in less than an hour.<\/p>\r\n\r\n\r\n\r\n

BuildPiper<\/strong><\/p>\r\n\r\n\r\n\r\n

BuildPiper<\/a> gives the adaptability to set up applications with or without the manifest. On the off chance that somebody would not like to use the manifest, BuildPiper, additionally, gives a choice to create it using GUI, which is as basic as topping off a structure. BuildPiper is a powerful container management platform that automates and comprehensively simplifies the application delivery process. It is a unified container application delivery platform, that enables the dockerized code to be deployed to production immediately with all the required observability, security, and compliance baked in.<\/p>\r\n\r\n\r\n\r\n

My experience with BuildPiper SAAS playground!<\/strong><\/p>\r\n\r\n\r\n\r\n

For me, I used WordPress as my container service which connects with MySQL containers in my setup.<\/p>\r\n\r\n\r\n\r\n

\"\"\r\n
Architecture diagram<\/strong><\/figcaption>\r\n<\/figure>\r\n\r\n\r\n\r\n

For this application, I am using two Dockerfiles which are used to configure two different pods:<\/p>\r\n\r\n\r\n\r\n

    \r\n
  1. WordPress application<\/li>\r\n
  2. MySQL Database<\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n

    MySQL database is a private service and need not be exposed publicly. Using BuildPiper, we can restrict and expose any pod\/service inside our cluster. Therefore, I decided to create a private pod structure for the database and went on ahead to create and expose the WordPress pod structure publicly using the BuildPiper ingress feature.<\/p>\r\n\r\n\r\n\r\n

    BuildPiper gives the flexibility to use environment variables like setting up build & deploy environment variables. MySQL database contains some deploy environment variables like MySQL username, default root password, etc.\u00a0<\/p>\r\n\r\n\r\n\r\n

    For WordPress containers, I am using a few build environments like WordPress username, password, database name, and database URL which I injected through BuildPiper.<\/p>\r\n\r\n\r\n\r\n

    Required Steps to configure\/setup in Buildpiper Saas <\/strong><\/p>\r\n\r\n\r\n\r\n

    First, we have to provide the service details for container service like<\/p>\r\n\r\n\r\n\r\n

      \r\n
    1. service-name<\/li>\r\n
    2. language supported by container service<\/li>\r\n
    3. repository URL<\/li>\r\n
    4. credentials detail<\/li>\r\n
    5. build type\u00a0<\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n
      \"\"\r\n
      Service information for application<\/strong><\/figcaption>\r\n<\/figure>\r\n\r\n\r\n\r\n

       <\/p>\r\n\r\n\r\n\r\n

      Now, we have to provide an environment type for microservice as BuildPiper supports multiple environments.<\/p>\r\n\r\n\r\n\r\n

      \r\n
      \"\"\r\n
      Environment type for Application<\/strong><\/figcaption>\r\n<\/figure>\r\n<\/div>\r\n\r\n\r\n\r\n

       <\/p>\r\n\r\n\r\n\r\n

      For the first part, we have to provide basic information about cluster and repository like\u00a0<\/p>\r\n\r\n\r\n\r\n

        \r\n
      1. the cluster, which is provided by BuildPiper in the playground<\/li>\r\n
      2. the namespace associated with the linked account<\/li>\r\n
      3. repository branch<\/li>\r\n
      4. Dockerfile path for container application which is common for both services [ WordPress & Database ] in my case<\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n
        \"\"\r\n
        Basic information about Application<\/strong><\/figcaption>\r\n<\/figure>\r\n\r\n\r\n\r\n

         <\/p>\r\n\r\n\r\n\r\n

        The second part contains information about build variables and CI [ continuous integration ] information for service.<\/p>\r\n\r\n\r\n\r\n

        For my application, I provided build variables which are used by WordPress:<\/p>\r\n\r\n\r\n\r\n

          \r\n
        1. Database<\/li>\r\n
        2. Database username<\/li>\r\n
        3. Database password<\/li>\r\n
        4. Hostname [ Get from database service URL value ]<\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n
          \r\n
          \"\"\r\n
          Build variables for Application<\/strong><\/figcaption>\r\n<\/figure>\r\n<\/div>\r\n\r\n\r\n\r\n

           <\/p>\r\n\r\n\r\n\r\n

          After setting up WordPress Build variables & cluster information for both WordPress and database setups, we have to provide resource Quota like CPU, RAM & replicas for different applications.<\/p>\r\n\r\n\r\n\r\n

          \"\"\r\n
          Resource quota for Application<\/strong><\/figcaption>\r\n<\/figure>\r\n\r\n\r\n\r\n

           <\/p>\r\n\r\n\r\n\r\n

          Now that we are done with that, we can provide access level information for our container application.<\/p>\r\n\r\n\r\n\r\n

          In this case, we need public access to WordPress containers through ingress routing. For this, we have to provide some information like:\u00a0<\/p>\r\n\r\n\r\n\r\n

            \r\n
          1. URL Name [ NAME.buildpiper.io ]<\/li>\r\n
          2. Expose Path<\/li>\r\n
          3. Service Port<\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n
            \"\"\r\n
            Access level information for Application<\/strong><\/figcaption>\r\n<\/figure>\r\n\r\n\r\n\r\n

             <\/p>\r\n\r\n\r\n\r\n

            For database pods, we need private access from our application. For this, we will choose private as ‘Access Level’ and provide the name\/URL for the database along with the port which is used as build variables for the WordPress application.<\/p>\r\n\r\n\r\n\r\n

            \"\"\r\n
            Access level information for database<\/strong><\/figcaption>\r\n<\/figure>\r\n\r\n\r\n\r\n

             <\/p>\r\n\r\n\r\n\r\n

            Next is an advance level configuration which is based on Scalability [ auto-scaling ], runtime\/deploy environment variables, vaults, liveness probe, and readiness probe.<\/p>\r\n\r\n\r\n\r\n

            \r\n
            \"\"\r\n
            Advance level configuration options pop-up<\/strong><\/figcaption>\r\n<\/figure>\r\n<\/div>\r\n\r\n\r\n\r\n

             <\/p>\r\n\r\n\r\n\r\n

            We can either skip it or continue with the configuration to take advantage of advanced configuration options,<\/p>\r\n\r\n\r\n\r\n

            For our case, we only needed runtime\/deploy variables for our database<\/p>\r\n\r\n\r\n\r\n

              \r\n
            1. MYSQL_ROOT_PASSWORD\u00a0<\/li>\r\n
            2. MYSQL_DATABASE<\/li>\r\n
            3. MYSQL_USER<\/li>\r\n
            4. MYSQL_PASSWORD<\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n
              \r\n
              \"\"\r\n
              Deploy\/runtime Environment variables for MySQL<\/strong><\/figcaption>\r\n<\/figure>\r\n<\/div>\r\n\r\n\r\n\r\n

               <\/p>\r\n\r\n\r\n\r\n

              Note<\/strong>: This is one time setup for each service & deployment and doesn\u2019t take much time. Each service has its own interface where we can update\/modify it.<\/p>\r\n\r\n\r\n\r\n

              After setting up both database & WordPress application services using BuildPiper, we can click on a service overview to view all services configured.<\/p>\r\n\r\n\r\n\r\n

              \"\"\r\n
              Service Overview<\/strong><\/figcaption>\r\n<\/figure>\r\n\r\n\r\n\r\n

               <\/p>\r\n\r\n\r\n\r\n

              Finally, we have to Build & deploy to make sure everything is working fine.\u00a0<\/p>\r\n\r\n\r\n\r\n

              We will first Build & deploy our database application as our WordPress application depends on the database.<\/p>\r\n\r\n\r\n\r\n

              To build database [ same for WordPress application ],<\/p>\r\n\r\n\r\n\r\n

              \"\"\r\n
              Service dashboard for database\u00a0<\/strong><\/figcaption>\r\n<\/figure>\r\n\r\n\r\n\r\n

               <\/p>\r\n\r\n\r\n\r\n

              On pressing build, it will ask for the tag name [ optional ] and branch [ optional & default branch that we already set-up while configuring service].<\/p>\r\n\r\n\r\n\r\n

              \"\"\r\n
              Build options for database service<\/strong><\/figcaption>\r\n<\/figure>\r\n\r\n\r\n\r\n

               <\/p>\r\n\r\n\r\n\r\n

              The build will create a docker image from Dockerfile that is present in the repository path,<\/p>\r\n\r\n\r\n\r\n

              Once the build is complete, we can deploy the database pod from the built image. For this, we can click on the deploy icon and select tag as required.\u00a0<\/p>\r\n\r\n\r\n\r\n

              \"\"\r\n
              Deploy database service in Buildpiper k8s cluster<\/strong><\/figcaption>\r\n<\/figure>\r\n\r\n\r\n\r\n

               <\/p>\r\n\r\n\r\n\r\n

              We can setup the WordPress application using the same set of steps.<\/p>\r\n\r\n\r\n\r\n

              Now that we are all done, we can use our public ingress URL [ NAME.buildpiper.io ] which we provided during setup to access the website.<\/p>\r\n\r\n\r\n\r\n\r\n\r\n

              \"\"\r\n
              WordPress site hosted on Buildpiper SaaS<\/strong><\/figcaption>\r\n<\/figure>\r\n\r\n\r\n\r\n

               <\/p>\r\n\r\n\r\n\r\n

              In the service dashboard, we can also check multiple things like\u00a0<\/p>\r\n\r\n\r\n\r\n

                \r\n
              1. Build & deploy status<\/li>\r\n
              2. Latest Artifact name while building<\/li>\r\n
              3. Current deployment artifact<\/li>\r\n
              4. Commit ID & messages<\/li>\r\n
              5. Build & deploy date<\/li>\r\n
              6. Build by & deploy by\u00a0<\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n

                Cool, right? I wasn’t kidding when I said, “comprehensively simplifies the application delivery process.”<\/p>\r\n\r\n\r\n\r\n

                \"\"\r\n
                Service dashboard overview\u00a0<\/strong><\/figcaption>\r\n<\/figure>\r\n\r\n\r\n\r\n

                 <\/p>\r\n\r\n\r\n\r\n

                Benefits of BuildPiper Saas<\/strong><\/h2>\r\n\r\n\r\n\r\n
                  \r\n
                1. BuildPiper gives multiple ways to configure application deployment:
                  Build manifest with UI
                  Upload manifest file<\/li>\r\n
                2. CI\/CD pipeline for single\/multiple deployments<\/li>\r\n
                3. Multiple language CI support<\/li>\r\n
                4. Single click Build\/Deploy<\/li>\r\n
                5. Buildpiper also maintains build & deploy log history for each artifact<\/li>\r\n
                6. Onboard a Dockerized service in minutes<\/li>\r\n
                7. Setup & Run hassle-free secured Pipelines<\/li>\r\n
                8. Enable the most robust & secure DevSecOps CI in a few clicks<\/li>\r\n
                9. Single click service modification<\/li>\r\n
                10. Easy interface to visualize the configuration<\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n
                  \"Thats<\/figure>\r\n\r\n\r\n\r\n

                   <\/p>\r\n\r\n\r\n\r\n

                  Know more about BuildPiper Saas<\/a> & features<\/p>\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n

                  To set up the first containerized application on BuildPiper Saas, visit<\/a>:<\/p>\r\n\r\n\r\n\r\n

                  Gif Source<\/a><\/p>\r\n

                  Opstree is an End to End DevOps solution provider<\/p>\r\n

                  \r\n\r\n<\/p>\r\n

                  CONTACT US<\/a><\/p>\r\n\r\n\r\n","protected":false},"excerpt":{"rendered":"

                  As of late, I took a dive at setting up and connecting WordPress with the database using container services. I created a website but couldn’t figure out where and how to deploy it. I was looking for a way with less exertion, at least expense, and minimum time. At this point, I thought of a<\/p>\n","protected":false},"author":192321000,"featured_media":29900,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_coblocks_attr":"","_coblocks_dimensions":"","_coblocks_responsive_height":"","_coblocks_accordion_ie_support":"","jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2}},"categories":[708216545,28070474],"tags":[3370,768739312,69816,242358,768739305,32466874,768739309,57812,17927],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/opstree.com\/blog\/wp-content\/uploads\/2025\/11\/DevSecOps-1.jpg","jetpack_likes_enabled":true,"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/pfDBOm-1hc","jetpack-related-posts":[],"_links":{"self":[{"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/posts\/4910"}],"collection":[{"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/users\/192321000"}],"replies":[{"embeddable":true,"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/comments?post=4910"}],"version-history":[{"count":27,"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/posts\/4910\/revisions"}],"predecessor-version":[{"id":30083,"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/posts\/4910\/revisions\/30083"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/media\/29900"}],"wp:attachment":[{"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/media?parent=4910"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/categories?post=4910"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/tags?post=4910"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}