Creating rails app project with Docker tutorial

[anaschwendler]

Hello everyone 👋

I've been using Docker to run rails projects in the lasts months, so I was planning to write a tutorial on how to create/run a project using docker, maybe it would be interesting because you don't need to deal with the installation part, just install docker and good to go :)

I would like to know if makes sense to add it here, if it is something that we can consider, and where it would make more sense in the installation section, separate tutorial...

Thanks! 🎉

[vesan]

I find it a welcome addition.

Would it be best to have a separatistien tutorial which would tell why you might be interested taking the Docker route and how to do it? Then include a paragraph in the installation guide that tells about the existence of the guide.

[milazangirolame]

i would love to see this tutorial

[anaschwendler]

Awesome! I'll finish that soon ;)

[Lancemccurdy]

That was painless....

[aknrdureegaesr]

Interesting project!

How do you intend to do the editing?

Possible route: Install Atom on the host and use a directory on the host as a volume in the Docker container.

But then, you have somewhat of a permissions mess at your hands. What's user "A" on the host may be user "B" in the container. So what one of the two writes, the other may or may not be able to change. The particular problems encounter are different, depending on the host's OS.

Personally, I'm most familiar with the Linux-host-situation. For one project, I've mitigated this problem by adding a user to the Docker container that has the same numerical id as that of the user on the host wanting to use that container. But I had some scripting language I could use on the outside.

Other route: Install a text-mode editor in the Docker container. In that case, you may want to teach people how to open different host console windows into the same container using docker exec -ti. There is also a certain danger of work becoming unaccessible in the absence of the container (which may or may not be acceptable for the purpose of a one-day workshop). Text-only work will be appealing only to some participants; maybe a minority.

Yet another route: Install a graphic user interface in the Docker container. Xvnc + novnc together allow any modern browser to access an X session. This still needs to address the issue of data becoming unaccessible when the container is removed. Also, cut+paste keyboard shortcuts are different between Mac and the rest of the world, which can drive people nuts.

Yet another route: Have samba, NFS or the like in the Docker container and use that to negotiate content between host and container. Or vice versa, something on the host exported into the container.

Whatever. I'm curious what you will come up with.

[aknrdureegaesr]

FWIW: moby/moby#3124 is pertinent.

[anaschwendler]

Hello @aknrdureegaesr!

I'm so sorry that I haven't finish that yet, I really need to get back to it!
I end up moving to Berlin this year, and end up not finishing that.

Thanks for the reminder, now that I'm more setup here, I'll do my best to get back to that on this weekend, I really want to do that! Soon I'll have news!

Thanks everyone!