No edit summary |
Expanded on reasons to use separate Steam/Resonite accounts for a headless |
||
(7 intermediate revisions by 3 users not shown) | |||
Line 13: | Line 13: | ||
== Recommendations == | == Recommendations == | ||
Before you get started here are some recommendations: | Before you get started here are some recommendations: | ||
# Use a non-windows machine | # Use a non-windows machine | ||
# Use a separate machine | #* While this setup works for Windows, Docker on windows can break depending on your CPU, Operating System setup and even sometimes the motherboard. For less issues, stay off windows. | ||
# Use a separate Resonite account - | # Use a separate machine | ||
# Use a separate Steam account from the one you use to play games | #* It is not recommended to run a headless on the same machine that you run Resonite on. This could lead to performance issues for both clients if you run them both at the same time. | ||
# Use a separate Resonite account. Whether these are positives or negatives for you can vary. | |||
#* Separate login credentials | |||
#* Dedicated storage instead of sharing with your own | |||
#* Separate settings/banlist/allowed hosts, avoids potentially overriding each other | |||
#* Headless doesn't currently support 2FA for logins [https://github.com/Yellow-Dog-Man/Resonite-Issues/issues/253 Issue #253] so it will need to be disabled | |||
# Use a separate Steam account from the one you use to play games | |||
#* Separate login credentials especially if in a shared environment or using scripts to download updates | |||
#* Can more safely leave steam guard off if your setup doesn't stay logged in (ie docker) | |||
#* Avoids issues with conflicting logins | |||
== Install Docker & Docker Compose == | == Install Docker & Docker Compose == | ||
Line 29: | Line 38: | ||
#* If all goes well, you'll see a pleasant message from Docker telling you that everything worked. | #* If all goes well, you'll see a pleasant message from Docker telling you that everything worked. | ||
# Run <code>docker compose version</code> to verify that you also have Docker Compose, you should see the Docker Compose version printed. | # Run <code>docker compose version</code> to verify that you also have Docker Compose, you should see the Docker Compose version printed. | ||
== Docker Refresher == | |||
We have a separate page if you'd like information about [[Docker|Docker in general]]. | |||
== Get the Files == | == Get the Files == | ||
For this setup we'll be using some sample files that are available on a [ | For this setup we'll be using some sample files that are available on a [https://github.com/Yellow-Dog-Man/BasicDockerHeadlessSetup GitHub Repository]. So if you're familiar with git, you can probably leave off here and follow the directions there. | ||
But if you're not familiar with git, don't worry. You don't even need git, just keep reading right here on the wiki. | But if you're not familiar with git, don't worry. You don't even need git, just keep reading right here on the wiki. | ||
Line 68: | Line 81: | ||
# In the Terminal window enter <code>docker compose up</code> | # In the Terminal window enter <code>docker compose up</code> | ||
After this a huge amount of items should appear in the terminal, this might be overwhelming but just wait, after awhile(any where from 3 to 10 minutes) you should see: <code><nowiki>resonite-headless | World running...<nowiki></code>. | After this a huge amount of items should appear in the terminal, this might be overwhelming but just wait, after awhile(any where from 3 to 10 minutes) you should see: <code><nowiki>resonite-headless | World running...</nowiki></code>. | ||
This means your headless is running. | This means your headless is running. | ||
Line 99: | Line 112: | ||
== See Also == | == See Also == | ||
* [[Headless | * [[Headless Server Software/Setup|Setup a Headless]] - How to setup a headless for the first time | ||
* [[Headless | * [[Headless Server Software/Managing Worlds|Managing Worlds]] - Guidance on world management with a headless. | ||
* [[Headless | * [[Headless Server Software/Configuration File|Configuration File]] - Learn about Headless Configuration Files | ||
* [[Headless | * [[Headless Server Software/Commands|Commands]] - Learn about Headless Commands |
Latest revision as of 12:32, 21 May 2024
Thanks
This guide was made possible by Shadow Panther's Headless Image.
Prerequisites
- Basic familiarity with:
- Command Line Systems
- Configuration files including JSON familiarity
- Docker & Docker Compose
- A Patreon linked Resonite account that has access to the Headless Beta Code
- You only need ONE account to get the code.
- A spare Steam account
Recommendations
Before you get started here are some recommendations:
- Use a non-windows machine
- While this setup works for Windows, Docker on windows can break depending on your CPU, Operating System setup and even sometimes the motherboard. For less issues, stay off windows.
- Use a separate machine
- It is not recommended to run a headless on the same machine that you run Resonite on. This could lead to performance issues for both clients if you run them both at the same time.
- Use a separate Resonite account. Whether these are positives or negatives for you can vary.
- Separate login credentials
- Dedicated storage instead of sharing with your own
- Separate settings/banlist/allowed hosts, avoids potentially overriding each other
- Headless doesn't currently support 2FA for logins Issue #253 so it will need to be disabled
- Use a separate Steam account from the one you use to play games
- Separate login credentials especially if in a shared environment or using scripts to download updates
- Can more safely leave steam guard off if your setup doesn't stay logged in (ie docker)
- Avoids issues with conflicting logins
Install Docker & Docker Compose
- Visit Docker's Get Docker page
- Follow instructions for your operating system
- Ensure you also have Docker Compose. Depending on your setup, this may be included already but if not there's a Docker documentation page which has the details.
Test Docker Setup
To verify that docker is setup on your machine and working correctly:
- Open a terminal window
- Enter
docker run hello-world
- If all goes well, you'll see a pleasant message from Docker telling you that everything worked.
- Run
docker compose version
to verify that you also have Docker Compose, you should see the Docker Compose version printed.
Docker Refresher
We have a separate page if you'd like information about Docker in general.
Get the Files
For this setup we'll be using some sample files that are available on a GitHub Repository. So if you're familiar with git, you can probably leave off here and follow the directions there.
But if you're not familiar with git, don't worry. You don't even need git, just keep reading right here on the wiki.
- Download the files as a zip
- This zip comes directly from GitHub
- Extract the zip file
- You should now have a folder called "Headless"
Specifying some credentials
Next, we'll need to gather some credentials and place them in a file within the "Headless" folder.
So be prepared with your:
- Patreon Headless Code
- Username and Password to a spare Steam account
- The Steam account does not need to own any games
- The Steam account does not need to be a Resonite Patreon
- We recommend using a separate Steam account from the one you use to play Resonite.
- We recommend turning off Steam Guard to prevent issues when signing on. That can be done on Steam's Website.
With those prepared:
- Inside the "Headless" folder, create a new file called
.env
. - Add a line:
RES_HEADLESS_CODE=<Headless Code>
where<Headless Code>
is replaced by the Patreon Headless Code. - Add a line:
RES_STEAM_LOGIN=<Steam Username> <Steam Password>
where<Steam Username>
and<Steam Password>
- Save the file
Running a Headless
This is the last step, everything should be ready!
- Open a Terminal window in the Headless folder
- On Windows, this can be done by:
- holding shift and pressing right click in some empty space within the Headless folder in Windows Explorer
- selecting "Open PowerShell window here"
- On Linux, for common distributions such as Ubuntu you can right click in the folder browser and select "Terminal" or "Open Terminal".
- Editors Note: It's been awhile since i've been in Linux from the point of view as a new user, if someone can edit that in it would help. But keep in mind "New User" ProbablePrime (talk) 09:07, 13 March 2024 (UTC)'
- On Windows, this can be done by:
- In the Terminal window enter
docker compose up
After this a huge amount of items should appear in the terminal, this might be overwhelming but just wait, after awhile(any where from 3 to 10 minutes) you should see: resonite-headless | World running...
.
This means your headless is running.
Joining your Headless
Inside Resonite on your regular account:
- Open the world browser
- Select the "Headless Sessions" item on the left
- Type "Testing" into the search bar
- You should see your headless' session
- Click it
- Click Join
Limitations and where to go
Due to the simplicity of this guide, you'll probably notice a few things you'll want to change or correct, due to that here's a few links to get you started:
- Your world is just a simple grid world and you want it to be a custom world
- Replace the contents of "Config.json" with one of the example configuration files.
- Your Headless has a weird name
- This name is based on an internal part of the Docker runtime.
- To override it, simply add a Resonite user's username and password to one of our example configuration files.
- Or take a look at our configuration guide
- The Resonite account does not need to:
- Be a Patreon
- We Recommend using a separate Resonite account from the one you use on Resonite regularily.
- You want Builder permissions in your Headless
- Take a look at our configuration guide
- Your question isn't answered?
- Take a look at our configuration guide
- Ask on our Discord.
See Also
- Setup a Headless - How to setup a headless for the first time
- Managing Worlds - Guidance on world management with a headless.
- Configuration File - Learn about Headless Configuration Files
- Commands - Learn about Headless Commands