Database creation documentation #220
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
No milestone
No project
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#220
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Document the two methods (same volume, image and separate) of creating/adding databases to docker. Should be added to this page.
Related Issue: #141
I believe the issue has been slightly misunderstood.
The current wiki works quite well as a implementation notes and step-by-step guide. however for this issue the purpose is to document the two valid approaches to creating a new database discovered in the related issue #141
Therefore the page should focus on explaining the two supported methods and describing the differences and trade-offs between. Which should help the developers understand which approach they are using and why.
The operational details specified in the wiki belong and are useful but might not be accurate for this specific wiki page but might be better to have in a separate how-to wiki page. Which can then be referenced from here for the actual implementation details.
If confused could look at xUnit wiki page and se how it works and references to the unit testing wiki page.
Database creation documenataionto Database creation documentationI believe the page is now much closer to the intent of the issue and no longer reads like a setup guide . The structure is good and the flow is easy to understand and us developers can now understand the differences between the two methods and their strengths / weaknesses.
Overall the wiki looks good and it communicates the intent of the issue much more clearly now, Therefore I believe that its done and no further changes need to be made.
The link from this page to the how-to page is good and appropriate and it helps by complementing each other.
I think this issue is still in the works.
Right now we have sesnors, general and users databases
There is an investigation issue on separated database. I close this issue