I'm trying to come up with a safe site development strategy. Here's what I've done so far:
1. I have my actual Mambo website (say, mysite.com) installed on the public_html/, and the SMF in public_html/smf.
2. I created an identical site on a subdomain like admin.mysite.com, which places the Mambo installation in the public_html/admin/, and the SMF in public_html/smf/.
The idea is to do all my modification and testing privately in the nonpublic /admin site, and when I'm satisfied that the changes are working properly, apply them to the main site.
But if something goes amiss, how about reversion to an earlier stage? How about this:
1. Copy periodically, say, public_html/admin to my backup folder, calling the folders admin20050710 and admin20050712 and admin20050714, etc. 2. In the event of a serious problem introduced by programming changes... 3. Delete public_html/admin. 4. Copy admin20050714 to public_html/ as public_html/admin20050714. 5. Rename public_html/admin20050714 to public_html/admin.
Could there be any hidden gotchas with a Mambo-SMF integration which might keep this from working? Presumably it would connect to the database just fine?
A single login box on the Mambo page--i.e., none on the SMF.
I've read a LOT of posts about logon and password issues. But I can't infer whether what I want to do--have SMF display as a FEATURE only within my Mambo site with no logon of its own--is possible.
If the above is possible, how do I remove the SMF login box?
Provide for administration?
Prevent someone from entering a URL like www.mysite.com/smf and bringing up the SMF outside the Mambo environment?
None of the text or images in this public website may be copied without the expressed written consent of the authors. Copyright 2005 by MamboHacks.com. Powered by Mambo. All rights reserved. TERMS OF USE
Show Posts
