StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHow to implement module installation and uninstallation using Zend Framework
primarykey
Id
4704999
data
AcceptedAnswerId
4744707
AnswerCount
2
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2011-01-16T11:20:44.893
FavoriteCount
6
LastActivityDate
2011-01-25T04:26:56.130
LastEditDate
LastEditorUserId
0
OwnerUserId
357448
ParentId
0
PostTypeId
1
Score
4
ViewCount
724
LastEditorDisplayName
text
Body
I have a webapplication built using Zend Framework that contains a lot of modules. These modules are all "optional" and are used to make extended functionality avalible. Some of these modules write their own logs etc. I was thinking about how to implement installation and uninstallation behvaiour for these modules. At first my idea was to let every module have a <code>InstallationController</code>, <code>UninstallController</code> etc and have these handle the installation. But then I started thinking about an approach that would involve letting each module contain <code>install.ini</code>, <code>uninstall.ini</code> etc. Then the core has functionality to pare and act upon these. An example of an <code>uninstall.ini</code> for the module <code>foo</code> file could be <pre><code>[save_logs] folder.remove.data.foo folder.remove.modules.foo file.remove.configs.foo [complete : save_logs] file.remove.logs.foo db.table.truncate.foo_table1 db.table.truncate.foo_table2 </code></pre> Then the user would be presented with the options of <code>Complete</code> or <code>Save Logs</code> while running the uninstallation of the <code>foo</code> module. One of the upsides I can see with this approach is a common core mechanic that handles all the operations and the fact that no code actually part of the <code>foo</code> module would be running during the uninstallation. I have never done this type of installation/uninstallation/update support on a webapp before so any ideas and tips would be nice.
Tags
<zend-framework><module><install><uninstall>
Title
How to implement module installation and uninstallation using Zend Framework
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USinquam
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POHow to implement module installation and uninstallation using Zend Framework
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POHow to implement module installation and uninstallation using Zend Framework
 UserUserId
 USmarkus
 VoteTypeVoteTypeId
 VTFavorite
3. VO
 singulars
 PostPostId
 POHow to implement module installation and uninstallation using Zend Framework
 UserUserId
 UStawfekov
 VoteTypeVoteTypeId
 VTFavorite
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.