1313237 - Create a read-only version of Kuma.

Status: RESOLVED FIXED

(developer.mozilla.org Graveyard :: Setup / Install, enhancement)

Description

[Ryan Johnson (:rjohnson)]

What problem would this feature solve?
======================================
For example, a read-only version of Kuma could be deployed as a fallback or backup when bringing the full-featured Kuma down for maintenance.

Who has this problem?
=====================
Staff contributors to MDN

How do you know that the users identified above have this problem?
==================================================================
Currently user experience downtime when Kuma is down for maintenance.

How are the users identified above solving this problem now?
============================================================
There is no current backup during downtime.

Do you have any suggestions for solving the problem? Please explain in detail.
==============================================================================
This effort.

Is there anything else we should know?
======================================
No.

Comment 1

[John Whitlock [:jwhitlock]]

Created a spec for this at:

https://docs.google.com/document/d/1-AcCNxUrSAX1srzYx3Lbz2Tg-3pAEkDZFBdhnUg2APk/edit#heading=h.ohsptigqtlv7

I think jpetto / shobson has a list of front-end changes that would be needed for read-only mode.

Comment 2

[Ryan Johnson (:rjohnson)]

See https://github.com/mozilla/kuma/pull/4150

Comment 3

[Ryan Johnson (:rjohnson)]

For the record (I actually had this running earlier but didn't document it), I successfully ran the maintenance-mode test suite on my local Docker instance running the latest code in https://github.com/mozilla/kuma/tree/maintenance-mode-1313237 (latest commit is https://github.com/mozilla/kuma/commit/9c0b18db5079d3946ac7f6f1c18cc3fe7ab97b63) configured for maintenance-mode and using the sample database. Since I'm using the sample database, I've excluded the search tests ("maintenance_mode and not search") since they depend upon a full copy of the production database, although one of the maintenance-mode tests hits the search page and makes sure the maintenance-mode banner, among other things, is displayed.  Here's my output:


(mdntest) rjohnson-25186:kuma rjohnson$ py.test -m "maintenance_mode and not search" tests/functional --driver Chrome --base-url http://localhost:8000 --driver-path ~/pytest-selenium/chromedriver
=============================================== test session starts ===============================================
platform darwin -- Python 2.7.12, pytest-3.0.3, py-1.4.31, pluggy-0.4.0
baseurl: http://localhost:8000
django settings: kuma.settings.testing (from ini file)
driver: Chrome
sensitiveurl: .*
rootdir: /Users/rjohnson/repos/kuma, inifile: pytest.ini
plugins: base-url-1.1.0, cov-2.2.1, django-2.9.1, html-1.10.1, rerunfailures-1.0.2, selenium-1.4.0, variables-1.4, xdist-1.15.0
collected 109 items

tests/functional/test_article.py .......
tests/functional/test_article_revision.py ..
tests/functional/test_dashboard.py ..
tests/functional/test_feedback.py ...
tests/functional/test_home.py .......
tests/functional/test_language_selector.py .
tests/functional/test_maintenance_mode_redirects.py .................................................................
tests/functional/test_notfound.py ...
tests/functional/test_profiles.py .
tests/functional/test_report.py ..
tests/functional/test_search.py .

============================================= pytest-warning summary ==============================================
WC1 None pytest_funcarg__cov: declaring fixtures using "pytest_funcarg__" prefix is deprecated and scheduled to be removed in pytest 4.0.  Please remove the prefix and use the @pytest.fixture decorator instead.
=============================================== 15 tests deselected ===============================================
========================== 94 passed, 15 deselected, 1 pytest-warnings in 262.45 seconds ==========================

Comment 4

[[github robot]]

Commit pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/c2411dbe9cb79de8af14212b256d90f939f7ded2
Merge pull request #4150 from mozilla/maintenance-mode-1313237

Maintenance Mode (Bug 1313237)

Comment 5

[Ryan Johnson (:rjohnson)]

With the merge to master, the status of this can be changed to resolved, as it's not something we will push to staging/master (i.e, enabled).

Comment 6

[[github robot]]

Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/1496c373a861452a675d7e3398ef31c12dd1ea2e
bug 1313237: Omit Maintence Mode tests

https://github.com/mozilla/kuma/commit/106cffbb01a52f28860e62b0408f304c86bfe68c
Merge pull request #4157 from mozilla/mm_int_tests_1313237

bug 1313237: Omit Maintence Mode tests