I recently got Ghost running after installing from source locally and the first thing I wanted to do was Login as a User.
I didn’t see any documentation about logging in as a seeded “test user” - does that exist somewhere?
The database has seeded users, including a ghost@example.com user, but I don’t know their passwords and would prefer not to be reverse engineering the hashed version just to get a cleartext pw I can use.
The alternative is that I create a new user, but to do that, I’d need to configure Mailgun, which is another config step that could be optional (or deferred for a bit, at least). The other downside to creating a new user is that I do not have any seeded content for that user (Posts, newsletters, members, etc) and would need to construct that state, as well.
To make things easier for people wanting to kick the tires on their local install, what is recommended to allow logging in as a seeded Test User (or am I missing somewhere that this is described)?
Thanks, yeah I can configure Mailgun to get it fully working, it was just another step in the process that I was hoping could be optional for local dev.
An example of how the seeded fixture test users could work:
The docs could have a list of Seeded Test Users with their email, password, and expected state:
Admin/Author
name@email.com
password here
Has a newsletter with subscribers, a few Posts, etc. (happy path state for testing a newsletter from the Author’s perspective)
Free Subscriber
name@email.com
password here
Is subscribed to a Newsletter (free) and has commented, etc.
Paid Subscriber
name@email.com
password here
Is subscribed to a Newsletter (paid) and has commented, etc.
This would be a great way to hop into testing states for the various users, like Factory testing. Of course we could make all of this state locally in our dev environment but it takes some effort and would seem to be useful for everyone running dev locally right out of the box. Some of the seeded users exist already so this is really about exposing their passwords and documenting the state so we can use it.
Well, a few weeks later and my motivation to continue the setup faltered on this step. I’m paying for Ghost Pro already so this was merely a curiosity to see if I could get Ghost running locally and play around with it - maybe contribute some code in my spare time. But I ran out of steam on the Mailgun step.
Having some example users seeded so we can kick the tires would really help the onboarding for people who may want to contribute. Just my 2 cents - maybe other people can push through this hurdle easier. I just felt like the documentation on getting up and running could have been better and affordances could be made to get it running without the Mailgun requirement, etc.