Is there any documentation for electing to host on AWS and not Glitch? Would the commercial or non-commercial be its own containerized instance?
by user 1102644126509453332
Is there any documentation for electing to host on AWS and not Glitch? Would the commercial or non-commercial be its own containerized instance?
by user 1102644126509453332
Hey, the client-side parts are super easy to host as typically you just upload your build folder. Thereās docs for various deployment options, but not specifically for AWS yet: Deployment & Compression | Needle Engine Documentation
Are you looking at just client-side code or also server-side (e.g. networking)? Would love to learn more about your usecase.
Hey, thank you for the Insite @herbstšµ , I suppose Iām looking for a use case hosting server side, Iām wanting to have a container instance, Is there a process to configure in the deployment process in Unity?
by user 1102644126509453332
With āserver sideā you mean running multiplayer networking code or just hosting? Just want to make sure weāre talking about the same thing
Thereās an API to make builds and thereās also command line flags for automated builds
On top of that you can make your own ādeployment componentsā similar to the one we already ship
Well I might be asking the wrong question, sorry about that. What I mean is deployment targeting. I suppose I am confused about targeting perhaps. In the process of build to folderā¦is there any step by step to change the configuration in unity and uploading directly to a hosted web server. Iām not very concerned about multi player networking yet. Thank you so much @herbstšµ . At the moment I am using Glitch, and I would like to know best practices for this use case.
by user 1102644126509453332
So the āsuper quick getting startedā is that you
This is amazing!! :PandaNorm: Needle is that versitle and easy to deploy! Thank you @herbstā:cactus:
by user 1102644126509453332
Youāre welcome! In the docs above that would be the āBuild to folderā approach, all the others are basically wrappers that first build to a folder and then upload the result somewhere for you
Changed the channel name: Deploying to AWS