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

Add MySQL App Service / ACA - fix typos and styles #48

Open
wants to merge 23 commits into
base: main
Choose a base branch
from

Conversation

john0isaac
Copy link
Contributor

@john0isaac john0isaac commented Feb 6, 2024

Purpose

  • Add Flask MySQL XX App Service
  • Add Flask MySQL XX ACA
  • fix small typos and styles

After building this I used Cookiecutter to generate the repo I previously created and there were no changes in the code.

Does this introduce a breaking change?

[X] Yes
[ ] No

Pull Request Type

What kind of change does this Pull Request introduce?

[ ] Bugfix
[X] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

@john0isaac
Copy link
Contributor Author

Commits after this comment are related to ACA setup as it's built on top of the mysql setup

@john0isaac john0isaac changed the title Add MySQL App Service and fix small typos and styles Add MySQL App Service / ACA and fix small typos and styles Feb 6, 2024
@john0isaac john0isaac changed the title Add MySQL App Service / ACA and fix small typos and styles Add MySQL App Service / ACA - fix typos and styles Feb 6, 2024
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I remember this is due to a known issue - @john0isaac do you have the link to this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

{% endraw %}
architecture: x64
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this going to be a problem when testing against ARM?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change is not needed but I asked myself why are we disabling interpretation for architecture: x64
it's not related to jinja syntax so, it's safe to do it like that and the wrapping was not needed.

@@ -81,6 +82,8 @@ To request support please create a [new discussion](https://github.com/kjaymille
- [Flask Azure Container Apps Postgres Addon Azure Container Apps](https://github.com/Azure-Samples/azure-flask-postgres-addon-aca)
- [Flask CosmosDB - MongoDB Adapter Azure Container Apps](https://github.com/Azure-Samples/azure-flask-cosmos-mongodb-aca)
- [Flask CosmosDB - MongoDB Adapter Azure App Service](https://github.com/Azure-Samples/azure-flask-cosmos-mongodb-appservice)
- [Flask MySQL - Flexible Server Azure App Service](https://github.com/john0isaac/azure-flask-mysql-flexible-appservice)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is a temporary good choice to include working samples. In the long term. There should be samples that are created in the Azure-Samples Repo

error: django.db.utils.OperationalError: (2002, Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2))
Django has the same env vars for development and production. My production env vars started with Azure_something which made django deployment fail
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

Successfully merging this pull request may close these issues.

None yet

2 participants