|
| 1 | +# Lab |
| 2 | + |
| 3 | +1. Clone git repo: `git clone https://github.com/ibm-developer-skills-network/sfvih-Back-end-Development-Capstone.git` |
| 4 | +2. Get into the directory by `cd sfvih-Back-end-Development-Capstone` |
| 5 | +3. Get into Django code `cd djangoserver` |
| 6 | +4. Install requirements `pip install -r requirements.txt` |
| 7 | +5. Run the server `python manage.py runserver` |
| 8 | +6. It will tell you that you have unapplied migrations. |
| 9 | + |
| 10 | + **Migrations** are Django’s way of propagating changes you make to your models (adding a field, deleting a model, etc.) into your database schema. They’re designed to be mostly automatic, but you’ll need to know when to make migrations, when to run them, and the common problems you might run into. There are several commands which you will use to interact with migrations and Django’s handling of database schema: |
| 11 | + |
| 12 | + 1. **_migrate_**, which is responsible for applying and unapplying migrations. |
| 13 | + 2. **_makemigrations_**, which is responsible for creating new migrations based on the changes you have made to your models. |
| 14 | + 3. **_sqlmigrate_**, which displays the SQL statements for a migration. |
| 15 | + 4. **_showmigrations_**, which lists a project’s migrations and their status. |
| 16 | + |
| 17 | +7. Create the initial migrations and generate the database schema: |
| 18 | + |
| 19 | + ```shell |
| 20 | + python manage.py makemigrations |
| 21 | + python manage.py migrate |
| 22 | + ``` |
| 23 | + |
| 24 | +8. Run server successfully this time: `python manage.py runserver` |
| 25 | +9. Launch Application |
| 26 | +10. Click on Songs and Photos |
| 27 | +11. Click on Concerts, no existing Concert present |
| 28 | +12. Let's create admin user `python manage.py createsuperuser` |
| 29 | + 1. Username: `admin` |
| 30 | + 2. Email address: _leave blank, simply press enter_ |
| 31 | + 3. Password: Your choice, or simply `qwerty123` |
| 32 | +13. Run the server again `python manage.py runserver` and goto admin: `http://localhost:8000/admin/` |
| 33 | +14. Enter the admin user details you created in previous step. |
| 34 | +15. Now you are in the admin section built by Django. |
| 35 | +
|
| 36 | + One of the most powerful parts of Django is the **automatic admin interface**. It reads metadata from your models to provide a quick, model-centric interface where trusted users can manage content on your site. The admin’s recommended use is limited to an organization’s internal management tool. It’s not intended for building your entire front end around. |
| 37 | +
|
| 38 | +16. Add a Concert: |
| 39 | + 1. Concert name: `Coachella 2023` |
| 40 | + 2. Duration: `72` |
| 41 | + 3. City: `Indio, California` |
| 42 | + 4. Date: `2023-04-14` |
| 43 | +17. Click on `View Site` meny at the top |
| 44 | +18. Now if you visit `Concerts`, you will see Coachella listed. |
| 45 | +19. Our Django application is now running, but Songs and Photos are hard coded. |
| 46 | +20. Open `concert\views.py` |
| 47 | +21. See `songs` and `photos` definition. |
| 48 | +
|
| 49 | + 1. Retrieve `songs` from a REST endpoint by replacing the code with following: |
| 50 | +
|
| 51 | + ```python |
| 52 | + songs = req.get( |
| 53 | + "https://raw.githubusercontent.com/captainfedoraskillup/private-get-songs/main/backend/data/songs.json").json() |
| 54 | + return render(request, "songs.html", {"songs": songs}) |
| 55 | + ``` |
| 56 | +
|
| 57 | + 2. Retrieve `photos` from a REST endpoint by replacing the code with following: |
| 58 | +
|
| 59 | + ```python |
| 60 | + photos = req.get( |
| 61 | + "https://raw.githubusercontent.com/captainfedoraskillup/private-get-pictures/main/backend/data/pictures.json").json() |
| 62 | + return render(request, "photos.html", {"photos": photos}) |
| 63 | + ``` |
| 64 | +
|
| 65 | +22. Verify Songs and Photos changes. Visit the Songs section, you will see a longer list of songs, clicking on each will show its Lyrics in a modal dialog. While going into Photos, you will see more than two. |
| 66 | +23. Now back to Concerts, click on the concert Coachella we created. You will see an RSVP page. |
| 67 | +24. RSVP Page shows you details of the Concert along with an option to either: Attend, Not Attend or no Option `-`. |
| 68 | +25. If you open `concert_detail.html`, you will see an html form: |
| 69 | +
|
| 70 | + ```html |
| 71 | + <form action="{% url 'concert_attendee' %}" method="POST"> |
| 72 | + {% csrf_token %} |
| 73 | + <input |
| 74 | + name="concert_id" |
| 75 | + type="number" |
| 76 | + value="{{concert_details.id}}" |
| 77 | + hidden="hidden" |
| 78 | + /> |
| 79 | + <div class="input-group mb-3"> |
| 80 | + <label class="input-group-text" for="attendee_choice">RSVP</label> |
| 81 | + <select class="form-select" name="attendee_choice" required> |
| 82 | + {% for attending_choice in attending_choices %} |
| 83 | + <option {% if attending_choice.0 == status %}selected {% endif %} value="{{ attending_choice.0 }}">{{ attending_choice.1 }}</option> |
| 84 | + {% endfor %} |
| 85 | + </select> |
| 86 | + </div> |
| 87 | + <input type="submit" class="btn btn-primary" /> |
| 88 | + </form> |
| 89 | + ``` |
| 90 | +
|
| 91 | +26. On `Submit` of this form, the details are sent to `concert_attendee` in `concert\views.py`. |
| 92 | +27. It does two validations: |
| 93 | + `if request.user.is_authenticated:` means whether the user is authenticated. Because anonymous users are not allowed to RSVP. |
| 94 | + Then `if request.method == "POST":` to check whether it is an `HTTP POST` event. |
| 95 | +28. From the `body` of the `POST` method, it takes `concert_id` and `attendee_choice`. |
| 96 | +29. Then it checks, whether a selection was made previously, if yes, then update it. Otherwise insert new selection the databaes for this user. |
| 97 | +30. Finally, redirect the user. |
| 98 | +
|
| 99 | +## Cleanup while testing |
| 100 | +
|
| 101 | +```shell |
| 102 | +find . -path "*/migrations/*.py" -not -name "__init__.py" -delete |
| 103 | +find . -path "*/migrations/*.pyc" -delete |
| 104 | +find . -path "*/db.sqlite3" -delete |
| 105 | +python manage.py makemigrations |
| 106 | +python manage.py migrate |
| 107 | +python manage.py runserver |
| 108 | +``` |
| 109 | +
|
| 110 | +## To move the data from SQLite to MySQL |
| 111 | +
|
| 112 | +Execute: |
| 113 | +
|
| 114 | +`python manage.py dumpdata > datadump.json` |
| 115 | +
|
| 116 | +Next, change your `settings.py` to the mysql database. |
| 117 | +
|
| 118 | +Finally: |
| 119 | +
|
| 120 | +`python manage.py loaddata datadump.json` |
| 121 | +
|
| 122 | +## Containerize the application |
| 123 | +1. build a docker image |
| 124 | + ``` |
| 125 | + docker build . -t concert |
| 126 | + ``` |
| 127 | +1. tag docker image with the correct registry information |
| 128 | + ``` |
| 129 | + docker tag concert captainfedora/concert:v1 |
| 130 | + ``` |
| 131 | + The above command tags to `captainfedora` repository on dockerhub with the image name of `concert` and label of `v1` |
| 132 | +
|
| 133 | +1. Run the docker image to validate everything is working |
| 134 | + ``` |
| 135 | + docker run -p 8000:8000 captainfedora/concert:v1 |
| 136 | + ``` |
0 commit comments