Looking to host

[Legacy_Blacktrancer]

               

That all sounds great to me but 32-bit is a must. We will be using NWNX and I don't want to figure out how to make all the linux plugins work outside of a 32-bit environment. I was told this would not be a problem on a past project and it ended up killing the project.

 

So Blacktrancer, if you and OldeFog get along, I think this will work great.

 

I'm not interested in using 32Bit architecture due to the fact that it would mean using CentOS 6.X. With the 32Bit you're looking at having a maximum of 8GB RAM which is no good in the long-term for a server that would hopefully carry a heavy load once it got on its feet. I prefer 64Bit so that the machine running the server can be a hefty 6 to 8 vCPU with 16 to 32GB RAM.

               
               

               
            

[Legacy_henesua]

               

Alright. I wouldn't be interested in figuring out how to finagle that by either chrooting or figuring out how to build the NWNX plugins on that architecture.

 

If someone else on the project will commit to building and maintaining all of the latest linux NWNX plugins on that machine and sharing them with our project, I am still game. But I am not going to be the one to do it. I just want to code and manage the database. I have no interest in maintaining infrastructure I am unfamiliar with and has proven to fail for me in the past.

               
               

               
            

[Legacy_meaglyn]

               

32bit NWNX should work fine on centos 7 64bit I'd think. The NWNX libs have to be 32bit since the game is. I'm doing that now (on centos6 x64 anyway), works fine.  You can build them on a 32bit system and copy them over.

               
               

               
            

[Legacy_niv]

               

I'd like to point out that you can compile and run nwserver+nwnx2 on a 64 bit userspace with ease, as long as you have the proper multiarch compiler suite for compiling, and the required libs for running it. The only known (to me) issue is that libq-dev on debian has a dependency bug that would make it pull in a 32bit postgres server too.

 

Note that nwserver being a 32bit binary adding a metric ton of RAM will not improve matters. No matter how much address space you offer, nwserver will not use more than 32bit of it. That said, nwserver doesn't need much RAM either. You run into cpu limitations far earlier than memory pressure (nwnx_jvm and similar hogs nonwithstanding) unless you are very careful with spreading out AI updates. '>

               
               

               
            

[Legacy_henesua]

               

I am aware that there are hoops one can jump through to make NWNX work on 64-bit distro of the OS. But I'm not going to be the one maintaining that, and have been burned by this in the past when the server admin bailed.

 

Are you committed to maintaining builds of NWNX plugins for the server Blacktrancer?

               
               

               
            

[Legacy_Pstemarie]

               

Absolutely. Simple, but very effective. 

 

Thanks, now you've got me wanting to read a novel I don't really time for ATM  '>

               
               

               
            

[Legacy_meaglyn]

               

I could build them for this server if you want.  It's generally safer not to put development tools on an internet facing server anyway...

               
               

               
            

[Legacy_Blacktrancer]

               

Supporting NWNX plugins isn't my bag.

               
               

               
            

[Legacy_henesua]

               

Sorry to hear that. I'm not sure this is a good fit for OldFog then.

               
               

               
            

[Legacy_YeoldeFog]

               

I will host it myself with henesua's specifics. Thank you for the offer Blacktrancer.