-
Notifications
You must be signed in to change notification settings - Fork 72
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
Migrate Flask tutorial to Charmcraft RTD #1976
base: main
Are you sure you want to change the base?
Conversation
added a few commands taken from the rockcraft task.yaml
skipped over the parts where code files were changed (for now)
24.04 blueprint
Move setup text to its own file Fix some linting issues
migrate.py visitors_app.py
So that the spread test won't pick it up too early in the test (causing a blocked status in the flask-hello-world app)
|
||
.. code-block:: bash | ||
|
||
sudo snap install charmcraft --channel latest/edge --classic |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we use latest/edge
here or switch to stable? Rockcraft above is using stable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does the stable
version of charmcraft support all the extensions? For Flask it does, but since this is under reuse
I wanted to make sure the setup was as extension-agnostic as possible
# [docs:deploy-juju-model-end] | ||
|
||
# [docs:deploy-nginx] | ||
juju deploy nginx-ingress-integrator --channel=latest/edge --revision 122 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any particular reason for pinning the revision please? I think lates/edge
should get the latest revision
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
latest/edge
did not get the latest revision in the GitHub CI test -- it did for my local testing though.
In GitHub, latest/edge
grabbed revision 44 (suspiciously, this is the latest revision for the Ubuntu 22.04 base
while 122 is the latest revision for the Ubuntu 20.04 base
) and revision 44 ran into hook failed: "config-changed"
errors upon deployment
One other thing to note: When I specified the base
instead of revision
, the "hook failed" issues went away.
docs/tutorial/flask.rst
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see the tutorial being rendered, but there isn't a dedicated tutorial section. I can reorganise
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added a tutorial section, and the Flask tutorial shows up underneath it when I check the rendered page. Let me know if you don't see it
Thanks for doing this, I know it isn't easy especially because this involved code 🙂 |
The current Flask tutorial: https://juju.is/docs/sdk/write-your-first-kubernetes-charm-for-a-flask-app
This PR will move the tutorial off of Discourse and Charm SDK and onto the Charmcraft RTD.