coppermine not able to be installed on local webserver first ?

[GH]

I wonder why it should be that, unless other web software,  it is not recommended to install and transfer later coppermine to the remote server domain.

If this is true, I cannot accept that this is du to the great complexity of any "self-hosting" issue, because this issue is very well resolved by nearly all software I knew very well as "Data Becker web-to-date" or "4imagesGallery". But may be, that they have all less features than  coppermine. (Of course, if I use minicms plugin and there is no possbility with the fckeditor to place relativ adresses, it can't work.)
I ask myself, where is the instruction to do it well with coppermine too or what is the misunderstanding in this case? Or, if that is really an option not token in developpement of coppermine.

Why I ask this?
Simply, because it could be so easy to prepare one master of coppermine for one domain, and later form this master to make a variant for another domain. And also, because the free hosting services are not very powerful, compared to the quickness of a localhost installation with apache server, to try something. And later, may be that you have another domain adress when succesfully tested, but you must change every link.

[Nibbler]

I don't understand the problem. There is no reason why you can't install or test Coppermine locally and then upload it to your main webserver.

[Joachim Müller]

As Nibbler suggested, you're welcome to set up coppermine locally and prepare it. All we say is that we do not recommend self-hosting, i.e. making the local install publicly available on the internet. The reason for this recommendation is security issues: we're convinced that a server that is available on the internet should be operated by pros and should be monitored 24 hours a day. Just setting up a web server locally and not allowing internet access is totally OK. In fact, it's what most developers do. We even have a package "Coppermine Live Demo" that is meant for exactly this purpose.
The only drawback of setting up your test server locally is the fact that others can't help you with your issues if you ask for support. This being said, you'll have to figure out all issues on your own when setting up coppermine on a local testbed. That's all.

[GH]

ok, thank you for this confirmation.
But that is what I did, prepare on apache webserver locally and than load up to the local host.

May be there was a misunderstanding for the nomination "self-hosting" in the answer to my topic. The issue was, that once loaded up, I could not acces to the remote side because after calling it appeared for a very short moment the original side but did not stay,  and then there was a kind of redirection to the localhost/....., the direction where I prepared the coppermine initially. But I did not enter any kind of redirection code. May be that in minicms there stayed to much absolute adresses with the localhost adress (for text links and images) and this were used not normally...., but in the modified theme.php where I have a menu with relative adresses, there were not for sure.
I cannot explain it better, a strange experience.

[Nibbler]

The only place Coppermine stores the URL is in config. You need to change that after you upload.

[GH]

a partial succes now:  transfer of coppermine from one site remote to another site with succes, but the manually introduced relative link adresse are no more good, there comes other minicms textes.

It is to suppose, that the changement of host place is not correctly made from minicms. I'll give this information also to donnavon to see if that is true or not.
Thanks all.

[Joachim Müller]

MiniCMS is not part of coppermine. Stop refering to it - it goes unsupported here. Of course you have to fix your custom links that you deliberately introduced. That's none of our business.