API v2 moving to a new repository

[lornajane]

Hey all

Just a quick heads-up, the v2 API is becoming increasingly separate from the existing website, and this will become increasingly the case as we move over to our new responsive site (early version at http://m.joind.in if you're interested).  As a result, the API is moving into its own repository over the next day or so (I hope!).  For now, be aware that there are changes coming for the v2 API source code and tools, once I've got everything in place and the docs updated, I'll send a longer email with more detail.

Feel free to either reply or find us in #joind.in on freenode if you have comments or questions.

Thanks

Lorna

[Mike van Riel]

This is super to hear, I am following this with great interest
(despite the silence ;)).

Thank you Lorna, and the other Contributors, for the time you put in
this.

> --
> You received this message because you are subscribed to the Google
> Groups "joindin-developers" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to joindin-develop...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out
> [1].
>
>
>
> Links:
> ------
> [1] https://groups.google.com/groups/opt_out

[Lorna Mitchell]

Update for you all :)

The v2 API (the one that drives http://api.joind.in) now has it's own repo: https://github.com/joindin/joindin-api  To work on the API, you need to clone this repo and issue pull requests from there.  We already have a separate category for this API on JIRA.

The biggest change is this:

** The database patches now live in the API project **

We hope that we'll be deploying http://joind.in less often and both http://api.joind.in and http://m.joind.in more often in the future, so I moved the database patching for the database that the API and existing website share over to the API project.  There isn't really a good solution to this until the newer site has all we need, but this seemed like the least worst.

If you have an existing clone of the joind.in repo, your next update will show a lot of deletions, as the API codebase, database patches, and related items all vanish.  Please fork and clone the new repo to get the API code (people working on the responsive site or the new versions of the apps which use the v2 API will need this as a dependency to their project), its API has some setup instructions for new installations but if you already had an API then:

- copy your database.php over from your existing joind.in repo

- repoint your existing virtual host at the webroot of your new clone

- hopefully things work now?  If not please email the list with the steps I just forgot about :)

If you have comments, questions or really anything else, please do get in touch.  We have the ability to separately deploy the API and website now, including test sites, and they also have their own builds, all though Jenkins (http://jenkins.joind.in).  If you see documentation or scripts that need updating, please go for it and update them, all input is appreciated!

Regards

Lorna

On 4 May 2013 16:57, Mike van Riel <mike.v...@naenius.com> wrote:

This is super to hear, I am following this with great interest
(despite the silence ;)).

Thank you Lorna, and the other Contributors, for the time you put in this.

On 03.05.2013 20:17, lornajane wrote:

Hey all

Just a quick heads-up, the v2 API is becoming increasingly separate
from the existing website, and this will become increasingly the case
as we move over to our new responsive site (early version at
http://m.joind.in if you're interested). As a result, the API is
moving into its own repository over the next day or so (I hope!). For
now, be aware that there are changes coming for the v2 API source code
and tools, once I've got everything in place and the docs updated,
I'll send a longer email with more detail.

Feel free to either reply or find us in #joind.in on freenode if you
have comments or questions.

Thanks

Lorna

 --
 You received this message because you are subscribed to the Google
Groups "joindin-developers" group.
 To unsubscribe from this group and stop receiving emails from it,

send an email to joindin-developers+unsub...@googlegroups.com.

 For more options, visit https://groups.google.com/groups/opt_out [1].



Links:
------
[1] https://groups.google.com/groups/opt_out

--
You received this message because you are subscribed to the Google Groups "joindin-developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to joindin-developers+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Lorna Mitchell
http://lornajane.net