Brett
|
| Posted: 09/05/2002, 6:41 AM |
|
Being very new to CCS, I'm reluctant to make changes to my live site without thorough testing (a good idea for anyone, right?). With my hosting setup, I can use either an entirely different database, or just different table names. I think I could just set up a new connection, but I want to keep a clean version if I need to go back, which means copying the project (I see rename, but not copy on the menu). I happen to use MSAccess for design, and PHP/MySQL/Apache/FreeBSD for the published site. Any tips?
I think this would be a great topic for a tutorial, don't you? Also, wouldn't it be great if CCS kept track of your database changes (or offered a "compare" feature) so it would generate the necessary SQL code to apply?
|
|
|
 |
Yo
|
| Posted: 09/27/2002, 10:48 AM |
|
Did you find an easy way to keep a working site..Im fed up screwing up my good site and keeping on starting from scratch
|
|
|
|
Steve
|
| Posted: 09/28/2002, 10:02 PM |
|
I am using a sub-directory off a test domain I have for live on the internet testing and a development site on PWS on my computer for dev/testing before going to the test site that is on the web. In particualar, the test site on the web has all the components on it installed that I use (Upload Components, Image Maipulation Components, Mail Components).
I have found a couple of issues. For Security (the Login Page), On the Project Settings - Security Tab - Convert Login Page URL to: I had to chage it from absolute to None. Using none - the login page must be in the same directory as the other pages that use it for the re-direct to the login page to work corectly. If absolute is used it will go to a login page that is located at the Server URL that is specified on the Project Settings - Publishing Tab.
As for version control, I am copying the subdirectory to another subdirect to preserve the couurent version when published live. For Example Subdir is Proj - When it goes live - Copy to Proj v1.0 sub dir. When changes occure, copy Proj to Proj v1.1, etc.... I also put a copy of the database with it as well.
Another issue you might hit is the connection string. Since I hhave the same project for different domains (clients) and the domains are on the same server so I can't use a DSN connection. Each website uses the same named database but located in a differnt directory. This means the connection is based on the MapPath. The problem with CCS is that the conection string can't be used in the connection wizard. It could in CC v2.0 but not in CCS. To do something like that, you'll need to modify the generated code in the Common file. Not a great thing to do but until Code Charge addresses it, then that is the work around.
As far as Code Charge tracking the Database changes - Given the multi databas types and languages supported, Tracking Database changes is way out of scope for CCS. CCS, being a v1.x.x realease is to imature at this point to address that. CCS needs to address other issues, in particualr documentation, which even you mentioned.
I am kinda surprised you are developing hitting one database and going to production with another. This will create a higher risk factor on having problems with the production environemnt and not the dev/test environment. Problems that won't be detected until it goes live.
|
|
|
|
Dennis
|
| Posted: 09/29/2002, 8:38 AM |
|
This is a VERY interesting topic.. and I think there is room for improvement here from the CCS code team! I have in the past used NetObjects Fusion for development and maintenance. NetObjects allows you to set up different server destinations for your code. So you can publish your test code to one location and when ready publish it into a different production location. This is very handy also if you use the same code on several different sites(we all know each site is generated from completely "new" code  ). Having only one publish location makes it very difficult with CCS.
|
|
|
|
|
