[ckan-dev] Antwort: Re: Maintenance mode

Florian.Brucker at mb.karlsruhe.de Florian.Brucker at mb.karlsruhe.de
Fri Apr 8 05:22:04 UTC 2016


https://github.com/ckan/ideas-and-roadmap/issues/171


"ckan-dev" <ckan-dev-bounces at lists.okfn.org> schrieb am 07.04.2016
18:27:44:

> Von: David Read <david.read at hackneyworkshop.com>
> An: CKAN Development Discussions <ckan-dev at lists.okfn.org>,
> Datum: 07.04.2016 18:27
> Betreff: Re: [ckan-dev] Maintenance mode
> Gesendet von: "ckan-dev" <ckan-dev-bounces at lists.okfn.org>
>
> Florian,
>
> I like the plan.
>
> Best to create an issue on the ideas-and-roadmap repo if you're not
> going to start it straight away.
>
> Dave
>
> On 7 April 2016 at 17:09,  <Florian.Brucker at mb.karlsruhe.de> wrote:
> > David,
> >
> > thanks for the update. It's good to know that everything goes through
the
> > API so that blocking writes there is a possibility. However, that means
that
> > users can still start to add/edit data and only receive an error when
they
> > try to submit their changes. So, as you said, one would at least need
some
> > kind of popup message on logins, although that would miss users that
are
> > already logged in. So maybe one could also change the edit templates so
that
> > they show a notice instead of their input form when maintenance mode is
> > enabled.
> >
> > Unfortunately I currently don't have the time to implement this
properly.
> > However, I might have in the future and I'd like to keep track of the
idea
> > so I'd like to file a ticket. Should that ticket go to
ideas-and-roadmap or
> > to ckan?
> >
> >
> > Florian
> >
> >
> > "ckan-dev" <ckan-dev-bounces at lists.okfn.org> schrieb am
07.04.201616:00:12:
> >
> >> Von: David Read <david.read at hackneyworkshop.com>
> >> An: CKAN Development Discussions <ckan-dev at lists.okfn.org>,
> >> Datum: 07.04.2016 16:00
> >> Betreff: Re: [ckan-dev] Maintenance mode
> >> Gesendet von: "ckan-dev" <ckan-dev-bounces at lists.okfn.org>
> >
> >
> >>
> >> Florian,
> >>
> >> I believe that refers to a bit of middleware:
> >> https://pypi.python.org/pypi/apachemiddleware/0.1.1
> >> The source repo is long gone, but you could install it and read the
> >> source - it's very short. I think it just returns friendly 503 error
> >> if you try to do a POST request, which will ensure that no writes
> >> occur, because the edit forms being submitted and writes to the API.
> >> However you will still need to add a banner, or pop-up message when
> >> someone tries to log-in, explaining what's going on. This would be far
> >> better than the whole site being down.
> >>
> >> I think this would be a great contribution to ckan core, but I'd want
> >> to confer - it might be solved better on other sites. I'd like to know
> >> what Django, Drupal etc do about this - no doubt there is something we
> >> can learn.
> >>
> >> David
> >>
> >> On 1 April 2016 at 08:19,  <Florian.Brucker at mb.karlsruhe.de> wrote:
> >> > Hello,
> >> >
> >> > I'm looking for a way to put my live CKAN installation into
read-only
> >> > maintenance mode so that users can continue the site but cannot make
any
> >> > changes. This would allow me to safely upgrade CKAN in the
background
> >> > without risking content inconsistencies.
> >> >
> >> > It seems that such a feature was added in 1.3 [0], but I couldn't
find
> >> > any
> >> > information about it in the current documentation. Is this feature
still
> >> > available?
> >> >
> >> >
> >> > Regards,
> >> > Florian
> >> >
> >> > [0] http://ckan.org/2011/02/18/ckan-v1-3-released/
> >> >
> >> >
> >> > _______________________________________________
> >> > ckan-dev mailing list
> >> > ckan-dev at lists.okfn.org
> >> > https://lists.okfn.org/mailman/listinfo/ckan-dev
> >> > Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
> >> >
> >> _______________________________________________
> >> ckan-dev mailing list
> >> ckan-dev at lists.okfn.org
> >> https://lists.okfn.org/mailman/listinfo/ckan-dev
> >> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
> >
> >
> > _______________________________________________
> > ckan-dev mailing list
> > ckan-dev at lists.okfn.org
> > https://lists.okfn.org/mailman/listinfo/ckan-dev
> > Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
> >
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20160408/22c69f18/attachment-0003.html>


More information about the ckan-dev mailing list