RE: [Mantisbt-dev] Mantis Installer / Customization / CVS Problems

[Robert F. <rf...@mo...>]

Sounds good, as far as the upgrade path goes, all we'd need to do is
install over the top of the old copy, check for a variable (say,
$installed_version) in a locally created file (i.e., created when the
original install was performed) that may contain, for example, the
current installed version, and if the contents don't match a variable in
the system (say, current version), then we do the upgrade path, which
could be derived from the current upgrade scripts (if applicable).
Of course, if the $installed_version variable doesn't exist, we could
assume a new installation.

On top of that, if we are on the upgrade path, we could simply pick up
the current config. Items, and have the user review them.

Rob.

-----Original Message-----
From: man...@li...
[mailto:man...@li...] On Behalf Of
Christopher Shaffer
Sent: Friday, 17 January 2003 1:02 AM
To: man...@li...
Subject: [Mantisbt-dev] Mantis Installer / Customization / CVS Problems



Julian (et al),

What I was trying to do was add custom values to the following fields:
project status, priority, severity, reproducibility, status, resolution,
projection, and eta.  I found a way to do it, having all values stored
in a database table.  When the global variables are initialized in
config_inc1.php, I pull the values from the table, and build the
value/string pairs.  I then had to fix get_enum_element() to always
return the original value instead of looking in the language construct
(my company operates in english...).  I would think that complete field
customization would be a great thing, although, I have no idea how you
could implement it on a multi-language level...


> Note that 0.18 will likely include custom field support (it's in CVS 
> but
> you need to enable a config option and add a DB table to use it).
This 
> allows you to add your own fields to arbitrary projects.  Again, this 
> might help you in some way.  If you want to give any more details I 
> might be able to suggest something for you.

I'd love to look at the code in CVS, but it seems to be down at the
moment :(.  Hopefully, SF will have it back up soon...

> I don't know anything about the PostNuke installer so I can't really 
> say :)
> 
> I don't think our install process is hugely complicated but I can see
> some benefit to having things automated a bit.  Can you describe how
you 
> would see an installer working?  What would you give it, what would it

> look up, what would it do, etc...

Since others have explained how the PN installer works, I'll just
describe what I was working towards.  (Installing Mantis is by no means
difficult!  But having a web-based installer really does give systems a
level of polish/professionalism.  )  In this description, the 'user' is
defined as the person installing Mantis, and 'installer' refers to the
installation scripts.

I'm thinking of a multi-step system.  Since I have no idea how the
upgrade system works, I'm leaving that out, for now.  (when I figure
that out, I'll add it in.)

Step 1:  Greeting.  Description of Mantis.  What the installer is going
to do.  Tell what information the user will be required to provide.

Step 2:  Licence agreement              (GNU Public License, right?)

Step 3:  New Install or Upgrade?        (for now, assume only path is
'New Install')

Step 4:  Request Database information (DB server, db username, db
password, database name.  Do you want to create the database?)

Step 5:  First, test db connection, if failed, back to step 4, else:
         Create database if desired, then execute sql statement.
         
         Ask user for administrator account information (username,
email, password)
         
Step 6:  Add admin user to database.
         Provide user with options for site-wide configuration (emails,
server settings, path
names...)
         
Step 7:  Write initial config file.
         Create first project? (if yes, activate project fields (Name,
status, view status, upload path, description)

Step 8:  If create first project was selected, build project.
         Conclusion screen.  Provide admin login info, and link to
login_page.php
         
FINISHED!!!!

Okay, just my thoughts.  What do you guys think?  Any suggestions.  This
way, the install doc is as simple as "Copy Mantis to a public directory,
go to your web browser, and go to
"http://www.myhost.com/path/to/mantis/install.php", and follow the
onscreen directions.

Chris Shaffer

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com
Understand how to protect your customers personal information by
implementing SSL on your Apache Web Server. Click here to get our FREE
Thawte Apache 
Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en
_______________________________________________
Mantisbt-dev mailing list
Man...@li...
https://lists.sourceforge.net/lists/listinfo/mantisbt-dev