Re: [Dhis2-devs-core] dhis.conf

I am less convinced that YAML would be too much. There are of course different audiences and Lars points us to the lowest common denominator ("how do i open this in word?") who is a troublesome customer alright, but maybe not the most important one. But for db configuration this is fine. The

Re: [Dhis2-devs-core] dhis.conf

On Thu, Nov 12, 2015 at 2:23 AM, Morten Olav Hansen wrote: > What about at least using a standard extension like .properties? > I think .conf is pretty standard within the unix/linux world (postgresql.conf, users.conf, hosts.conf, etc) and it indicates that is a

Re: [Dhis2-devs-core] dhis.conf

On Thu, Nov 12, 2015 at 8:58 AM, Jason Pickering < jason.p.picker...@gmail.com> wrote: > Hi Lars, > Yes, I see your point, and maybe even YAML is too much. Having two leading > spaces could be too much to task. > > Anyway, I thought I would at least suggest it, but if a plain old > properties

Re: [Dhis2-devs-core] dhis.conf

Hi Lars, I like it. While we're at it, could we also add a feature to make it easier to run multiple DHIS 2 instances on the same machine, each with their own config file (and hence their own database)? I know there are ways to do this already, but I wonder if we can make an even simpler one by

Re: [Dhis2-devs-core] dhis.conf

Hi Jim, thanks for the feedback. I am not sure if this is the way to go. There is no standard way of getting the servlet name except from a web http request (which we can't easily get in the startup process). Also, I think its better to have separate Tomcat instances and DHIS2_HOME locations per

Re: [Dhis2-devs-core] dhis.conf

Hi Lars, That makes sense. Thanks. On Thu, Nov 12, 2015 at 12:22 PM, Lars Helge Øverland wrote: > Hi Jim, > > thanks for the feedback. > > I am not sure if this is the way to go. There is no standard way of > getting the servlet name except from a web http request (which

[Dhis2-devs-core] dhis.conf

Hi devs, a new solution for dhis configuration is in place and the conf file should now be called: *dhis.conf* The db related properties are now: connection.dialect = org.hibernate.dialect.PostgreSQLDialect connection.driver_class = org.postgresql.Driver connection.url =

Re: [Dhis2-devs-core] dhis.conf

I agree that structure is nice. However, the intention is to keep this as simple as absolutely possibly. I think the average dhis self-taught sys admin is a bit familiar with good old property files but not so much with yaml or json, and the risk for people ending up with invalid config is high. I

Re: [Dhis2-devs-core] dhis.conf

Hi Lars, Great idea, and I am sure it will be useful. Just to be a bit difficult as I usually am however. In some scripts (mostly Python) i have used YAML for these sorts of configurations. The advantage is it is pretty human readable, and yet more structured than plain text files, so it would

Re: [Dhis2-devs-core] dhis.conf

A default full config file can be found here: https://github.com/dhis2/dhis2-utils/blob/master/resources/conf/dhis.conf -- Mailing list: https://launchpad.net/~dhis2-devs-core Post to : dhis2-devs-core@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs-core More help :

Re: [Dhis2-devs-core] dhis.conf

For similar (tangentially related) configuration, I have used json. See below. Either yaml or json (or even dreaded xml), I agree with Jason that a bit of structure can be beneficial. Yaml syntax is maybe the most forgiving for user editing by hand. { "dhis2Systems" : { "hmis" : { "type" :

Re: [Dhis2-devs-core] dhis.conf

Hi Lars, Yes, I see your point, and maybe even YAML is too much. Having two leading spaces could be too much to task. Anyway, I thought I would at least suggest it, but if a plain old properties file works, then lets not over-engineer it for the moment. I can just possibly envision a situation