# Deploying from windows

**URL:** https://discourse.roots.io/t/deploying-from-windows/4434
**Category:** trellis
**Created:** 2015-08-07T14:46:44Z
**Posts:** 14
**Showing post:** 7 of 14

## Post 7 by @DemaniClassic — 2015-09-07T00:51:59Z

Check out my post here

> [@Windows Sage Setup Provisioner](https://discourse.roots.io/t/windows-sage-setup-provisioner/4690):
>
> Hi, I have created a [bash script](https://gist.github.com/darrienworth/05b68adf245e5fc7912a "bash script") that will automatically setup sage for Windows users. This has been tested with Windows 8.1 and the most recent version of Trellis as of 9/6/15. This solves the lengthy process that must be completed after every ‘vagrant up’ or ‘vagrant destroy’ It completes many of the steps that I have described in the post below. Soon I wll update this script to handle all of the file changes that must be handled on the VM in order to get the entire Trellis, Bedrock, …

I have created a script that handles most things that need to be configured in order to setup the sage theme and deploy to staging and/or production server.

The issue you mentioned above is taken care of by the script. It runs the solution I mentioned above automatically.

---

_[View the full topic](https://discourse.roots.io/t/deploying-from-windows/4434)._