Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DEV-6316 Issue with Exercise CRUD-Master Instructions and File Structure #2815

Merged
merged 1 commit into from
Dec 3, 2024
Merged

DEV-6316 Issue with Exercise CRUD-Master Instructions and File Structure #2815

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions subjects/devops/crud-master-py/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -284,13 +284,13 @@ a common way to structure this kind of projects that may help you:
│ │ │ ├── __init__.py
│ │ │ └── ... // Other python files
│ │ ├── requirements.txt
│ │ └── server.js
│ │ └── server.py
│ ├── billing-app
│ │ ├── app
│ │ │ ├── __init__.py
│ │ │ └── ... // Other python files
│ │ ├── requirements.txt
│ │ └── server.js
│ │ └── server.py
│ └── inventory-app
│ │ ├── app
│ │ │ ├── __init__.py
Expand All @@ -302,7 +302,7 @@ a common way to structure this kind of projects that may help you:

When testing and before automating it through the VM build you should be able
to start the API Gateway and the two APIs by using the command `python
server.js` inside their respective directories.
server.py` inside their respective directories.

As a best practice, you should develop your APIs using separates python virtual
environments to isolate the requirements needed for each API. You can use
Expand Down
Loading