-
-
Notifications
You must be signed in to change notification settings - Fork 229
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
Make it easier to enter a URL during ghost config
#812
Labels
Comments
ErisDS
added a commit
to ErisDS/Ghost-CLI
that referenced
this issue
Sep 5, 2018
closes TryGhost#812 - When entering a URL, add a protocol if one is missing - Follow the rules laid out in TryGhost#812, so that we use https by default where possible - Also handle domains entered with // at the start
As a side note this actually might allow us to upgrade our version of validatorjs, which is currently pinned a few major versions behind due to them changing the url validation. Not that we have to update it, but if this change allows us to we might as well. |
ErisDS
added a commit
to ErisDS/Ghost-CLI
that referenced
this issue
Sep 6, 2018
closes TryGhost#812 Update url handling behaviour: - When entering a URL, add a protocol if one is missing - Follow the rules laid out in TryGhost#812, so that we use https by default where possible - Also handle domains entered with // at the start Swap to using url util - moved all old usages of validate-instance-url
ErisDS
added a commit
to ErisDS/Ghost-CLI
that referenced
this issue
Sep 7, 2018
closes TryGhost#812 Update url handling behaviour: - When entering a URL, add a protocol if one is missing - Follow the rules laid out in TryGhost#812, so that we use https by default where possible - Also handle domains entered with // at the start Swap to using url util - moved all old usages of validate-instance-url
acburdine
pushed a commit
that referenced
this issue
Sep 9, 2018
closes #812 Update url handling behaviour: - When entering a URL, add a protocol if one is missing - Follow the rules laid out in #812, so that we use https by default where possible - Also handle domains entered with // at the start Swap to using url util - moved all old usages of validate-instance-url
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At present we expect a fully formatted URL to be entered during
ghost config
including the protocol. However, we don't really make that clear in all cases and it's not really required. It's perfectly reasonable for me to entermysite.com
and expect that the CLI would add the https part for me along with setting up SSL.Instead, what happens currently is the CLI complains the URL isn't valid 😞
I think we should add protocols to the URL according to the following rules:
http
https
Note: we are moving as fast as we can towards only supporting http for development - all Ghost blogs should be run fully HTTPS in production.
The text was updated successfully, but these errors were encountered: