# Site Can't Be Reached on Digital Ocean

**URL:** https://discourse.roots.io/t/site-cant-be-reached-on-digital-ocean/10481
**Category:** trellis
**Created:** 2017-09-21T23:53:25Z
**Posts:** 7
**Showing post:** 6 of 7

## Post 6 by @fullyint — 2017-09-22T00:27:17Z

> [@Multisite remote provision/deploy doesn't create any database tables](https://discourse.roots.io/t/multisite-remote-provision-deploy-doesnt-create-any-database-tables/9097/2):
>
> Given Trellis creates DB tables in development, it can be surprising that …
> 
> > **Trellis does not automatically install WordPress on remote servers.** It’s normal and expected to see the WordPress install screen the first time you deploy. It’s up to you to either import an existing database or install a fresh site. _[– deploy docs](https://roots.io/trellis/docs/deploys/#deploying)_
> 
> Deploying is a process you will repeat many times as your site evolves and updates over time, whereas importing or creating DB tables will typically only happen once, after your initial deploy. So, the deploy doesn’t automatically create/import tables.

It would be less confusing if for new multisite deploys the default WP install screen would show in the browser like it does for regular sites (non-multisite).

Trellis figures people will vary in how they want to install WP (manual in browser, manual via wp-cli, some script, etc.), so it leaves the install in your hands. I suspect it would be valuable if Trellis had a pre-built install-on-deploy option (disabled-by-default).

---

_[View the full topic](https://discourse.roots.io/t/site-cant-be-reached-on-digital-ocean/10481)._