We are trying to streamline the process of showing clients their websites whilst in development without the need to change absolute paths etc.
我们正在努力简化在开发过程中向客户展示其网站的过程,而无需更改绝对路径等。
We mostly develop locally and change our hosts files to reflect the domain name, when we are ready to show the client we copy the files to www.client.com/dev but I'm looking for a better method, any suggestions that can make this process smoother and faster would be great.
我们主要在本地开发并更改我们的主机文件以反映域名,当我们准备向客户端展示我们将文件复制到www.client.com/dev但是我正在寻找更好的方法,任何可以提出的建议这个过程更顺畅,更快将是伟大的。
2 个解决方案
#1
If you always host the site on a separate domain and not in a subdirectory, you will never have to change absolute paths. So instead of hosting a site in development at www.client.com/dev try dev.client.com. Another option would be to use client.yourcompany.com.
如果您始终在单独的域而不是子目录中托管站点,则永远不必更改绝对路径。因此,请访问dev.client.com,而不是在www.client.com/dev上开发网站。另一种选择是使用client.yourcompany.com。
Also try to protect the site in development with HTTP basic authentication. This is easy to set up in most web servers, without changing your web application. Also, if the content is even remotely sensitive in any way, use HTTPS as well.
还尝试使用HTTP基本身份验证保护开发中的站点。这在大多数Web服务器中很容易设置,无需更改Web应用程序。此外,如果内容甚至以任何方式对远程敏感,也请使用HTTPS。
Alternatively, let them simply come over to your office and present it to them (or go to them and present it). The upside is that you have full control over what they will and won't see, and it never has to go online.
或者,让他们简单地到你的办公室并把它呈现给他们(或去他们并呈现它)。好处是你可以完全控制他们将会看到和不会看到的东西,而且它永远不必上网。
#2
Well, we have client.t.uw.ru site which is universally visible.
好吧,我们有client.t.uw.ru网站,它是普遍可见的。
When it matures, it moves onto www.client.com and is pushed to search engines.
当它成熟时,它会移动到www.client.com并被推送到搜索引擎。
Thus, we have a * DNS entry on t.uw.ru domain which makes it easy.
因此,我们在t.uw.ru域上有一个* DNS条目,这很容易。
#1
If you always host the site on a separate domain and not in a subdirectory, you will never have to change absolute paths. So instead of hosting a site in development at www.client.com/dev try dev.client.com. Another option would be to use client.yourcompany.com.
如果您始终在单独的域而不是子目录中托管站点,则永远不必更改绝对路径。因此,请访问dev.client.com,而不是在www.client.com/dev上开发网站。另一种选择是使用client.yourcompany.com。
Also try to protect the site in development with HTTP basic authentication. This is easy to set up in most web servers, without changing your web application. Also, if the content is even remotely sensitive in any way, use HTTPS as well.
还尝试使用HTTP基本身份验证保护开发中的站点。这在大多数Web服务器中很容易设置,无需更改Web应用程序。此外,如果内容甚至以任何方式对远程敏感,也请使用HTTPS。
Alternatively, let them simply come over to your office and present it to them (or go to them and present it). The upside is that you have full control over what they will and won't see, and it never has to go online.
或者,让他们简单地到你的办公室并把它呈现给他们(或去他们并呈现它)。好处是你可以完全控制他们将会看到和不会看到的东西,而且它永远不必上网。
#2
Well, we have client.t.uw.ru site which is universally visible.
好吧,我们有client.t.uw.ru网站,它是普遍可见的。
When it matures, it moves onto www.client.com and is pushed to search engines.
当它成熟时,它会移动到www.client.com并被推送到搜索引擎。
Thus, we have a * DNS entry on t.uw.ru domain which makes it easy.
因此,我们在t.uw.ru域上有一个* DNS条目,这很容易。