Closed urFate closed 2 years ago
Hmm, it seems to be a big in the Magma since it is advertising the same (server) jar as the installer_link
:
{"name":"efb9116e","tag_name":"efb9116e","created_at":"2022-07-01T19:37:54.053Z","link":"https://git.magmafoundation.org/api/v4/projects/7/packages/maven/org/magmafoundation/Magma/1.12.2-efb9116e/Magma-1.12.2-efb9116e.jar","installer_link":"https://git.magmafoundation.org/api/v4/projects/7/packages/maven/org/magmafoundation/Magma/1.12.2-efb9116e/Magma-1.12.2-efb9116e.jar","git_commit_url":"https://git.magmafoundation.org/magmafoundation/Magma/commit/efb9116e"}
It would be great if you could help look for or create an issue with them for their API.
Hmm, it seems to be a big in the Magma since it is advertising the same (server) jar as the
installer_link
:{"name":"efb9116e","tag_name":"efb9116e","created_at":"2022-07-01T19:37:54.053Z","link":"https://git.magmafoundation.org/api/v4/projects/7/packages/maven/org/magmafoundation/Magma/1.12.2-efb9116e/Magma-1.12.2-efb9116e.jar","installer_link":"https://git.magmafoundation.org/api/v4/projects/7/packages/maven/org/magmafoundation/Magma/1.12.2-efb9116e/Magma-1.12.2-efb9116e.jar","git_commit_url":"https://git.magmafoundation.org/magmafoundation/Magma/commit/efb9116e"}
It would be great if you could help look for or create an issue with them for their API.
Why not just run Magma jar instead of forge installation? Magma provides production ready jar without installation needed and server works fine.
Some versions truly need to be installed in order to prepare dependencies. When you download Forge manually, are you downloading the installer or a jar ready to go?
Besides, it's the principle of it. If their API is saying it's an installer link then it should be an installer jar. If there's no installer and the server jar is runnable as is, then the API should say so.
Some versions truly need to be installed in order to prepare dependencies. When you download Forge manually, are you downloading the installer or a jar ready to go?
Besides, it's the principle of it. If their API is saying it's an installer link then it should be an installer jar. If there's no installer and the server jar is runnable as is, then the API should say so.
I downloaded Magma jar(outside of the Docker container) and started it by java -jar magma.jar
and server works out of the box with mod and plugins funcionality.
OK, I was making a broader point, but I'll just queue up a fix to work around their broken API.
Some versions truly need to be installed in order to prepare dependencies. When you download Forge manually, are you downloading the installer or a jar ready to go?
Besides, it's the principle of it. If their API is saying it's an installer link then it should be an installer jar. If there's no installer and the server jar is runnable as is, then the API should say so.
Magma has an integrated installation tool (like installer.jar --installServer) we also download and load every dependency with that. We completely replaced the installer jar and dont provide that installer anymore. Unfortunally, the API doesnt show if it's a server or installer, as our release files are not labeled with server or installer (only for 1.12) because 1.12 is only a serverJar. I will see, if we can improve the API.
Side note: We did the same with 1.18, only this is still in beta with no official release. There we will still provide both, serverjar and Installer.
Best regards Malcolm ~ MagmaFoundation Mod and Dev
Unfortunally, the API doesnt show if it's a server or installer, as our release files are not labeled with server or installer (only for 1.12) because 1.12 is only a serverJar. I will see, if we can improve the API.
Thanks @m1lc0lm . For now I can work around the issue by checking if the two links equal and use it as a server jar.
@m1lc0lm is the server jar self-installing for 1.16.5 also? I'm starting to get harassed by users 😒, so I am becoming not happy with providing Magma support.
...and for future reference, the API response for 1.18 is broken in the other direction. The link
is pointing to an installer, which is wrong:
curl -fsSL https://api.magmafoundation.org/api/v2/1.18/latest | jq
{
"name": "63cbeee2",
"tag_name": "63cbeee2",
"created_at": "2022-07-19T19:14:21.146Z",
"link": "https://git.magmafoundation.org/api/v4/projects/5/packages/maven/org/magmafoundation/Magma/1.18.2-40.1.54-63cbeee2/Magma-1.18.2-40.1.54-63cbeee2-installer.jar",
"installer_link": "https://git.magmafoundation.org/api/v4/projects/5/packages/maven/org/magmafoundation/Magma/1.18.2-40.1.54-63cbeee2/Magma-1.18.2-40.1.54-63cbeee2-installer.jar",
"git_commit_url": "https://git.magmafoundation.org/magmafoundation/Magma-1-18-x/commit/63cbeee2"
}
@m1lc0lm is the server jar self-installing for 1.16.5 also? I'm starting to get harassed by users 😒, so I am becoming not happy with providing Magma support.
Yes. Atm 1.12 and 1.16 is self installing. We have beta build of 1.18 self installing. But its not available over the api. But it will in a few days.
Excellent. That means the changes I pushed last night will work fine for 1.18 when your side is done.
Yes. Should work then.
Magma 1.18 is available over the api. You can just pull it from there. Its also self installing so :)) I dont know if you noticed that.
{ "name": "695a1617", "tag_name": "695a1617", "created_at": "2022-12-10T23:57:56.294Z", "link": "https://git.magmafoundation.org/api/v4/projects/5/packages/maven/org/magmafoundation/Magma/1.18.2-40.1.86-695a1617/Magma-1.18.2-40.1.86-695a1617-server.jar", "installer_link": "https://git.magmafoundation.org/api/v4/projects/5/packages/maven/org/magmafoundation/Magma/1.18.2-40.1.86-695a1617/Magma-1.18.2-40.1.86-695a1617-installer.jar", "git_commit_url": "https://git.magmafoundation.org/magmafoundation/Magma-1-18-x/commit/695a1617" }
use link as before. URL hasnt changed
Describe the problem
I tried to run Magma server but docker log stuck on Forge installation. Between at the same time, the server itself is launched in the background. (I saw that by forge installer log file and HTOP)
(Forge installer log)
Container definition
Container logs