Develop PW site on a website running other CMS

[theo]

Hello

This is probably a FAQ, but I could not find anything

I have an existing Website using Typo3.
I would like to develop a newly designed website with PW on the same web root.
Which is the best way to do this?

Typo3 has an index.php in web root.

How can I keep running the old website until the new one (PW) is ready and tested?

Do I have to use a subfolder or can I test it on the final destination (root)?

Thank you and sorry for my English.
 

[flydev]

Hello and welcome theo.

I think that your best bet would be a subdirectory. You create your directory, upload processwire and the important step to get it working is to modify your .htaccess.

What the documention say about that :

If you installed ProcessWire in an subdir you have to adjust the RewriteBase to it. So for example if your installation lays in a folder called "pw" (your URL woud look like "http://yoursite.com/pw/") your RewriteBase should look like the following:

RewriteBase /pw/

More info there :  https://processwire.com/docs/tutorials/troubleshooting-guide/page3

[szabesz]

Some general/security related info about this topic can be found here: https://processwire.com/docs/security/other-software/

EDIT: I also recommend using a subdomain for the staging site. Not just for security reasons but generally this is the "cleanest way" to separate the two.

[theo]

Hello flydev


Thank you.


But this means, that the website will still run under http://yoursite.com/pw/ when it's ready. Right?

If I move the installation to webroot later, the media URLs will be wrong. Is it true?

This is not actually what I was looking for.
 

Thanks.

----------------------------------------------------

Hello szabesz

Some general/security related info about this topic can be found here: https://processwire.com/docs/security/other-software/

EDIT: I also recommend using a subdomain for the staging site. Not just for security reasons but generally this is the "cleanest way "to separate the two.

This is not a problem. Typo3 will be removed when PW is ready.

Thank you.

[szabesz]

"...media URLs will be wrong..."

ProcessWire can take care of it if you "set things up properly", but I have just said in my edited post above, if you use a subdomain, there will be no need to keep an eye on URIs/URLs, migrating should work without this sort of issue.

[flydev]

If I move the installation to webroot later, the media URLs will be wrong. Is it true?

As szabesz said, everything will work.  Until you do not hardcode your urls but use the API, all good.

[theo]

Oh, yes. I overlooked the "subdomain".  That would have been my next idea, and probably the best.

Thank you all.

[dragan]

PW uses relative paths and URLs. You can freely move things around however you wish (unlike, say, Wordpress...)

Internal links (e.g. via WYSIWYG editor) will not break.

As already mentioned, just make sure you use PW API vars like $config->httpHost / $config->urls->root / $config->urls->assets properly. And maybe add all possible domains in config.php from the beginning:

$config->httpHosts = array('localhost', 'sub.domain.com', 'domain.com');

[theo]

PW uses relative paths and URLs. You can freely move things around however you wish (unlike, say, Wordpress...)

Internal links (e.g. via WYSIWYG editor) will not break.

As already mentioned, just make sure you use PW API vars like $config->httpHost / $config->urls->root / $config->urls->assets properly. And maybe add all possible domains in config.php from the beginning:

$config->httpHosts = array('localhost', 'sub.domain.com', 'domain.com');

Thank you.

I have set up a subdomain in the meantime.

I have to add all (later) possible domains to  $config->httpHosts in this case too, right?

Can you explain why this is necessary?