ehmatthes / django-simple-deploy

A reusable Django app that configures your project for deployment
BSD 3-Clause "New" or "Revised" License
307 stars 26 forks source link

Documenting a Test Run #218

Closed mgermaine93 closed 4 months ago

mgermaine93 commented 1 year ago

Thank you for documenting a test run of django-simple-deploy! In the pre-1.0 phase of development, every test run is a helpful data point. For more about test runs, please see Documenting a Test Run.

Please answer any or all of the following questions. The more information you share, the more easily we'll be able to integrate your feedback into the project.

Before completing the test run:

I'm using macOS Ventura, 13.2.1.

The sample blog project.

N/A.

I used the requirements.txt file in the sample blog project.

Heroku.

After you complete the test run, please answer the following questions in a followup comment:

I thought the documentation was quite helpful for a beginner like me. I was sitting next to you at PyCon when I went through the test deployment process, etc., so I feel you got a sense of all of my questions :)

See above.

For beginners, I think it would be helpful to illustrate when the user is supposed to have activated their virtual environment. This would probably involve adding in (b_env) to all of the lines of command line examples you have in the docs where the user is supposed to be using their virtual environment. That said, I think you already took care of this during PyCon, seen here.

Not a question, but more of a thought... I'd be interested in seeing django-simple-deploy applied to individual servers as well as platforms. I'm a bit biased, but this would have direct positive implications on my work at the moment, and would make things easier all around. But as with the above points, I think we talked about this in person at PyCon.