Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

One Click Coolify Deployment #53

Open
wants to merge 123 commits into
base: dev
Choose a base branch
from
Open

Conversation

HowieDuhzit
Copy link
Contributor

@HowieDuhzit HowieDuhzit commented Feb 25, 2025

This is my setup for world deployment I have been using to deploy worlds in seconds.

This allows for near single click deployment on self hosted coolify servers by pulling a docker image file built by the DockerFile.

Currently the compose file is building from a docker image i maintain that is just an up to date build of dev branch:
howieduhzit/hyperfy:latest

Compose Features:
All the ENV, Storage, and port setup is done automatically
ENVs not commonly edited are hardcoded for convenience.
Admin code and JWT are set at random
World persistence seperate from app persistence so the updates are clean without destroying worlds
Persistence includes changing world variable between worlds.

Ideally we should have a main/dev branch docker image built from the hyperfy docker account so we can deploy as hyperfy-xyz/hyperfy:main or hyperfy-xyz/hyperfy:dev

With this dockerfile its a simple as running
docker build -t hyperfy-xyz/hyperfy:main .
docker push hyperfy-xyz/hyperfy:main
or
docker build -t hyperfy-xyz/hyperfy:dev .
docker push hyperfy-xyz/hyperfy:dev
on each git push update

This allows for easy server updates by simply restarting the server to pull the latest image.

I will demo this at the next Hyperfy.How event to show how easy this makes deployment.

I also updated the public index and added the favicon and basic Hyperfy placeholder meta information for cleaner basic link sharing.

HowieDuhzit and others added 30 commits January 31, 2025 04:11
@HPrivakos
Copy link
Contributor

Ideally we should have a main/dev branch docker image built from the hyperfy docker account so we can deploy as hyperfy-xyz/hyperfy:main or hyperfy-xyz/hyperfy:dev

We do, it's hosted on github repo instead of docker repo though, so it's ghcr.io/hyperfy-xyz/hyperfy
You have:

I strongly disagree with the rollback to non-alpine node docker image, it unnecessarily make the image bigger while not adding any feature.

@HowieDuhzit
Copy link
Contributor Author

I fixed the dockerfile to be back in line with HP, updated the compose to use the main Image and also add a fix for the blackscreen issue with the app pane atm on dev branch

@jb0gie
Copy link

jb0gie commented Mar 1, 2025

KevinGatesRbsIntroGIF

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants