follow

#53 custom downloads

Reported by Jonas Obrist 2009-12-21

I propose following (alternative) way to optain a copy of XA:

1. The user go to the website and goes to the download page
2. The user chooses 'custom download' (or something similar)
3. The user chooses from additional modules to be selected other than xa-core
4. Now the user is shown a form (or a series of forms) to configure the modules selected
5. When all forms are filled in correctly the user is given a preconfigured zip package of XA with the values he chose and the additional modules.

In order for this to work modules probably have to provide information on how to configure. We can either do this from the website (xa-core team/modules developers can define configs etc using the admin panel) or some hidden files in the actual download package (for example a dotfile containing the information needed).

A possibility would be to make ini-style dotfile-configs in the modules:

[verbosity_of_something]
    type=int
    max=5
    min=1
    default=0
[enable_something]
    type=bool

Allowing certain types (int, str, choice, bool, ...) and also define additional information, such as defaults and ranges.

I think that having a GUI to configure XA would be very good. I remember MAP's config file which was HUGE. Not sure how big our configs are going to be, but making it easier for server owners can't be wrong, can it?

Attachments

Comments and changes

1. #1 Tom Morton

   written 2009-12-21

   • Changed version from 1.1.0.x to 1.2.0.x.

   I'm nit totally adverse to this idea. However I would sugges considering it a long term aim

   reasoning:

   firstly the primary distribution method of xa is with es releases. Downloads would be predominantly for updates - which are pretty impossible to configure in the way suggested

   in terms if choosing the modules to download. I suspect people will want it all anyway. As most is enabled by default and i'm not sure many turn them off

   with that said one possibilty is to make the two or three currently disabled modules that require config before u load them optional. So have the core package and let he downloaded choose and config the few options

   ultimately though it seems a lot of work for no gain

   I would suggest a more long term goal: which actually mattie has mentioned in the past. That is of creating and xa module to backup and manage configs from a website. This could build on the current gauth creator and extend it. We would use mercurial as a versioning system - the pure python verdsiom will work with es and django - to sync configs. Host things on the xa domain and provide interfaces to the config files etc

   this to me seems a much more rounded approach with more benefits for the work

   though I think we are looking at a long term aim with it maybe spring 2010? I'd be looking to release a new version of xa then as well.

   Thoihrs
2. #2 Tom Morton

   written 2009-12-21

   Ignore typos. I am on my phone
3. #3 Tom Morton

   written 2010-03-03

   • Changed status from new to wontfix.

   Website is now separate repo - will move issues over there

Verification: Please write the text from the image in the box (letters only)

Is that you, Humanoid? Is this me?

• Cancel