Configuring Ghost for the first time

Same here. Local ghost install. Create user(s). Lock out other users. No email configured. Not sure exactly where to go with this.

[grid]

@justinacolmena , For a local install and if you just want to create site members, just do that in the dashboard. (I assume you want members not users, because that’s what your image shows.)

? Enter your blog URL: http://localhost:2368/
? Enter your MySQL hostname: localhost
? Enter your MySQL username: ghost
...
Ghost was installed successfully! To complete setup of your publication, visit: 
    http://localhost:2368/ghost/

So the URI /ghost/ is the key to completing the setup.

Ah. I don’t think you’re posting on a thread that makes sense (the OP had a totally different question), but I’m glad you got it figured out.

(EDIT: Forked this discussion from the initial thread which was about a totally different question, as far as I can tell - sorry for any discontinuity that results.)

Could be. OP is rather vague, and I’m not being any more specific than that anyways. Thank you.


Make that publicly available on the internet for example.

So far so good, with Caddy to automatically configure ssl and reverse-proxy open internet connections at large to the “local” install at 127.0.0.1:2368. Configure the external url in config.production.json and on the theme site navigation.


Compare wordpress, but everything runs a little bit more refined, heavy-duty, and industrial strength on node rather than php. Interesting choice of database to go with mysql only and effectively dump mariadb. Postgresql seems to have somewhat limited web applications.

Email received from localhost installation. Actually

$ ssh -L 127.0.0.1:2368:127.0.0.1:2368 myuser@somehost.example.org

Must manually specify 127.0.0.1 rather than localhost because ghost is running on IPv4 loopback only, and IPv6 connections will stall if it is not listening on [::1]:2368 as well. So actually that was a remote install, but proxied over ssh to access locally. Once that was working, I added a rule reverse_proxy 127.0.0.1:2368 to the server section in the Caddyfile.