Closed gabrielstuff closed 2 years ago
Hello @gabrielstuff thanks for your feedback,
Staging and Dev sites are still not fully supported at this time. A few months ago we had a security concern regarding SFTP credentials and the way that the Dev site was setup, so we delayed implementing the Dev site feature.
The Staging site technically works already, but only as a subdirectory /staging/
website.
Please stay tuned for an update and let us know if any suggestions --
Ok, clear, good to know. Thanks. Can we help somehow ?
@gabrielstuff Yes please feel free to make suggestions in this Issue or other Issues at anytime. You can also submit a Pull Request if you are confident in your suggestion but discussing things first is probably a better approach --
This Issue is rather irrelevant now, since staging/dev sites are working now and many previous bugs are fixed.
The reason for many of the errors seen in this Issue is because we previously had not implemented conditional checks into the various bash scripts like this example:
if [[ "$STAGING_SITE" == "true" ]]; then
chown -R www-data:wordpress /var/www/html/staging/wp-content/temp
chown -R www-data:wordpress /var/www/html/staging/wp-content/upgrade
chown www-data:wordpress /var/www/html/staging/wp-config.php
fi
Ref: https://github.com/littlebizzy/slickstack/blob/master/bash/ss-perms-wordpress-core.txt
We've since added these checks (if staging and/or dev site is enabled) into many different bash scripts so that certain snippets only run if either staging and/or dev sites have been specifically enabled in ss-config.
There might still be a few "if statements" missing, so feel free to comment below or create a new Issue.
Hello,
After a fresh install on Digital Ocean Ubuntu 20.04 LTS, I've got the following RED warnings :
I can't access to the dev and staging website, they always redirect me to the production site. Should I run something in prior to try
dev
orstaging
?