4 ms·
I'd tend to think most pg'ers would want to use their everyday pg tools to setup their db's. For most, that's going to be command line tools, which sounds like
by rektide 11y ago
I'd tend to think most pg'ers would want to use their everyday pg tools to setup their db's. For most, that's going to be command line tools, which sounds like what you are not having fantastic success using.
If embedding here-documents inside scripts isn't to your liking, perhaps you should either separate out the seed scripts and cat them in, or have your app-server take on more responsibility for seeding. Systems like Liquibase used by Dropwizard are an example of a more formalized way of performing initial seed, an example of something that might be more what you are looking for if shell scripts are proving difficult to operate.
- mixmastamyk 11y agoIt works, it's just clumsy.
- Roboprog 11y agoScripting is clumsy compared to what? Clicking radio buttons and "next" for 5 minutes??? Another alternative is to make an empty (or test setup) database instance in the "PGDATA" directory, and archive that (while the DB is shut down) for redeployment on another server instance. Unlike Oracle, everything is in one place, as ordinary files and subdirectories.
- mixmastamyk 11y agoNo, here-documents should not be required. The security settings should be a lot more intuitive, etc.
- Roboprog 11y agoFair enough on the security settings. That's something I have to squint at in many system, as I don't deal with it much, other than to grant full access to an app level account. A cheat sheet on common use cases would help.