Using Developer Workspaces (Cloud IDE or Local Virtual Env) with Code Studio

Whether your developer workspace is local development or a virtual environment, developing and building apps is typically the same. It will be a combination of the environment you build in, the tools you use to manage your code, the tools to collaborate and manage issues, and where you test and deploy your code. Acquia has made it easy for you to pick your developer workspace, bring your own or use Cloud IDE and let Code Studio complete your Drupal workflow.

Acquia Code Studio is a complete DevOps platform built in partnership with GitLab. Code Studio provides a complete pipeline following best practices for application development out of the box. Whether you have an existing Drupal application or are building a new one, your first commit to Code Studio will start a CI/CD pipeline. Without having to write the GitLab YAML file, Code Studio will build, test, and deploy your code. Code Studio will run a Build Code job to install Composer dependencies for the first job. Next, it will run a Test Drupal job and run three tests: PHP Code Sniffer, PHP Stan, and PHPUnit. After that, Code Studio will run a Static Application Security Testing (SAST) job, and a Secrets Detection job will scan your code to confirm that you have not accidentally committed any secrets. The last job is a Deploy Drupal stage job. All of this happened using the Code Studio out-of-the-box defaults.

You have pushed your code to Code Studio and are up and running. Now, no problem if our smart defaults are not 100% what you want. You have the freedom to customize and integrate it with whatever you want. There is no limit, and you can make necessary changes/modifications/enhancements with instructions from Acquia documentation here. The flexibility it comes with, and the fact that it is right there for you building on top of the power of GitLab, means it is a safe, comfortable choice. You don’t have the risk of locking yourself in with a proprietary product because it is open source.

Partnering with GitLab means you have all the tools you need to collaborate and are provided in an instantly familiar way to any developer. Every developer knows GitLab or Github. You don’t have to worry about someone having to figure out a new tool. All the tools for issues, milestones and merge requests are in one place. Everything is set up and ready to go. If someone comes on your team or project, they are already familiar with the tools. Because everything is woven together seamlessly, it only adds to your work and doesn’t distract you.

It doesn’t matter where you are currently building your application. Bring your developer workspace to develop, and use Code Studio to handle the rest. Continuous integration and continuous delivery can take weeks to get configured. You can get started immediately with your first commit using Code Studio’s default best practices for application development.