-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Staging workflow #398
Comments
For my own website I simply restrict access to the stage version to logged in users (in system settings), so the website can not be crawled. Maybe someone else has a good workflow for transferring files, would love to find a solution for that, too... |
How do you transfer the updated content to the live version? |
FTP. I use that workflow only in rare cases when I refactor my whole content. For general editing, the visual mode is enough for me, all the formatting is there. You probably use the raw mode and you want to preview a page in your theme-design before you publish changes? |
Yes, I would like to see the edits with my theme. For example, I want to see if images are placed correctly. |
I don't edit my site on the live server because I can't preview my edits before publishing.
Currently, I do everything on a locals server, but that does not work on the go.
So I thought I could use a second installation of Typemill for staging, maybe on a subdomain. When everything is fine, then all changes should be transferred to the live version.
Does anybody know a a simple tool/script for this. And how to make the staging system not be indexed by Google? I can't configure the staging system differently or add noindex stuff to the theme as that would be transferred to the live system. Will http auth be a good choice?
The text was updated successfully, but these errors were encountered: