Guide deploy ghost #699
Guide deploy ghost #699
Conversation
✅ Review app deployedCheck how your changes look like!
|
davlgd
force-pushed
the
guide-ghost-blog-documentation
branch
from
3e84fdf to
0b3a36e
Compare
davlgd
force-pushed
the
guide-ghost-blog-documentation
branch
from
0b3a36e to
ab05e2f
Compare
davlgd
force-pushed
the
guide-ghost-blog-documentation
branch
from
ab05e2f to
00e7b42
Compare
davlgd
force-pushed
the
guide-ghost-blog-documentation
branch
from
00e7b42 to
9782ba1
Compare
|
|
||
| ## Installation and Configuration | ||
|
|
||
| ### Initialize Your Project |
There was a problem hiding this comment.
As this part is mostly moving files/editing config of the Ghost project, maybe we could just:
- Do it in a Clever Cloud repo
- Provide the preconfigured repo link, users just have to clone it
- Provide users needing more info about Ghost and how it works a link to Ghost doc
| clever addon create mysql-addon --plan s_sml myblogsql | ||
| clever service link-addon myblogsql |
There was a problem hiding this comment.
you can link it at add-on creation
| ```sh | ||
| clever env set database__connection__host <ADDON_HOST> | ||
| clever env set database__connection__user <ADDON_USER> | ||
| clever env set database__connection__password <ADDON_PASSWORD> | ||
| clever env set database__connection__database <ADDON_DATABASE> | ||
| clever env set database__connection__port <ADDON_PORT> | ||
| clever env set url https://<domain_URL_blog> |
There was a problem hiding this comment.
Use a binding script, as we do in oTree guide for example. If the user changes the add-on or if config changes, it will still work
There was a problem hiding this comment.
Create a .sh script with the env variables directly to make everything more persistent?
| clever addon create cellar-addon --plan s_sml <cellar-app> | ||
| clever service link-addon <cellar-app> |
There was a problem hiding this comment.
Link at creation
If you use a binding script maybe you can:
- Create add-ons
- Create the binding script
- Configure env
There was a problem hiding this comment.
I don't understand, you want me to put a script to execute directly?
| clever env set mail__from "[email protected]" | ||
| clever env set mail__options__service "your-mail-service" # e.g. Mailgun, Gmail, etc. | ||
| clever env set mail__options__host "smtp.yourmail.com" | ||
| clever env set mail__options__port "587" | ||
| clever env set mail__options__secureConnection "false" | ||
| clever env set mail__options__auth__user "your-smtp-username" | ||
| clever env set mail__options__auth__pass "your-smtp-password" |
There was a problem hiding this comment.
Is there a way to use mailpace here ? Maybe we can use a tab to show how to setup both classic SMTP and Mailpace?
| git remote add clever <CLEVER_GIT_URL> | ||
| git push clever <branch>:master |
|
|
||
| ## More Information | ||
|
|
||
| For a small blog, you can use the XS or S Node.js plan. |
There was a problem hiding this comment.
Maybe provide this info as a [!TIP] when we tell the user how to create the application
Co-authored-by: David Legrand <[email protected]>
Co-authored-by: David Legrand <[email protected]>
Co-authored-by: David Legrand <[email protected]>
|
@Juju-archy Thanks for the changes. I use this PR to test something for guides, I'll get back to you on it later this week. |
2 participants
Describe your PR
Guide to deploy Ghost Blog (Node.js, Cellar, MySQL) on Clever Cloud
Checklist
Reviewers
Who should review these changes? @CleverCloud/reviewers