@@ -150,45 +150,59 @@ Django-Appointment now supports Docker, making it easier to set up, develop, and
150
150
you can quickly get the project running in a consistent environment, streamline the development process, and simplify
151
151
deployment across different platforms.
152
152
153
- # ## Getting Started with Docker
153
+ # ## Getting Started with Docker for Development or Local Testing
154
154
155
- To use Django- Appointment with Docker, follow these steps:
155
+ Using Django- Appointment with Docker is primarily intended for development purposes or local testing. This means you' ll
156
+ need to clone the project from the GitHub repository to get started.
156
157
157
- 1 . ** Prepare .env File** : Create an `.env` file in the root directory of your project with your configuration settings.
158
+ Here' s how you can set up Django-Appointment for local development or testing with Docker:
159
+
160
+ 1 . ** Clone the Repository** : Clone the Django- Appointment repository to your local machine:
161
+
162
+ ```bash
163
+ git clone https:// github.com/ adamspd/ django- appointment.git
164
+ ```
165
+ or using SSH :
166
+ ```bash
167
+ git clone git@ github.com:adamspd/ django- appointment.git
168
+ ```
169
+
170
+ 2 . ** Prepare .env File** : Create an `.env` file in the root directory of your project with your configuration settings.
158
171
You should include your email host user and password for Django' s email functionality:
159
172
160
173
```plaintext
161
174
EMAIL_HOST_USER =your_email@ gmail.com
162
175
EMAIL_HOST_PASSWORD =your_password
163
176
```
164
- 2 . ** Build and Run the Docker Containers** : Run the following command to build and run the Docker containers:
177
+ 3 . ** Build and Run the Docker Containers** : Run the following command to build and run the Docker containers:
165
178
166
179
```bash
167
180
docker- compose up - d -- build
168
181
```
169
182
170
- 3 . ** Create a Superuser** : After the containers are running, create a superuser to access the Django admin interface:
183
+ 4 . ** Create a Superuser** : After the containers are running, create a superuser to access the Django admin interface:
171
184
172
185
```bash
173
186
docker- compose exec web python manage.py createsuperuser
174
187
```
175
188
176
- 4 . ** Access the Application** : Once the containers are running, you can access the application at `localhost:8000 ` . The
189
+ 5 . ** Access the Application** : Once the containers are running, you can access the application at `localhost:8000 ` . The
177
190
Django admin interface is available at `localhost:8000 / admin` .
178
- 5 . ** Shut Down the Containers** : When you' re finished, you can shut down the containers with the following command:
191
+ 6 . ** Shut Down the Containers** : When you' re finished, you can shut down the containers with the following command:
179
192
180
193
```bash
181
194
docker- compose down
182
195
```
183
- 6 . ** (Optional) Run Migrations** : If you make changes to the models or database, you can run the migrations with the
196
+ 7 . ** (Optional) Run Migrations** : If you make changes to the models or database, you can run the migrations with the
184
197
following command:
185
198
186
199
```bash
187
200
docker- compose exec web python manage.py migrate
188
201
```
189
-
190
- > ** Note:** I use the default database settings for the Docker container. If you want to use a different database, you can
191
- modify the Dockerfile and docker- compose.yml files to use your preferred database.
202
+
203
+ > ** Note:** I use the default database settings for the Docker container. If you want to use a different database, you
204
+ > can
205
+ > modify the Dockerfile and docker- compose.yml files to use your preferred database.
192
206
193
207
# # Customization 🔧
194
208
0 commit comments