Local haxelib server using sqlite uses different db path for website and remoting API

[jasononeil]

Using "localhost:2000/" for the website, and "localhost:2000/api/3.0/" for the API, they use different paths:

Website: /root/haxelib.db API: /root/../../haxelib.db

This would obviously be a good idea to fix...

[back2dos]

Uhm, is this still an issue?

[jasononeil]

Yes, but I doubt it affects many people. I'll look at it after some of the more urgent ones.

[nadako]

That is due to -D haxelib_api, but I really have no Idea why it's even needed. Let's remove it?:)

[back2dos]

Off the top of my head I think this is related to the fact that the remoting API module is built separately from the web server and located in some subfolder (api/3.0 or somesuch thing).

On Tue, Dec 22, 2015 at 10:30 PM, Dan Korostelev [email protected] wrote:

That is due to -D haxelib_api, but I really have no Idea why it's even needed. Let's remove it?:)

— Reply to this email directly or view it on GitHub https://github.com/HaxeFoundation/haxelib/issues/56#issuecomment-166734716 .

[nadako]

Maybe that's related to some mod_neko cwd behaviour? Because for nekotools server i have to compile WITHOUT -D haxelib_api

[nadako]

@andyli you do have access to haxelib servers nowadays? could you check if we can get rid of that -D haxelib_api define and not break anything? :)