Hi - Is it possible to have a set up - where you have UBBT installed on your local machine, as a stand-alone setup, for the purpose of testing new code or changes to code, as a stepping stone before finally deciding to upload your deltas to the production server.
Naz.
_________________________
Naz. [The world is big enough for everyone - so be HAPPY ]
Express Hosting
"We are the official hosting company of UBB.threads. Ask us about our free migration services to migrate your UBB.threads installation."
#215148 - 07/04/0803:59 PMRe: UBBT test server on local Machine
[Re: Naz]
from what i've seen, you are much better off to run ubbt on a Linux box for the live site.
this is expecially the case for large DBs. and by large, i really mean HUGE
for development however, loading up WAMP (takes 10mins and you are running) on a windows box is so easy, that it doesn't make sense to have a Linux box to play around with stuff.
now, if you truly LOVE linux and have a home system with that installed.. by all means go for it!
the only pain in the arse for development is Imagemagick. I just ignore that feature on my development environment and use GD2.
Sorry to dig this post up but it answers 90% of my questions and the remaining 10% is on topic...
Anyway, as far as creating a dev environment for the typical LAMP environment goes: Has anyone written up a "best practices" type of checklist to making a copy of the environment on other hardware? Eg: Is it better to go the backup/restore route for the db? I'm quite new to mysql, but every other rdbms I've used doesn't easily allow for cross-platform dump/loads - or at least there is some "catch" to the process.
The rest seems somewhat trivial - moving/altering the apache config and the ubb directory with the php pages.
Registered: 06/05/06
Posts: 14995
Loc: Portland, OR; USA
Well, when I test i just test with dummy data; but easiest thing to do to work off of board data would be to just follow a backup/restore procedure and just point your config files on the local server to the proper information to connect to its local db...
Sorry to dig this post up but it answers 90% of my questions and the remaining 10% is on topic...
Anyway, as far as creating a dev environment for the typical LAMP environment goes: Has anyone written up a "best practices" type of checklist to making a copy of the environment on other hardware? Eg: Is it better to go the backup/restore route for the db? I'm quite new to mysql, but every other rdbms I've used doesn't easily allow for cross-platform dump/loads - or at least there is some "catch" to the process.
The rest seems somewhat trivial - moving/altering the apache config and the ubb directory with the php pages.
the only thing i always watch out for is the main difference in mysql on Windows vs Linux systems as regards table names. Out of the box, mysql on windows makes all the table names lower case. Linux preserves case.
since ubbt uses upper case in the table names, it can be a gotcha. so i always edit my 'my.cnf' file on the windows box (even if it's running WAMP) to NOT change table names to lower case. that way compatibility is maintained.