[GH-ISSUE #55] How do we version design documents for each app version. #1049

Open
opened 2026-04-29 22:01:15 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @jofomah on GitHub (Jun 24, 2015).
Original GitHub issue: https://github.com/jo/couchdb-best-practices/issues/55

for instance, if i have an app version whose design documents are different from subsequent version, what is the best way to version this.

Originally created by @jofomah on GitHub (Jun 24, 2015). Original GitHub issue: https://github.com/jo/couchdb-best-practices/issues/55 for instance, if i have an app version whose design documents are different from subsequent version, what is the best way to version this.
Author
Owner

@jo commented on GitHub (Jul 6, 2015):

You can include a version as part of the document ID, eg. _design/app-1.0

<!-- gh-comment-id:118772891 --> @jo commented on GitHub (Jul 6, 2015): You can include a version as part of the document ID, eg. `_design/app-1.0`
gitea-mirror changed title from [GH-ISSUE #55] How do we version design documents for each app version. to [GH-ISSUE #55] How do we version design documents for each app version. 2026-04-30 22:01:25 -06:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/couchdb-best-practices#1049
No description provided.