910d71eefc
Add code of django-restframwork to taiga
2015-04-14 11:15:15 +02:00
c178aacdb2
Update djmail to 0.10
2015-03-26 12:42:41 +01:00
bd0b162a0e
Update django to 1.7.6
2015-03-10 09:27:16 +01:00
b8ac3e7937
Incremented django-transanctional-cleanup to 0.1.14 version
2015-02-18 08:35:00 +01:00
589490d7a5
Update django to 1.7.4 and update dev requirements
2015-02-16 19:24:10 +01:00
357d7706a1
Upgrade django-pgjson to 0.2.2
2015-02-11 13:36:47 +01:00
50fd9b6161
Locking the element on take_snapshot to avoid racing condition issues
2015-02-11 11:10:37 +01:00
47a0b46b5e
Updated django-transactional-cleanup version
2015-02-10 18:59:57 +01:00
6e13e774d6
Upgrade django-pgjson to 0.2.1
2015-02-09 16:11:31 +01:00
8858c8b782
Revert "Update django-pgjson from 0.2.0 to 0.2.1"
...
This reverts commit 67ef7de61f
2015-02-07 00:57:50 +01:00
67ef7de61f
Update django-pgjson from 0.2.0 to 0.2.1
2015-02-07 00:26:36 +01:00
cc046b5555
Add lxml to requirements.txt file
2015-01-29 13:05:07 +01:00
0d591dcadc
Translate and fix all emails
2015-01-26 09:44:57 +01:00
6e39a8f7a8
Add django-transactional-cleanup and configure it
2015-01-14 11:57:00 +01:00
a8afd77f89
Add import/export functionality to the API
2015-01-13 13:43:09 +01:00
4fe73aef52
US #1680 : Emails redesign
2015-01-12 18:04:41 +01:00
3e46b439bf
Bitbucket webhooks for commits
2014-12-02 14:42:42 +01:00
c83ffa8529
Fix issue #1500 : Now generated html is escaped
2014-10-31 13:10:34 +01:00
da6feaf26e
Revert "Update django version to 1.7.1"
...
This reverts commit fab678987a
2014-10-30 23:27:28 +01:00
fab678987a
Update django version to 1.7.1
2014-10-26 19:23:02 +01:00
50afed05f9
Adding raven requirement
2014-10-22 12:48:28 +02:00
51f0ef7fef
Update gunicorn version on requirements.
2014-10-13 16:59:00 +02:00
8ffce26fb8
Fix requirements.txt
2014-10-08 01:48:15 +02:00
bbc6635812
Removing duplicated enum requirement
2014-10-07 18:17:32 +02:00
8a1303f11d
Removing duplicated Unidecode
2014-10-07 18:06:53 +02:00
bd11e51cc8
Merge branch 'master' into stable
...
Conflicts:
requirements.txt
2014-10-07 15:46:35 +02:00
1c0d6cd706
[backport] Making the project name not mandatory and using the owner username for the slug generation
2014-10-03 22:38:54 +02:00
b82f6a4743
Making the project name not mandatory and using the owner username for the slug generation
2014-10-03 22:27:10 +02:00
0e535cf0f1
Fix unclear message on requirements.txt.
2014-09-29 23:28:09 +02:00
43e16c2c13
Taiga-events integration (realtime taiga)
2014-09-29 17:49:47 +02:00
9ac490ef40
Update 3rd party libraries to latest versions (requirements.txt).
2014-09-16 10:48:43 +02:00
749f75dfe2
Add pillow to requirements.
2014-09-16 10:48:42 +02:00
d9e4d30bb3
Remove reversion from requirements.txt
2014-09-16 10:48:42 +02:00
f88d92910a
Update requirements.
2014-09-16 10:48:42 +02:00
530c459687
Update the sampledatahelper version and use file_from_directory
2014-09-01 18:15:16 +02:00
a5865a1cec
Update django to latest stable version.
2014-09-01 11:45:49 +02:00
2a925bf40e
Upgrade the django version to the last bugfix release
2014-08-26 09:29:26 +02:00
0e414267db
Integration with RabbitMQ and Celery
...
First update taiga-vagrant vm if you're using it, you will have access
to the rabbit management console at port 8001 of the host machine.
* Defining tasks
- Tasks must be defined in a `deferred` module of an app, for example,
`taiga.projects.deferred` module.
- Tasks must be decorated and given the name "<app>.<task-name>", for
example in `taiga.projects.deferred` module:
```
from taiga.celery import app
@app.task(name="projects.add")
def add(x, y):
return x + y
```
- Tasks should be at most just wrappers around service functions to
promote re-usability of those functions from other parts of the code,
say, management commands and the like.
* Calling tasks
Tasks should be called using one of the three functions defined in
`taiga.deferred` module:
- `defer`: Use this function if you need to perform some task
asynchronously and GET THE RESULT back later, for example:
```
result = defer("projects.add", x=1, y=2)
...
result.get() # => 3
```
- `call_async`: Use this function when you want to fire off some
task. No result is get back. For example:
```
call_async("projects.email_user", user)
```
- `apply_async`: Is the same as `call_async` but since it's a function
application and you must pass the args and kwargs together as one
parameter each you are allowed to pass celery-specific
extra-options (but bear in mind this is not recommended!)
```
apply_async("projects.email_user", args=(user,), kwargs={}, routing_key="tasks.email")
```
2014-07-02 09:49:56 +02:00
a8085a2feb
Return user photo cropped and with absolute url
...
Remember to run `pip install -r requirements.txt` to install the
additional dependencies.
2014-07-01 14:38:26 +02:00
b652cdc5f2
Add request to requirements
2014-06-29 02:13:03 +02:00
ac5e163dc5
Implement tags using pg arrays
2014-06-18 10:14:29 +02:00
5cbfaa8a20
Update djmail to versión 0.7
2014-06-12 12:17:31 +02:00
671cc0fcbc
Increment djmail version to 0.6
2014-06-12 00:12:15 +02:00
68a79a4b1e
Update requirements and fix some errors
2014-06-05 10:20:25 +02:00
613f84b31a
Update requirements
2014-06-04 20:22:24 +02:00
2b087678b9
Remove domains.
2014-05-26 17:33:12 +02:00
53425bedba
Adding diff patch html for description fields
2014-05-16 22:20:01 +02:00
a84b50c00b
Fix tests
2014-05-16 10:17:35 +02:00
e824932f4c
Add mdrender module
2014-05-09 12:29:12 +02:00
a8bdb364ee
Add history module
2014-05-09 10:32:52 +02:00
David Barragán Merino
Jesús Espino
Alejandro Alonso
Xavier Julián
Alejandro Alonso
Jesús Espino
Andrey Antukh
Anler Hp