Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dev / Prod database, publishing forms, and versioning #327

Closed
disperse opened this issue Nov 19, 2020 · 1 comment
Closed

Dev / Prod database, publishing forms, and versioning #327

disperse opened this issue Nov 19, 2020 · 1 comment

Comments

@disperse
Copy link
Contributor

Allows for connecting data to immutable forms, publishing forms from dev to prod makes a copy and editing forms on prod will no longer be possible.

@wyattis
Copy link
Member

wyattis commented Mar 8, 2021

If DB switching (#357) seems unreasonable to implement, then isolating studies (#358) can help achieve the goal of having separate prod and test environments without requiring duplication and synchronization of multiple databases. One study can be used exclusively for testing and another for collecting production data.

Study isolation only solves part of the current issue with developing and testing forms. To fully deal with existing form issues we need to implement form versioning. This approach should also include a feature to make it trivial to copy forms across studies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants