Introducing Forge CLI

One of the most requested features of the Forge platform, particularly from the more techie folks who are used to using services like Heroku, Firebase and other such developer platforms, has been to provide a command-line-interface (CLI) for Forge.

Previous Deployment Methods

Up until now you had 3 ways to publish your sites to Forge:

  • Drag & Drop a .zip into the browser
  • Github Sync
  • Dropbox Sync

Each of these has made it infinitely easier to create and deploy your static sites than it would be otherwise.

We then added autosync and webhooks so that you can automate the deployment, such as when you commit some code to your Github repository or updating some content on an external service like Contentful.

The Terminal Gap

But, for many users who live in the Terminal (or platform equivalent), not being able to perform these tasks without opening the browser or creating service-specific accounts was a barrier, and if not, could be a workflow / productivity hurdle too far.

The Solution

So we set about building a small CLI that enables you to do pretty much everything you'd initially expect.

Next Steps: In the next steps we'll get a run-down of the Forge-CLI app.

Join the Discussion

Have questions or want to share your experience? Join our community discussion to connect with other developers and get help from the Forge team.

Visit Forum Discussion