When you use Skuid to build your enterprise applications, you’re clicking around, dragging and dropping components into pages. Those actions turn into declarative metadata about your site.
And often, to accurately test and integrate that metadata, you need to move it around. For example, you might need to:
- download an entire site’s worth of pages to make small adjustments locally
- move Skuid configurations from a sandbox site to a production site
- store Skuid configurations in a version control system
While it’s possible to save page XML and create page packs, moving entire apps’ worth of Skuid objects from site to site can prove challenging. Enter Skuid’s command-line-interface (CLI). Using the Skuid CLI, you can easily pull (download) Skuid pages and push (upload) Skuid metadata from one site to another using only a few commands.
Achieve continuous integration with Skuid CLI.
Users want a change management process that works for them. They want the latest features, but they also want to know that the software they're using has been thoroughly tested and thoughtfully released.
That’s the goal of organizations that practice continuous integration, which, in addition to making sure users are always using the best version of your product, makes finding and removing bugs dramatically easier. By integrating code (and the metadata that Skuid produces when you drag, drop, and customize components) daily, developers can spend less time backtracking to find errors and more time delivering new value-add features. With the Skuid CLI, you can make continuous integration second nature in your organization.
Use Skuid CLI to maintain source control throughout your project.
Source control is like tracking changes in Microsoft Word, or viewing the comment history in Google docs, but for enterprise app development.
Without source control for your code (or, in the case of Skuid development, your declarative configurations), you might:
- Accidentally override important changes made by another developer without realizing it.
- Have to create a completely new file every time you want to try something different without losing your original work.
- Lose your mind.
But with source control, you can access a detailed history of everything that’s been done in a file so that you don’t lose your progress or your marbles. The Skuid CLI makes it easy to store your Skuid configurations in a version control system where you can access this valuable information.
You can easily pull (download) Skuid pages and push (upload) Skuid metadata from one site to another using only a few commands. For developers already using a version control system, that means that when you’re working with Skuid, you don’t have to change your tools. Just use CLI to easily connect your own version control system with Skuid.
Get fast, seamless automated testing with Skuid CLI.
Just like with fully-coded enterprise applications, you don’t want to mess with your Skuid configuration in production, because you risk breaking important things in the application. For that reason, Skuid developers typically build and complete automated testing in their own sandbox environments.
With the Skuid CLI, you can build and test to your heart’s content, and when your new or updated app is ready, you can deploy it to your production site, and more importantly, your users, quickly. Changes you make can easily be grouped into releases with the Skuid CLI, so that you can make more significant updates in bulk and notify your users all at once. Ready to try your hand developing with Skuid? Get a free trial today.
