Package: grokui.admin
grokui.admin: A basic grok admin UIThe replacement for the formergrok.adminpackage.The internal name of the admin UI is:
Grok Application Interface Application or, for short GAIA.GAIA is itself a Grok application and a subproject to the core Grok
development. Its main goal is making developing of Zope 3 and Grok
applications a faster and smarter job with more fun for everybody.Login - what is my username/password?Before you can use the admin UI, you first must log in.The username and password of the manager principal (kind of super
user) can be found in the filebuildout.cfgin the root of your
subversion checkout.In case you do not know, what ‘subversion checkout’ means, look for a
filesite.zcmlin your installation.Users ofgrokproject, might find this file in<installdir>/parts/app/site.zcml.Using the admin-UIAfter login you can visit some of the main management topics, as
described below:On top of the admin-UI you can always find three links to the main
management activities currently possible with GAIA:ApplicationsList of all instanciated applicationsYou can add new instances of Grok applicationsYou can rename instances of Grok applicationsYou can delete your installed applications.Notestarting with version 0.5 there is no introspector/class
browser included ingrokui.adminanymore. Eventually this will be
made available in another package by someone else.ServerSet security notifications. Those are by default disabled, because
they mean home-calling functionality you may do not want. You can
enable/disable those notifications or set a URL to retrieve
information about security related problems.Start/Restart the server. Caution! This does not work, if the server
was started in ‘foreground mode’ (with ‘zopectl fg’).Pack the ZODB. This removes old data from the database, freeing up
disk space. In a production environment, you might want to pack the
ZODB automatically fromcron. This can be done using a command
like the following:curl -q -s -u admin:admin "http://localhost:8080/++grokui++/@@server?pack=1&days=1"which will remove old data older than one day. If you leave out thedaysparameter, all old data will be removed.Get basic information about the running Zope system.Enter a message to be displayed on top. You can, for example, leave
a message here for your co-admins. To delete the message, just enter
the empty string in the appropriate input box.Maintaining grok installations with the admin UIThere are some special info views available especially for the use of
system administrators that want to automate Grok administration in
some aspects. They provide minimal information about certain topics.Currently the following infos are available this way:The grok version working in background:curl -q -s -u admin:admin "http://localhost:8080/++grokui++/@@admin/@@version"The security notification (if any):curl -q -s -u admin:admin "http://localhost:8080/++grokui++/@@admin/@@secnote"Beside this you can pack the ZODB databases as described above.grokui.admin changes1.0 (2023-08-28)Drop support for Python 2.7, 3.5, 3.6.Add support for Python 3.7, 3.8, 3.9, 3.10, 3.11.Caution: With this release the maintenance of this package ends.0.13 (2020-08-20)Python3.6+ compatibility.0.12 (2016-02-16)Update to follow API changes in grok.Update tests.0.11 (2012-05-02)Make sure to require the latest grok and grokcore.site.0.10 (2011-07-14)Nothing changed yet.0.9 (2011-01-20)Use the correct IApplication interface definition.0.8 (2010-10-27)In testing the security notifications, start a server instead of usingfile://localhostURLs. This saves a lot of urlopen troubles across
platforms.Test setup cleanup.0.7.2 (2010-10-26)Fix tests in Windows.0.7.1 (2010-10-07)Fix a bug in the test setup where zope.session was not configurred.Fixhttps://bugs.launchpad.net/grok/+bug/638763We don’t hide away Duplication/KeyErrors that are raised during
application creation any more.0.7.0 (2010-07-04)The application creation view now uses the Grok util functioncreate_application. Therefore, theApplicationInitializedEvent,
recently introduced in Grok, is now triggered while an application is
created and persisted. This is an important event, allowing to hook
handlers that need local utilities and catalog indexes that are not
yet present at the ObjectCreatedEvent stage.0.6.2 (2010-05-19)Modified package to comply with Zope Foundation policy.Removed duplicated/unused code.
Fixhttps://bugs.launchpad.net/grok/+bug/539940Reflect changes in Folder API: check also for KeyError, not only for
DuplicationError when adding new apps.Added extra-templatedirs and moved templates into these in order to
avoid (erraneous) templatedir-registry warnings.0.6.1 (2010-03-07)Added missing tests dependencies. Declarations and includes should
now be complete.0.6 (2010-02-28)Moved theIndexview togrokui.base.The design has been slightly changed to get rid of the lazy Grok and
to match thehttp://grok.zope.orgwebsite design. The design belongs
now togrokui.base.grokui.adminhas been splitted into several packages. It now depends
ongrokui.basethat provides basic components to create and plug UI
views.grokui.adminhas been altered to reflect the splitting
changes and now provides a collection of components that will allow
you to plug your own administration panels and elements.Dependencies have been drastically cut down. We are now using the
ZTK. The only zope.app package remaining is for the tests.Reflect the changes in grokcore.view 1.12 where View and CodeView
become a single View again.0.5 (2009-09-15)Feature changesThe whole introspector stuff was removed in order to reduce number
of dependencies.Bug fixesAdding apps now emits IObjectCreated events.0.4.1 (2010-02-14)Bug fixesBackports of fixes from 0.3.3 version (see below).0.4 (2009-08-21)Feature changesAdded a security notifier to inform users when security issues are
published onhttp://grok.zope.org. The notifier must be explicitly
enabled. You can also run your own site/directory to place security
notifications.Added info views to get important information easier with tools likecurl. Supported infos:Grok version usedCurrent security notification (if any).Bug fixesAdapting this package to use the new version of grokcore.view
which splits View into CodeView.Upgraded the versions to the alpha 4 list to avoid a dependency
problem with zope.container versions.Include the new grok.View permissions for testing.0.3.3 (2010-02-14)Bug fixesFixed bug in object browser: objects that ‘booleanized’ evaluated toFalse(empty containers for instance) were not displayed.0.3.2 (2009-04-10)Added dependency for zope.app.preference. This is needed by
zope.app.apidoc but not always fetched.0.3.1 (2009-04-09)Fixed missing dependencies in setup.py.0.3 (2008-12-13)Feature changesAdded capability to pack ZODBs (thanks to Jasper Spaans).0.2 (2008-12-01)Feature changesAdded capability to rename apps.0.1.2 (2008-09-28)Made server controls dependent from availability ofIServerControl. Otherwise the buttons for restarting or stopping
the server process are not rendered.0.1.1 (2008-08-05)Fixed wrong links in docgrok template.Fixed ftesting.zcml that did not work with Grok 0.13.0.1 (2008-07-10)Feature changesInitial implementation by factoring outgrok.adminfromgrok.