I personally would think this would make more sense as a permission for a
user role. That way, it is very clear who is allowed to do what.
Regards,
Jason
On Mon, Mar 24, 2014 at 3:45 PM, riddy ndoma riddynd...@gmail.com wrote:
I think as good. Because it's flexible @Lars!
2014-03-23 19:57
We have actually accommodated other weeks (eg Wed to Tue) in Cambodia, but
this code is not yet part of the core.
On Mar 24, 2014 12:53 PM, Jason Pickering jason.p.picker...@gmail.com
wrote:
Hi Shantala,
The weeks are calculated according to the ISO 8601 time and date standard.
This generally
Hi,
I've noticed this bug too, but it only seems to happen when one first
filters on the data elements.
Manaf, can you try selecting your data element without first filtering on
the name, and see if that works?
bram
On Mar 24, 2014 5:44 AM, Tran Chau tran.hispviet...@gmail.com wrote:
Hi
Thank you. This helps.
On Mon, Mar 24, 2014 at 11:58 AM, Knut Staring knu...@gmail.com wrote:
We have actually accommodated other weeks (eg Wed to Tue) in Cambodia, but
this code is not yet part of the core.
On Mar 24, 2014 12:53 PM, Jason Pickering jason.p.picker...@gmail.com
wrote:
Hi
Could you elaborate a bit on your specific requirements?
Knut
On Mon, Mar 24, 2014 at 8:14 AM, Shantala Raman sra...@thoughtworks.comwrote:
Thank you. This helps.
On Mon, Mar 24, 2014 at 11:58 AM, Knut Staring knu...@gmail.com wrote:
We have actually accommodated other weeks (eg Wed to
Sure. The requirement is to have data collection done weekly with the week
being an Epi week http://www.cmmcp.org/epiweek.htm (epidemiology week),
having week start date of Sunday and end date of Saturday.
On Mon, Mar 24, 2014 at 12:48 PM, Knut Staring knu...@gmail.com wrote:
Could you
Hi Jason
You can't fix your problem with nginx config without first addressing your
bind error. The error is simple enough - it just means something else is
already listening on port 80.
So try this:
sudo netstat -ntlp |grep ':80'
which will show you in the last column what exactly is
Hi all,
I have managed to answer my own question, through trial and error - but
thought I would share the solution for those who are interested:
1. After installing nginx, I replaced the contents of the
/etc/nginx/proxy_params file with the following:
proxy_redirect off;
Hi Bob,
Thanks for your reply. I found I had to disable the static content serving
to make nginx work, at least in the config I ended up with. Clearly, there
are a lot of improvements I can make to our location settings, and nginx is
certainly both very powerful and flexible. Spent quite a
Hi Jason
Your config now looks very much like what gets deployed by dhis2-tools:
http://bazaar.launchpad.net/~dhis2-devs-core/dhis2/trunk/view/head:/tools/dhis2-tools-deb/pkg/usr/share/dhis2-tools/samples/nginx/dhis2
.
With the exception that you have done that neat trick with proxy_params
which
Hi Shantala,
As Knut's email alludes to , along the article which you shared hints at,
there may be different definitions of what an Epi Week actually is.
It is therefore that DHIS2 has adopted the ISO standard definition, which
can be determined with precision, due to the rigor of its
11 matches
Mail list logo
