This repository was archived by the owner on Dec 3, 2019. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 3, 2019. It is now read-only.
Instructions on a native setup added to the readme #278
Description
Feature
Why is this feature being added?
When using this repo locally, you can do so via Docker, a AWS VM, or through a native setup. We currently have instructions for the first two, but not the latter.
What should your feature do?
Create a set of instructions for setting up this repo natively. Follows the pattern laid out in #277
Activity
aamarill commentedon May 23, 2018
Hello @hpjaj can I get started on this issue? 😄
hpjaj commentedon May 23, 2018
@aamarill - it's yours!
aamarill commentedon Jun 4, 2018
@hpjaj I apologize for the delay on this!
If you see someone else looking for work, please have them give me a hand with this.
Feel free to update the "status" label to "available".
I don't think I am going to have too much spare time in the coming weeks.
Thanks! 😄
aamarill commentedon Jul 10, 2018
@hpjaj So sorry for the delay on this, but I don't think I can work this anymore. I recommend that you please update the status to "available". In addition, you may want to add a "beginner friendly" tag 😅
Thank you for the opportunity to contribute!
robbkidd commentedon Aug 21, 2018
Would a hybrid native/docker/docker-compose development environment work? Wherein the Ruby bits—the web service running in development mode, minitest tests, rubocop, etc—run on the host while services that the backend depends on (Postgres, Redis) continue to run in docker containers. Would that meet the desire for a "native" development environment?
dmarchante commentedon Aug 21, 2018
good question. I will have to pull in eyes more familiar with this. @nellshamrell @hollomancer ?
robbkidd commentedon Aug 21, 2018
Scoping questions: Is the goal to ...
... avoid requiring a developer to install Docker?
... enable a developer to run the Ruby portions of the backend in a more direct way on their host to ease console access or running a debugger?
What challenges have developers had with docker- and cloud-based development environments that a native setup would address?
dmarchante commentedon Aug 21, 2018
... avoid requiring a developer to install Docker?
Potentially, we are trying to be as beginner friendly as possible. Additionally, I anticipate learners will want to know how to set up the environment locally.
... enable a developer to run the Ruby portions of the backend in a more direct way on their host to ease console access or running a debugger?
@nellshamrell @hollomancer
What challenges have developers had with docker- and cloud-based development environments that a native setup would address?
This goes back to the beginner issue who may want to get rid of as much complexity as possible, or focus on getting set up and run Ruby natively. We just want to provide the options since we have a diverse group of reasons and skill levels who are wanting to contribute.
@robbkidd These are some great questions that we should think about. Let's wait for input from Nell and Conrad before moving forward.
jjhampton commentedon Aug 21, 2018
@robbkidd I suspect that your second option was one of the goals - 'enable a developer to run the Ruby portions of the backend in a more direct way on their host to ease console access or running a debugger'. I'm thinking that we want setup/running of the back-end to be something that is easy and accessible even for beginner devs. I don't have any details as I'm not very active on the back-end team here, but I've seen beginners post questions about difficulties with Docker in our Slack a few times.
It feels like we just want to give developers (especially beginners) more options instead of tying them down to only one type of environment.
leenyburger commentedon Aug 22, 2018
@robbkidd @jjhampton @dmarchante - @hpjaj helped me set this up natively when I first got involved and it really helps beginning developers to not have to mess with Docker. Plus
byebugand Docker aren't friends. It's intimidating to runmakecommands when you're still figuring outrakecommands. The steps are something like this:Add 127.0.0.1 operationcode-psql
to your /etc/hosts file enables you to run Rails app that uses Docker, without Docker.
apex-omontgomery commentedon Sep 14, 2018
Looks like having a variety of options is a good choice.
I understand that docker is daunting for many people, but I feel that it adds so much easy into the process (don't have to modify hosts, don't have to install postgres) but it does add some pain.
A hybrid setup would allow easier debugging, and allow abstracting all the other things?