Closed #391. `je/42cc_3154_blog_api`
Docs:
Endpoint: _prefix/_
* GET _prefix/_ - returns a list of posts, including title and API url
* GET _prefix/year/month/title_ - returns a JSON representation of a post
* POST _prefix/_ - creates a post
* parameter title - the title of the post
* parameter text - the text of the post
* parameter labels - labels of the post
* parameter state - 'draft' or 'published'
* POST _prefix/year/month/title_ - updates an existing post
* parameter parameters:
* parameter title - the title of the post
* parameter text - the text of the post
* parameter labels - labels of the post
* parameter state - 'draft' or 'published'
---
** [tickets:#3154] Users need a way to backup allura data [idt 824]**
**Status:** in-progress
**Labels:** support feature-parity p2 42cc
**Created:** Wed Nov 02, 2011 06:41 PM UTC by Chris Tsai
**Last Updated:** Mon Jul 15, 2013 11:23 AM UTC
**Owner:** nobody
https://sourceforge.net/apps/ideatorrent/sourceforge/ideatorrent/idea/824/
>SF clearly says that the backup of the project data is left to project admins:
>https://sourceforge.net/apps/trac/sourceforge/wiki/Backup%20your%20data
>Fine.
>However, there is currently no way to backup the SF2.0 tools, for instance the
>data from the ticket tool.
Backups would be the first step, then a way to restore (though we never offered
that part in SF classic to my knowledge)?
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed
to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
