Furnace will deploy resources outside of the free tier on your cloud platform. We are not responsible for any costs incurred
Our aim is to have you up and running in less than 5 minutes. You'll need to meet the following prerequisites (see current limitations):
Further prerequisites are needed depending on which platform you will be deploying to.
To list projects already available in GCP if you have them run
gcloud projects listfrom the gcloud CLI
To find your subscription ID run
az account show --query id -o tsvfrom the Azure CLI
The process starts with installing the Furnace CLI and running
npm install @project-furnace/cli -g
You'll be asked a series of questions relating to your environment. After filling in the questions Furnace will start creating various resources in your chosen platform. These resources will consist of a deployment container, API endpoints, serverless functions, credentials and keys, storage, and message queues. For a more indepth look at what is actually being created please see the relevant platform specific documentation.
This may take a few minutes to complete but when it's done you will be notified via the CLI. Once this command has completed you're ready to create a new stack.
furnace new my-stack
Again you'll be prompted to answer a series of questions about your Stack. Furnace will then initialise a few more resources required for your Stack including GitHub repositories and webhooks. You'll now have a new repository created that you can start to build on. You can learn more about working with Furnace Stacks with the 5 Minute Walkthrough.
stack.yamlcontains a list of environments, by default you have
production. Once you're ready deploy your first stack, we do so using a standard
git add .
git commit -am "initial commit"
git push origin master
This pushes to the first environment defined in your Stack, you can see the deployment status in
environmentsin the Stack repository in GitHub or using the
furnace statuscommand inside the Stack directory.
If something goes wrong or a deployment doesn't complete please see the platform specific page on where to find the relevant logs.
Once you're happy that your Stack is functioning how you expected in your initial environment you can
promoteit to an upstream environment eventually towards its final/production environment. For example, keeping with the default environments, to promote the
stagingyou would simply:
furnace promote dev
furnace ignitecan also be run with the following command line arguments:
These args can be used for any target platform
These args are platform dependent: