Easy DIY Linux Install

[rubysoul]

One other thing I noted - I actually have newer opcodes and patches than you. Mine have a few more entries making the files slightly larger.

[plesky]

Originally Posted by rubysoul

Oh interesting, the docker had the executables all in a "bin" folder. Let me restructure things to mirror yours.

EDIT: Actually.. I'm wondering if yours is an old way of structuring it? I just checked and my previous Windows install that still works had all the executables in a bin folder, too.

The executables ARE in a bin folder. (as per readme-setup doc) Those are symlinks in the screenshot (not included in the "install" folder

[rubysoul]

Originally Posted by plesky

The executables ARE in a bin folder. (as per readme-setup doc) Those are symlinks in the screenshot (not included in the "install" folder

Ahhhh gotcha! I modified your calling scripts to call in the bin folder haha.

[rubysoul]

https://imgur.com/a/NeKRwlu

This is how I did it since I wanted the installation self-contained like the windows version. I didn't want the separate eqemu user nor that folder.

(I can't see the image and I'm not sure why so I pasted the url too)

(also ignore bin-docker, it's just a backup of the executables built in the docker, I'm running the precompiled ones now)

[plesky]

You can technically setup the bin folder anywhere, put the executables inside it, as long as your symlinks point to them. One time, I created a bin folder, right inside the server folder and put them in there to run them.

In the original linux install, it created a /home/eqemu/server_source and /home/eqemu/server_build (which also created a bin inside of that) when the binaries were compiled.

If you follow the instructions for compiling, at the end of that readme-setup, whatever build directory is used for compiling, it will create a bin folder there.

[rubysoul]

Originally Posted by plesky

You can technically setup the bin folder anywhere, put the executables inside it, as long as your symlinks point to them. One time, I created a bin folder, right inside the server folder and put them in there to run them.

In the original linux install, it created a /home/eqemu/server_source and /home/eqemu/server_build (which also created a bin inside of that) when the binaries were compiled.

If you follow the instructions for compiling, at the end of that readme-setup, whatever build directory is used for compiling, it will create a bin folder there.

Yep, that's how the docker runs it. Too bad the docker itself didn't work, either, but I won't get into that in this thread lol. I'll probably just end up going back to creating the 10 zones manually for now. I really can't figure out where the hickup is at this point and I feel like I've checked virtually everything.

[plesky]

Originally Posted by rubysoul

Yep, that's how the docker runs it. Too bad the docker itself didn't work, either, but I won't get into that in this thread lol. I'll probably just end up going back to creating the 10 zones manually for now. I really can't figure out where the hickup is at this point and I feel like I've checked virtually everything.

I would assume, the biggest hurdle in anyone creating a full install script for linux, would simply be having solid download links for the installer. When I was having problems compiling current code in debian 11, there was updates needed that I couldn't get from debian repo anymore, I had to upgrade to debian 12 to get what I needed for a smooth compile. (debian 11 is fading into the woodwork), lol

The docker install, I "think" was created by that Akkadius that left recently. I'm not sure.

[rubysoul]

Originally Posted by plesky

I would assume, the biggest hurdle in anyone creating a full install script for linux, would simply be having solid download links for the installer. When I was having problems compiling current code in debian 11, there was updates needed that I couldn't get from debian repo anymore, I had to upgrade to debian 12 to get what I needed for a smooth compile. (debian 11 is fading into the woodwork), lol

The docker install, I "think" was created by that Akkadius that left recently. I'm not sure.

Yep, it was. Someone updated the docker 2 weeks ago to "fix all the links". Maybe something isn't quite right with it still.

I've only worked with Ubuntu personally. That was the last thing I could think of, that maybe this one quirk is related to running the newer 24.04, but who knows at this point lol.

[rubysoul]

Ok, I got it working. I gotta own this one lol.

Creating the symlinks in the root of the installation, pointed at the bin folder right there in the installation, fixed the problem.

I didn't think this could actually be the problem because everything else worked, but I was wrong. The only thing that makes any sense to me is I saw a snippet somewhere, not even related directly to this problem, where someone mentioned the executable point needs to be in the same folder as the eqemu_config.json file. I guess I proved everything else EXCEPT the dynamic zones works thru just a reference of the original calling folder lol. Oh well, it's fixed! Thanks for dealing with me LOL.

[plesky]

Someday, maybe I will go to work on that install.sh script to turn it into a full auto-install, but I would need to secure download file links for it. It's still the original install script, all I did was edit a few lines to compensate for manual setup. Originally, in the script, it would download the eqemu_server.pl which the script would call at the end of it. So a big part of the install was in that .pl file

If I could get my hands on that original eqemu_server.pl file it would help build a new script. But the current one available is blank.

[rubysoul]

Originally Posted by plesky

Someday, maybe I will go to work on that install.sh script to turn it into a full auto-install, but I would need to secure download file links for it. It's still the original install script, all I did was edit a few lines to compensate for manual setup. Originally, in the script, it would download the eqemu_server.pl which the script would call at the end of it. So a big part of the install was in that .pl file

If I could get my hands on that original eqemu_server.pl file it would help build a new script. But the current one available is blank.

This?

https://github.com/kevman5/Eq-Emulat...qemu_server.pl

[plesky]

Originally Posted by rubysoul

This?

https://github.com/kevman5/Eq-Emulat...qemu_server.pl

Ya, but that one is blank too, lol

[rubysoul]

Originally Posted by plesky

Ya, but that one is blank too, lol

Which part? That link is a 2807 line file for me, unless it's a url in that file that you're talking about.

Another link, think this one is direct from Akk:

https://github.com/EQEmu/Server/blob...qemu_server.pl

[plesky]

Ok, I was having probs viewing the files right on github, but I downloaded it and YES, that's the file I need. Last time I did a windows install, (long ago) it downloaded a blank eqemu_server.pl file. Even the one's in my windows servers, have a blank one. But I think the installer gets it from elsewhere

But it's obviously still available. I just kept seeing a blank file on the github, must be my browser, lol

[plesky]

In the source github changelog it shows:

### Deprecation

* Remove eqemu_server.pl script and ties to server ([#4049](https://github.com/EQEmu/Server/pull/4049)) @Akkadius 2024-02-10

Obviously the modern code had no use for it anymore. It was also used for updates, etc, previously.