Skip to content

Loading…

Updated README with more precise instructions #4

Merged
merged 2 commits into from

2 participants

@arthurlutz

No description provided.

arthurlutz added some commits
@arthurlutz arthurlutz Update README.rst
more precise description of plugins required and which kind of OAuth token to use
390dcc1
@arthurlutz arthurlutz Update README.rst
formating
58dab30
@joar joar merged commit 5aa3ac3 into joar:master
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Jan 10, 2013
  1. @arthurlutz

    Update README.rst

    arthurlutz committed
    more precise description of plugins required and which kind of OAuth token to use
  2. @arthurlutz

    Update README.rst

    arthurlutz committed
    formating
Showing with 13 additions and 3 deletions.
  1. +13 −3 README.rst
View
16 README.rst
@@ -38,17 +38,27 @@ directory containing the ``automgtic.ini`` file and run::
Usage
-------
+Make sure to activate the following plugins on mediagoblin ::
+
+ [plugins]
+ [[mediagoblin.plugins.oauth]]
+ [[mediagoblin.plugins.api]]
+ [[mediagoblin.plugins.httpapiauth]]
+
+
Once you have installed the dependencies, you need to have an OAuth client
registered on the GNU MediaGoblin instance, you can register one at
``instance.example/oauth/client/register``.
+Name it what you want, type should be "Public", and Redirect URI should be "http://www.foo.example/".
+
Once you have registered your OAuth client you need the client identifier in
your config.
.. warning::
- Before you start editing your config, do ``cp automgtic.ini
- automgtic_local.ini``, this to separate the version-controlled
- ``automgtic.ini`` from your local settings.
+ Before you start editing your config, do
+ ``cp automgtic.ini automgtic_local.ini``, this to separate the
+ version-controlled ``automgtic.ini`` from your local settings.
When the ``client_id`` is set, run ``./run.py --authorize``, then follow the
instructions provided. This will update your ``.ini`` with the ``access_token``
Something went wrong with that request. Please try again.