Opened 15 years ago
Last modified 15 years ago
#129 closed defect (FIXED)
organize admin/development scripts
| Reported by: | Will Kahn-Greene | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.0.4 |
| Component: | Keywords: | ||
| Cc: | Parent Tickets: |
Description
There are a few scripts that are in the repository now and probably more to come. We should reorganize them so they get "installed" when using builtout and setup.py install. Also, they should follow a similar structure and have header information.
Maybe it's interesting to create a gmg command that has a series of sub commands like PyBlosxom and git both have.
Regardless, the following things should be done:
- administration/management scripts should be collected and put in a centralized place
- they should be tweaked so they follow the same conventions (which means we should create a set of conventions for scripts)
- we should fix the install process to "install" these scripts as well
It's probably worth doing this for 0.0.4, but it's something someone can think about towards the end of the 0.0.4 cycle.
Note:
See TracTickets
for help on using tickets.
First off, there is a gmg command with sub commands. I moved destroy_environment over to use that (this is covered in bug #296).
Second, we have a bunch of bash scripts for doing things. We can at some point move those to a scripts/ directory, but that might get confusing given that after running bootstrap.py, you end up with a bin/ directory. Which is which? Why are there things in one place and not the other?
Anyhow, other than bash scripts, this is totally covered and should be marked closed.