How to handle template seeding
How do templates handle initial user creation when the user needs to go through a login flow to input their details? My application generates a link when creating a user that the user uses to login. I want to create that user when the template is created, but I'm not sure how to handle that - would it be ideal to create a service that's job is to create the user and output the login URL, that the template user deletes after they've registered?
12 Replies
Project ID:
N/Ais this your code or someone elses code?
someone else
then you would need to conform to however they have designed the user creation flow
it generates a URL to register the user - so i can either bundle it in with the main service or have a dedicated service to create the user, output the login, and ask the user to delete the service?
would be nice if we could label things in templates
You can name services though?
I'm missing a lot of context, but im sure you will end up choosing the best option!
is it possible to get the postgres data tab on a custom image?
that's detected if the image source contains the word postgres
👍 currently using a repo but ill move it to an image to get that
it may work with a repo too, not sure exactly
im guessing the repo has to include the text postgres, so i just ended up using github actions
i got it working successfully so ill go ahead with the template :)
awesome!