I tried out the cvs version 1.1.2.4 with the dba module from http://drupal.org/node/132753
It gives some errors, but that is not (yet) what I want to report.

I have some reguests and feedbacks:

1:
I think the dba module generates the sql file, In dba I have mail switched on, when I use demo I have the demo sql also in my mailbox. It would be nice to have the choice of mail in the demo settings

2:
The dump path of dba is for security reasons not accesible to the web. There is a note in demo about this. The standard dump path of demo is inside drupal: map files????

3:
I use multisite. In the file map I have the sites in different maps: file/site1/demo file/site2/demo. The settings are made in Drupal files system path. In my opinion the multi site option is not useful. It gives me: file/site#/demo/domainname/. An absolute path (like dba) is good.

4:
Why is the drupal module necessary in demo? I do not use it, it's only switched on.

5:
In status the default snapshot has no date and time only the name, would be nice the have it, like available snapshots in reset site.

Thank you for developing this great module. Like the name said, I want to use it in a demo site.

Regards
Martin

Comments

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Assigned: Unassigned » sun

Answers to your issues:

  1. Demo was not designed to mail a backup of your database. To do that, you can use the built-in functionality of dba.module.
  2. You do not have to link files to another location in your filesystem. Just enter a relative or absolute path into the Dump path field.
  3. Having different file paths in a multi-site installation is a custom setting. I assume that most people are using the same files-path for each site in a multi-site installation. Because of that, Demo appends the site's name to the Dump path.
  4. As per project description Demo has been designed to quickly setup a demonstration site for Drupal modules. When Demo is installed, the drupal.module is enabled and automatically configured to allow users of drupal.org to login with their accounts. If you are using Demo for a local development/test installation, don't let it trouble you. DNS will not allow external access in most cases. And even if your Demo site is publicly accessible, you have to setup access permissions for authenticated users first, to let them have access to certain functionality.
  5. Please update to the latest development snapshot. It contains amazing updates.
sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Category: feature » task
Status: Active » Fixed

Some updates:

2. The directory where dumps are stored is protected by a .htaccess file. No files are downloadable. So there should not be any worries about this. If other modules (f.e. web file managers) are not respecting .htaccess files, it's their fault.

4. Dependency on drupal.module and creation of demo users has been completely removed.

5. If you haven't already, please update to the latest version.

Feel free to post a new issue with more feedback on the latest version! :)

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)