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.

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

Understanding how the solution is deployed with bicep and which port used by default #2236

Open
gtedavid opened this issue Dec 15, 2024 · 1 comment

Comments

@gtedavid
Copy link

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ x ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

  • Copy frontend and backend folders
  • Create dockerfile to install dependancies

Any log messages given by the failure

Expected/desired behavior

Fully functional web site

OS and Version?

Windows 11 (deployed from)
Executed on a Linux system (Bullseye)

azd version?

run azd version and copy paste here.
(not the case here)

Versions

Mention any other details that might be useful

First question and context : deployment via bicep
I'm trying to deploy the application without bicep. I'm also trying to understand how or what does the bicep or azd do to deploy the entire code to the web app.

What are the actions done by the Bicep to upload the app folder, knowing that it doesn't exist afterwards in the webapp ?

Second questions : port used by the application
What ports do gunicorn, the python backend and the front use ?


Thanks! We'll be in touch soon.

@gtedavid gtedavid changed the title Understanding how the Dockerised solution and solution deployed without bicep Understanding how the solution is deployed with bicep and which port used by default Dec 15, 2024
@Teravla
Copy link

Teravla commented Dec 19, 2024

Up

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants