In Windows there is %USER%/Application Data folder (or just %USER%) that is analog of ~/. in Linux. MacOS has home directory as well, so that should not be a problem.
> On 26 Aug 2019, at 14:41, Dmitriy Pavlov <dpav...@apache.org> wrote: > > Ok, folks, I'm not insisting on > ~/ignite/work nor ~/.ignite/work > > I wondering what about Windows systems. Linux is not only one platform > Ignite runs on. > > пн, 26 авг. 2019 г. в 14:28, Maxim Muzafarov <maxmu...@gmail.com>: > >> Folks, >> >> According to the Filesystem Hierarchy Standard [1] (Wikipedia is not >> the ideal reference), the `/var/lib` directory is the `state >> information. Persistent data modified by programs as they run, e.g., >> databases, packaging system metadata, etc.` >> >> So, I'm +1 for `/var/lib/ignite` to place persisted Ignite files there. >> >> [1] https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard >> >> On Mon, 26 Aug 2019 at 14:00, Nikolay Izhikov <nizhi...@apache.org> wrote: >>> >>> Yes, of course. >>> >>> В Пн, 26/08/2019 в 13:58 +0300, Petr Ivanov пишет: >>>> Does this parameters intended to be overridden (for tests purposes for >> example) or it will be permanently sticked to this new directory without >> ability to change? >>>> >>>> >>>>> On 26 Aug 2019, at 13:58, Nikolay Izhikov <nizhi...@apache.org> >> wrote: >>>>> >>>>> +1 for '/var/lib/ignite' >>>>> >>>>> В Пн, 26/08/2019 в 13:28 +0300, Dmitriy Pavlov пишет: >>>>>> +1 for '~/.ignite/work' >>>>>> >>>>>> пн, 26 авг. 2019 г. в 13:27, Anton Kalashnikov <kaa....@yandex.ru >>> : >>>>>> >>>>>>> Hello, Igniters. >>>>>>> >>>>>>> There are a lot of variants was already proposed lets vote to >> one of them. >>>>>>> I made a list of possible paths which was mentioned earlier. I >> also >>>>>>> included variants outside of home directory('user.dir') to this >> list but I >>>>>>> want to notes that we had already discussed it and we decided to >> choose >>>>>>> some path in home directory rather outside of that. Also If you >> have any >>>>>>> other variants feel free to add it. >>>>>>> >>>>>>> 1) ~/.ignite/work >>>>>>> 2) ~/ignite/work >>>>>>> 3) ~/.config/ignite/work >>>>>>> >>>>>>> 4)/var/lib/ignite >>>>>>> 5)/usr/local/ignite >>>>>>> 6)/var/ignite >>>>>>> 7)/var/lib/ignite >>>>>>> 8)/opt/ignite/ >>>>>>> >>>>>>> +1 for '~/.ignite/work' >>>>>>> >>>>>>> -- >>>>>>> Best regards, >>>>>>> Anton Kalashnikov >>>>>>> >>>>>>> >>>>>>> 26.08.2019, 12:39, "Nikolay Izhikov" <nizhi...@apache.org>: >>>>>>>> Ilya, >>>>>>>> >>>>>>>>> In development environment one can just run Java from >> /var/lib/ignite >>>>>>>> >>>>>>>> Actually, I doesn't understand you. >>>>>>>> Are you talking about development of some application that >> uses Ignite >>>>>>> >>>>>>> or contribution to Ignite code base? >>>>>>>> >>>>>>>> If we are talking about some application that uses Ignite then >> we should >>>>>>> >>>>>>> decide, which scenario is primary. >>>>>>>> (One more time, we are talking about PDS enabled caches): >>>>>>>> >>>>>>>> 1. Ignite server node started as separate java process. >>>>>>>> 2. Ignite server node embedded in application as a library. >>>>>>>> >>>>>>>> I think, for PDS enabled cashes first case is primary. >>>>>>>> In that case, user should install Ignite via some package(deb, >> rpm, >>>>>>> >>>>>>> docker, etc). >>>>>>>> This package should done all required configuration. >>>>>>>> Including directory permissions. >>>>>>>> >>>>>>>> This should be done like other DBMS do. >>>>>>>> >>>>>>>> If we are talking about embedded Ignite then we can ask the >> user to >>>>>>> >>>>>>> provide sufficient permission for default dir or change dir to >> some other. >>>>>>>> >>>>>>>> So, I still think we should use /var/lig/ignite for PDS data. >>>>>>>> >>>>>>>> How it sounds? >>>>>>>> >>>>>>>> В Пн, 26/08/2019 в 12:23 +0300, Ilya Kasnacheev пишет: >>>>>>>>> Hello! >>>>>>>>> >>>>>>>>> In development environment one can just run Java from >> /var/lib/ignite >>>>>>>>> (makes total sense) and will immediately get almost correct >> behavior >>>>>>> >>>>>>> (well, >>>>>>>>> data will be stored to /var/lib/ignite/ignite/work) >>>>>>>>> >>>>>>>>> However, I still think that we should write to >> user.dir/ignite and not >>>>>>> >>>>>>> just >>>>>>>>> user.dir since current directory is often crowded. >>>>>>>>> >>>>>>>>> Fellows, anyone who is against using user.dir? Please share >> your >>>>>>> >>>>>>> concerns. >>>>>>>>> >>>>>>>>> Regards, >>>>>>> >>>>>>> >>>> >>>> >>
