Closed
Bug 232912
Opened 22 years ago
Closed 19 years ago
Bugzilla demo installation on landfill
Categories
(Bugzilla :: Bugzilla-General, enhancement)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: gerv, Assigned: gerv)
Details
As outlined on the mailing list, we need an http://landfill.bugzilla.org/demo
(or, better yet, a http://demo.bugzilla.org). This would have the following
properties:
- Runs CVS tip (like bugzilla-tip)
- Has all features turned on
- Has working collectstats.pl
- Has a small number of products and components
- Has fixed database of about 50 bugs in a variety of configurations
- Database gets reset to original at midnight every day
This would:
- Show off all of Bugzilla's features
- Allow people to play to their heart's content without being worried about
breaking anything
- Give us a stable set of bugs to write about in the documentation.
Gerv
Assignee | ||
Comment 1•22 years ago
|
||
So how do we get there from here? We need to:
- Set up a new Bugzilla on landfill
- Set up a system where the database gets reset to a known database file every
night.
Once this is done, people can spend time adding to the database and, if they are
happy, backing it up to that file, thereby "saving" their work. This way, we can
build up the products, components, bugs and features incrementally.
So setting up a new Bugzilla on landfill isn't that hard - it's the database
reset mechanism which is the slightly tricky bit. Myk, justdave: can either of
you help here? I can probably do or organise most of the rest.
Oh, an obvious thought about collectstats.pl - we may have to fake the data or
something, because obviously if the database keeps getting reset then we're
never going to generate any new data.
Gerv
Comment 2•22 years ago
|
||
bugzilla-tip on landfill already has all features enabled (or it's supposed to
anyway).
We also have bugzilla-stable and bugzilla-devel which are 2.16.4 and 2.17.6
respectively at the moment, both of which should also have all features enabled.
I would recommend setting up both of those as the demo installs. Basically what
needs to happen is the database reset. We have database cloning command-line
tools already on landfill, so this should be pretty easy. We just need to
decide on a name for a backup database, and clone the in-use one to the backup
name. Then we set up a cron job to drop the original and re-clone it from the
backup once a week (or whatever).
Assignee | ||
Comment 3•21 years ago
|
||
Dave: the question is, should the demo database be based on the current one, or
on a new one created specially? It's easier to use the current one, but a new
one would be cleaner.
Also, the "reset every week" thing is going to play havoc with the charting...
Maybe we should just turn all features on, on bugzilla-stable and bugzilla-devel
and leave it at that?
Gerv
Assignee | ||
Updated•21 years ago
|
Severity: normal → enhancement
Comment 4•21 years ago
|
||
From an email I wrote while looking at old emails:
-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==-
Just going through some old mails and was wondering if this ever went anywhere?
Being that this would be a test installation, it may be acceptable to have some
kind of a "promote me to admin" link so that prospective users can get a look at
the admin interfaces, too. We may also wish to do resets more often if we allow
people to change install options.
If we wanted to go one step further, we could make
http://landfill.bugzilla.org/demo/tip and http://landfill.bugzilla.org/demo/2.18
(etc). On the stable installs, we could put any/all available localized
templates along with the appropriate setting in editparams.cgi.
If we wanted to provide the ability for somebody to try out the admin interface
but didn't wanna promote them in this existing install, we could provide a link
for "create a new install with me as the admin." This install could be flagged
for deletion in one week.
In all these instances, it would be nice if the header said somewhere in it when
the reset/deletion will occur. "This install is scheduled for (reset|deletion)
in 3 days. These scripts would mostly be landfill specific things and would
require little to no modifications of the Bugzilla codebase.
Assignee | ||
Comment 5•21 years ago
|
||
We can't make any old person an admin - the admin interface isn't nearly as
secure as the public interface. I also think creating new installs based on web
commands would be fraught with problems, not least the possibility of DOS.
I think we should walk before we can run, and try and create a stable and tip
demo install, automatically updated, with everything turned on, and a baseline
set of interesting bugs, with a database reset once a week.
We have most of the infrastructure for this on landfill already - it just needs
someone with admin rights there to write and test the appropriate scripts.
Gerv
Comment 6•21 years ago
|
||
with the exception of the scripts to create and destroy installs, everyone with
a shell account on landfill has access to do any of the rest. The commands to
drop and clone databases with the permissions of the bugs user are accessible to
everyone in the shell.
Updated•19 years ago
|
QA Contact: mattyt-bugzilla → default-qa
![]() |
||
Comment 7•19 years ago
|
||
I see no interest in this bug. We can alread build our own installation on landfill and turn parameters on/off as you like. -> WONTFIX
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•