More glanceable breakdown of pros and cons of self-hosting
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
Start with the existing hosting considerations section at docs.getodk.org/security/#hosting-considerations and the DigitalOcean installation page mentioned in the issue. Determine whether the proposed comparison belongs in the documentation or website, then identify the relevant setup pages and define completion as a clear, upfront breakdown of self-hosting pros and cons across them.
Written by the indexing model from the issue text.
Description
It would be great to include this disclaimer on all the set-up pages (I am thinking the DigitalOcean installation page for example). For older users like myself, who installed ODK before ODK Cloud was an option, it would be great to have that disclaimer front and center, so we can make informed decisions about web-hosting in the future.
-- User feedback.
Not sure if this should live in the docs or on the website, but something like https://docs.getodk.org/security/#hosting-considerations or https://ghost.org/docs/hosting/#ghostpro-vs-self-hosting would be great to have up-front.
- Dominant language
- Python
- Stars
- 58
- Forks
- 161
- Avg merge
- 20h 51m
- Merged PRs (30d)
- 2
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getodk/docs
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
Central Collect
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Make it explicit that an S3 bucket configured for use with Central must accept abitrary connectionsOpenCentral
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
area:cli area:security enhancement priority:medium size:small
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
RonaldHensbergen/composable-data-stack#1338 ·
Maintainers usually reply within 1 day
-
area:stdlib effort:S impact:med platform:linux type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
automated endpoint-dead needs-curation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
almanac-data/climate-almanac#139 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
UKGovernmentBEIS/inspect_ai#6695 · 1 comment ·
Maintainers usually reply within 1 day