Core features

Automated DNS

Steward configures your DNS and webserver to automatically handle any incoming requests and load the code from the appropriate directory. Configure the domain extension you like to use for local development to always point to your local machine. For example, when you use the .test extension, we will make sure to point yourdomain.test to 127.0.0.1. This way we eliminate any need to change the /etc/hosts file.

Automated webserver

Steward uses caddy webserver. It makes sure to use the right web root dynamically. For example: when you request yourdomain.test in your browser, it will automatically load the contents from ~/sites/yourdomain.

Also, Steward tries to guess your web root during boot. When one of your projects is built in Magento, the web root will automatically point to /pub as required for Magento to work correctly. Steward will include the rewrites for the static content files as well for Magento projects. For Laravel, it uses the /public directory and for Wordpress, uses the root / directory, unless it’s built in bedrock, in which case it uses the /web directory.

Terminal Multiplexer (tmux)

Steward uses tmux to keep the webserver running in a background window. To tap into the window and follow the process' command line output. Run tmux attach -t caddy to tap into the caddy webserver window. To leave the window, hit ^b + d (for detach). If you accidentally close the window, run stew http:restart.