Contributing with Janitor #35
Comments
Hi! Thanks for the generous offer! I'll let some other devs chime in, but it looks like it would work quite well. Getting a Dockerfile going is trivial - we already use Docker in our normal build pipeline for Linux, so that shouldn't be too hard of a hurdle. Here is one which gets us most of the way: https://gist.github.com/j-selby/ae15ac5dafca1d8d56971e5007912daf |
Pretty straight forward dockerfile indeed. For the dockerfile, here are my edits :
Maybe we should add a EDIT: I just added yuzu with a temporary image (without building yuzu) to janitor to let you spawn and test containers. |
Super cool initiative! I see that most of the work to add Yuzu to Janitor is already done. Having the Dockerfile somewhere in this repo, and hooking the repo up as a Docker Hub automated build (takes like 3-5 clicks), would allow Docker Hub to detect any new commits to https://github.com/yuzu-emu/yuzu/ and rebuild the developer image automatically, keeping it up-to-date with no effort from anyone. Adding a Adding a |
P.S.
|
Hello! Thank you for reaching out to us. We'd love to schedule a phone call to discuss this further. Let us know when you are available! |
Hello,
We are hosting a platform named Janitor (https://janitor.technology) to bootstrap development containers for open-source projects.
We are interested into hosting the project and help you contribute faster.
I looked at your build instructions and it seems relatively simple to create a Dockerfile for our platform to clone the project, install all dependencies and build yuzu.
We feature a cloud IDE (powered by our own instances of Cloud9 IDE), Ubuntu containers running on bare metal servers, a desktop preview with noVNC and debug tools working out-of-the-box.
If you are interested in this idea, let's continue the discussion here for specific needs for your Dockerfile or meta questions. If you are not, feel free to close this issue.
Happy coding,
EtienneWan
The text was updated successfully, but these errors were encountered: