Skip to content

Instantly share code, notes, and snippets.

@daronco
Last active August 29, 2015 14:13

Revisions

  1. Leonardo Crauss Daronco revised this gist Jan 12, 2015. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion gistfile1.md
    Original file line number Diff line number Diff line change
    @@ -1,7 +1,7 @@
    * Access the API Mate: http://mconf.github.io/api-mate/
    * Create a new meeting.
    * Join this meeting to make sure it won't be removed from the server in case you take too long to run the other steps.
    * Use `getConfigXML` via GET to get the default `config.xml`.
    * Use `getDefaultConfigXML` via GET to get the default `config.xml`.
    * Copy and paste this `config.xml` into a new file. Edit it to remove any special characters (e.g. you might have HTML tags in the copyright field, so you have to remove or escape them).
    * Edit your `config.xml` according to your needs.
    * Put the edited XML content in the "XML for setConfigXML via POST" field in the API Mate.
  2. Leonardo Crauss Daronco revised this gist Jan 12, 2015. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion gistfile1.md
    Original file line number Diff line number Diff line change
    @@ -5,7 +5,7 @@
    * Copy and paste this `config.xml` into a new file. Edit it to remove any special characters (e.g. you might have HTML tags in the copyright field, so you have to remove or escape them).
    * Edit your `config.xml` according to your needs.
    * Put the edited XML content in the "XML for setConfigXML via POST" field in the API Mate.
    * Instead of using the API Mate to call `setConfigXML` (don't just click in the link), use another tool that runs outside of the browser. `curl` is a good option. First, copy the link the API Mate generated to `setConfigXML`. It will be a really long URL. Then use it with curl (replace `<link>` by the URL):
    * Instead of using the API Mate to call `setConfigXML` (don't just click in the link), use another tool that runs outside of the browser. `curl` is a good option. First, copy the link the API Mate generated to `setConfigXML`. It will be a really long URL. Then use it with `curl` (replace `<link>` by the URL):

    ```bash
    curl --header "Content-Type:application/xml" -i -X POST '<link>'
  3. Leonardo Crauss Daronco revised this gist Jan 12, 2015. 1 changed file with 6 additions and 2 deletions.
    8 changes: 6 additions & 2 deletions gistfile1.md
    Original file line number Diff line number Diff line change
    @@ -5,15 +5,19 @@
    * Copy and paste this `config.xml` into a new file. Edit it to remove any special characters (e.g. you might have HTML tags in the copyright field, so you have to remove or escape them).
    * Edit your `config.xml` according to your needs.
    * Put the edited XML content in the "XML for setConfigXML via POST" field in the API Mate.
    * Instead of using the API Mate to call `setConfigXML` (don't just click in the link), use another tool that runs outside of the browser. `curl` is a good option. First, copy the link the API Mate generated to `setConfigXML`. It will be a really long URL. Then use it with curl (replace <link> by the URL):
    * Instead of using the API Mate to call `setConfigXML` (don't just click in the link), use another tool that runs outside of the browser. `curl` is a good option. First, copy the link the API Mate generated to `setConfigXML`. It will be a really long URL. Then use it with curl (replace `<link>` by the URL):

    ```bash
    curl --header "Content-Type:application/xml" -i -X POST '<link>'
    ```

    The answer should be something like:

    ```xml
    <response>
    <returncode>SUCCESS</returncode>
    <token>asdfl234kjasdfsadfy</token>
    <token>qHgdIqZz</token>
    </response>
    ```

    * If you got the answer above, use the value inside `<token>` to join a new user. Paste the token in the field `configToken` in the API Mate and then join the meeting as you usually would, using the join links (as moderator or attendee, it doesn't matter). The user that just joined should be using the configurations you set in your `config.xml`.
  4. Leonardo Crauss Daronco created this gist Jan 12, 2015.
    19 changes: 19 additions & 0 deletions gistfile1.md
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,19 @@
    * Access the API Mate: http://mconf.github.io/api-mate/
    * Create a new meeting.
    * Join this meeting to make sure it won't be removed from the server in case you take too long to run the other steps.
    * Use `getConfigXML` via GET to get the default `config.xml`.
    * Copy and paste this `config.xml` into a new file. Edit it to remove any special characters (e.g. you might have HTML tags in the copyright field, so you have to remove or escape them).
    * Edit your `config.xml` according to your needs.
    * Put the edited XML content in the "XML for setConfigXML via POST" field in the API Mate.
    * Instead of using the API Mate to call `setConfigXML` (don't just click in the link), use another tool that runs outside of the browser. `curl` is a good option. First, copy the link the API Mate generated to `setConfigXML`. It will be a really long URL. Then use it with curl (replace <link> by the URL):

    curl --header "Content-Type:application/xml" -i -X POST '<link>'

    The answer should be something like:

    <response>
    <returncode>SUCCESS</returncode>
    <token>asdfl234kjasdfsadfy</token>
    </response>

    * If you got the answer above, use the value inside `<token>` to join a new user. Paste the token in the field `configToken` in the API Mate and then join the meeting as you usually would, using the join links (as moderator or attendee, it doesn't matter). The user that just joined should be using the configurations you set in your `config.xml`.