View Single Post
  #12  
Old 01-18-2017, 03:42 AM
Shin Noir's Avatar
Shin Noir
Legendary Member
 
Join Date: Apr 2002
Location: Seattle, WA
Posts: 502
Default

If you wanted to be slick, take a VM you can keep up 24/7 and fork latest eqemu/server master branch, then set up a cron to auto pull it to a local instance and keep it up with latest tip and auto compile, and commit to another repo precompiled for your docker instance.

Put a copy of quest/misc files in there too.

Then, set up a db dump for initial run, and use akka's world menu from then on.

Lastly, write a master Makefile tweaks, like
make init, initialize and pull down latest repo db, quest etc into current dir.
make update, pull down latest repo db/quest etc
make run, run docker instance with current dir as volume attachment point.
make shell, shell into docker instance
make list, list current running docker containers

etc

Then, spinning up your docker instance is all contained in a makefile.. If someone wants to ground up compile, they just replace the binaries, but if they don't, this makefile can configure and run everything without compiling.

I'm not sure why your image is large, why not just split mysql into it's own docker image vanilla pointing to a local volume dir, link it to a vanilla linux instance, and mount the local stuff and include some commands to build the few dependencies required to run eqemu, and be done with it? no need for gcc and all that. Docker-compose can handle it all. And, could look into kubernetes as an alternative.

When someone wants to dev and build source, i'd say toss that in it's own standalone image, and add it to the above make listing

Been looking into putting eqemu on docker myself for a bit. =)

I think I have the docker eqemu project/org reserved, btw, if you want to push the imagesthere eventually let me know.
__________________

~Shin Noir
DungeonEQ.com

Last edited by Shin Noir; 01-18-2017 at 04:01 AM..
Reply With Quote