Hello David, This cookbook has worked for me for the last five years on Mac OS X, always and totally reliable up to incl. El Capitan and every intermittent release before. And most of all, it worked even as a repair measure. So if my server would stop working after a small Mac Os X update, I took these steps, and without migrations it just worked again then: 1. google enterprise Postgres installer 2. hit the first link, follow your intuition on where you get until you download the binary for the platform you want 3. install postgres and then launch package maker 4. in package maker, you can scroll down and navigate to the category web development, and there select phpPgAdmin with apache 5. run the installation, it is going to install a special instance of apache only for phpPgAdmin 6. it will guide you through to the end including to select a port and website to connect to, just hit return 'til the whole things shuts up and gives you the summary page 7. make a screenshot for your files, log on trough a web browser, you will see, it explains itself Note 1: depending on where you want to allow logons from to your page, this is another chapter, but actually quite straight forward. Note 2: Given you are in the middle of another approach, this might fail now. Regardless of any prior data you have, disregard it until here. Once the server is running, you have the next piece to cover and it is normally quite easy to do then. I did also both, Mysql and Postgres, and even though it seemed a little less intuitive at first, and even though I find a waste of time in any matter aggravating, there is a host of reasons it was a very good and time saving decision in the long run to have switched and thus gained access to tons of features mysql does not offer, not to mention the license giving you freedom mysql is never going to be able to offer. Finally of that, I have rarely found an open source community as supportive and responsive as the postgres community, you can measure that against premium service of some providers who charge you money for it. Hang in there for the start, it is going to be rewarding. Hope this helps your decision process Alex > On 25 Oct 2015, at 1:28 p.m., Adrian Klaver <adrian.klaver@xxxxxxxxxxx> wrote: > > On 10/24/2015 09:19 PM, David Blomstrom wrote: >> I'm a writer. I studied programing and MySQL so I could create websites >> that I can publish my articles to. I don't have time to keep up with the >> endless technology - MySQL, PDO, stored procedures, PHP, JavaScript, >> JQuery, and on and on - especially when I have to work for a living. >> I've been using MySQL for years, so I'm familiar with it. It therefore >> makes sense for me to find a GUI as similar to MySQL as possible. >> >> With phpMyAdmin, I can easily create, modify, copy and migrate tables >> between databases. If that can be done as easily with a >> command-line-tool, even after surviving the learning curve, then I'm >> interested. But it's really hard to imagine how that could be. > > pgAdmin will allow you to do those things. phpPgAdmin also, though I have never used it, so I can not be of much help there. The predominate command line tool folks are referring to is psql: > > http://www.postgresql.org/docs/9.4/interactive/app-psql.html > > For dumping databases or their contained objects there is pg_dump: > > http://www.postgresql.org/docs/9.4/interactive/app-pgdump.html > > for restoring non-plain text dumps there is pg_restore > > http://www.postgresql.org/docs/9.4/interactive/app-pgdump.html > > for plain text dumps just use psql. > > These three programs will cover most of your use cases. The benefit to using these tools is that you end of working with scripts that then can be put under version control. Takes a little bit of time to set up but the payoff is worth it for anything above the really simple level. > >> >> Thanks for the tips. >> >> On Sat, Oct 24, 2015 at 9:07 PM, Adrian Klaver >> <adrian.klaver@xxxxxxxxxxx <mailto:adrian.klaver@xxxxxxxxxxx>> wrote: >> >> On 10/24/2015 08:52 PM, Rob Sargent wrote: >> >> ok. now who has the url to the pithy >> heres-why-you-/really/-want-the-command-line. >> >> It distills to something about actually knowing what you’re doing. >> >> >> Everyone has to start somewhere. The point is get someone using >> Postgres in manner they are comfortable with, then they can start >> exploring the possibilities. I personally find the command line more >> productive, but there is a learning curve. >> >> >> >> >> >> -- >> Adrian Klaver >> adrian.klaver@xxxxxxxxxxx <mailto:adrian.klaver@xxxxxxxxxxx> >> >> >> >> >> -- >> David Blomstrom >> Writer & Web Designer (Mac, M$ & Linux) >> www.geobop.org <http://www.geobop.org> > > > -- > Adrian Klaver > adrian.klaver@xxxxxxxxxxx > > > -- > Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
