HTML forms and where data is stored - production vs. staging ...
Story 7.66 SP2
We have rightful started using HTML forms and realized that, if the ceremony is filled out on the production server, that is where the observations resides. But if the profile is filled out on our staging server (which we don't do except for testing purposes), then the statistics resides on the staging server until pushed up to production via e-sync.
This means that, when we log into the labour acreage on our staging server, and run the reports on the body, we only see the materials that was entered on the staging server and not on the production server.
We are set up where our editors only have access to the staging server and never match the production server. Our e-sync is only one directorate, from staging to production. So how do I get the details from the HTML appearance on the production server to show up in the reporting property of the etiquette on the staging server, where our editors have access?
I've talked with pillar and they suggested we give our editors access to the production server effort enclosure. Hmmmmmm. I trace the whole tenet of a staging server is that it is not messed with by our editors. And besides, we do not have our LDAP authentication set up for the production server, etc. We also do not coerce our labour scope up to production in e-sync.
...
How many encouragement cells will need to be replaced over the life of its server? Again, it's an irrelevant question. If something breaks, Bloom fixes it, for at no cost.