deployment - Staging Environment best practices -
i'm setting staging environment laravel application because want see how changes behave live before going production.
setting env. fine, since i'm using bitbucket , dploy, makes workflow smooth.
my questions domain setup. should create subdomain staging.mydomain.com test it? should limit staging version's access somehow or should make public unpublished url?
any other tips on creating environment?
it's first application.. welcome.
if need test facebook integration, instance, it's better have subdomain (instead of domain in 2 ports, i.e., http://www.domain.com:8080 clash facebook app http://www.domain.com, there no way of having separate fb applications changing port, if have http://test.domain.com can app in fb).
also, if rely on encrypted stuff eventually, on other hand have use same domain staging , testing, since commercial libs issued key uses domain of application (e.g. licensed lib http://www.domain.com , not work on http://test.domain.com). ssl certificates have same issue.
you must have robots.txt hiding staging don't forget! , if want issue basic http authentication that's decision :)
Comments
Post a Comment