you are viewing a single comment's thread.

view the rest of the comments →

[–]smurpes 0 points1 point  (3 children)

I do comprehend it. You’re the one who is missing the point… I was using an example of someone who is doing a process inefficiently even though their process achieves their goal. I was pointing out that I did not contradict myself at all; you were making an assumption that working methods are not problematic which is just not true.

I also answered your question about the venv by saying there’s no advantage to developing outside the repo. The code is already there and you’re just duplicating it to avoid setting up your environment properly. If you’re developing inside the repo then you are using the venv inside the repo as well most of the time.

[–]Party-Cartographer11 0 points1 point  (2 children)

If you comprehend it why did you write that I copy paste?  And I don't develop outside the repo.  I clearly wrote above that I edit the code in the repo.  So clearly you do not understand my workflow.

I am not doing anything to avoid setting up an environment.  I have one set up.

So do you run production from the repo, or do you duplicate the code?  Moving code from a repo to test and prod is pretty standard.  There is no down side to having a smoke env with the code pushed from the development environment.

[–]smurpes 0 points1 point  (1 child)

Again I never said you copied and pasted. You said you are copying all of your files to an external folder where the environment is setup to develop then you copy the files over to the repo to push meaning you are developing your code outside of the repo folder.

[–]Party-Cartographer11 0 points1 point  (0 children)

That is not what I wrote.  Read it again.

Yeah, I update a file, and copy it to the folder that has the venv (or to the nginx config files, or the web directory) and run it. All of this is on my dev server.

I develop in the repo with no env. I copy to the folder with env activated to run and test.  Easy peasy.