Configuration export

Get help from other users here.

Moderators: Developer, Contributor

Post Reply
Shinee
Posts: 6
Joined: 15 Mar 2012, 10:40

Configuration export

Post by Shinee »

Hi,

For some specific reason, I can't create a new projet on Mantis (used by 2 differents customers). I would like to install another mantis on my machine (which has already one). But I want to keep the current configuration, workflow...but on a new databse

I was thinking:
- Backup existing DB
- Restore DB has a new DB
- Copy / Paste current configuration with new folder name
- Change DB information connection on the new installation
- Set up the webserver

Do you see a problem with this ?

Thanks a lot.
istvanb
Posts: 226
Joined: 22 Aug 2010, 21:00

Re: Configuration export

Post by istvanb »

You can do that, once I had two different install on the same computer, with different DBs. Its gonna be damn confusing though, so it would be nice to know more about the specific reason you mentioned, to see if we can approach the problem from a different angle.
atrol
Site Admin
Posts: 8374
Joined: 26 Mar 2008, 21:37
Location: Germany

Re: Configuration export

Post by atrol »

I see no problems if the new installation will be a complete replacement of the old one.

If you are running both installations in parallel you will get problems if
a) you are storing your attachments on disk and
b) the new installation contains the same issues
Please use Search before posting and read the Manual
Shinee
Posts: 6
Joined: 15 Mar 2012, 10:40

Re: Configuration export

Post by Shinee »

It's not a remplacement installation, it's really a new one based on the first installation (workflow,...).

The reason is that I have 2 different customers, and I don't want them to have access to the same installation (database,...). But I really want to keep workflow we implement, configuration.

Thanks for your answers btw.
istvanb
Posts: 226
Joined: 22 Aug 2010, 21:00

Re: Configuration export

Post by istvanb »

Well... What would be the reason not having access to the same DB? I guess what you mean is not having access to the issues of the others. You dont need to have 2 installation to do that. You just have to set each project private, set the see private project threshold to updater or so, then assign your customers as updaters to their corresponding project.

Is this what you try to achieve?
Shinee
Posts: 6
Joined: 15 Mar 2012, 10:40

Re: Configuration export

Post by Shinee »

I don't want them to be on the same DB cause one of them (call him customer 1) will perhaps host this mantis in the future (web site and database). So I really don't want to have to clean the DB of the customer 2 data before sending it to customer 1.
istvanb
Posts: 226
Joined: 22 Aug 2010, 21:00

Re: Configuration export

Post by istvanb »

Oh, I see. It makes sense then.
Shinee
Posts: 6
Joined: 15 Mar 2012, 10:40

Re: Configuration export

Post by Shinee »

I notice strange files under the root folder. Names are like :
0d595b8af1c6ac6d7b503a25bd07801a
238db1a91b984468679a3e13ace0b1ab
bd371441bbce191a07877eadcaebd180
...
Dunno what it is. I think I have to clean the root folder of these.
atrol
Site Admin
Posts: 8374
Joined: 26 Mar 2008, 21:37
Location: Germany

Re: Configuration export

Post by atrol »

Shinee wrote:I notice strange files under the root folder. Names are like :
0d595b8af1c6ac6d7b503a25bd07801a
238db1a91b984468679a3e13ace0b1ab
This files are attachments of issues
Please use Search before posting and read the Manual
Shinee
Posts: 6
Joined: 15 Mar 2012, 10:40

Re: Configuration export

Post by Shinee »

Thank you for the explanation.
Post Reply