StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POImproving our dev environment at work
primarykey
Id
438530
data
AcceptedAnswerId
438637
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-01-13T10:21:23.933
FavoriteCount
4
LastActivityDate
2009-01-13T11:07:50.410
LastEditDate
2017-05-23T12:09:11.293
LastEditorUserId
-1
OwnerUserId
28144
ParentId
0
PostTypeId
1
Score
8
ViewCount
553
LastEditorDisplayName
text
Body
In the near future i will get some 2 weeks for moving and improving our development environment at work. We mainly develop one large PHP/MySQL project with 2-10 developers. At the moment we have one dev server, running apache with mod_userdir, each dev has a /public_html folder in his (samba-accessible) home. For VCS and Project Management/Issuetracking we use Subversion and Trac. Testing/Deployment takes some manual steps, not much automation there. My plans for the new setup include the following changes to the existing stuff: <ul> <li>Continuous Integration</li> <li>Integrate CI to Trac, create/find a plugin which offers to start actions after success or failure of the build progress (i.e. deploy to staging/live)</li> <li>Create automated deployment-scripts (one-click)</li> <li>Integrate (<a href="http://www.stack.nl/~dimitri/doxygen/" rel="nofollow noreferrer">Doxygen</a>)-Documentation into the build-progress and somehow into Trac</li> <li>Add <a href="https://stackoverflow.com/questions/438398/subversion-as-version-incrementor-at-each-commit">automatic versioning</a></li> <li>Add another layer of monitoring (local nagios monitoring our production-system-nagios)</li> <li>Add a nightly running MySQL Replication Slave, which can then by the developers be used to test stuff on up2date data</li> <li>Review the backup plans</li> <li>Document how and why I set everything up in this way</li> </ul> Do you have any tipps/hints what can be improved further? Anything we should do in a different way?
Tags
<svn><deployment><automation><trac><environment>
Title
Improving our dev environment at work
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USKarsten
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
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
 POImproving our dev environment at work
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POImproving our dev environment at work
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POImproving our dev environment at work
 UserUserId
 USAdriano Varoli Piazza
 VoteTypeVoteTypeId
 VTFavorite
CommentsPostId
1. This table or related slice is empty.

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.