I know this topic will not be entirely Coda oriented, but I wanted to
have your opinion before starting really using Coda. I develop
WordPress websites and I would need to set up Coda to be able to
develop quickly and without wasting tweaking details instead of
actually being coding something!
So how shall I set up Coda, MAMP and WordPress to be able to develop
locally and update on my FTP in a few clicks.
I figure that I will have to have as many copies of WordPress as sites
in Coda, if I want to be able to upload all WordPress folder content
without problems.
I think I should be making good use of my hosts file to be able to
work locally and being able to simply comment my hosts file in order
to see how it looks online.
Any thoughts on that? Experiences? Ideas? I really don't know much
about Coda (yet!) so I am really waiting for your ideas and your own
expreience!
I am in the same situation with developing WordPress sites with MAMP and Coda and would also like to know the best (step-by-step) process in this kind of workflow.
Adam W. Warner
________________________________
________________________________
From: Jeremy <jehe...@gmail.com>
To: Coda Users <coda-users@googlegroups.com>
Sent: Wednesday, June 3, 2009 4:15:43 PM
Subject: [Coda-Users] Coda - WordPress - MAMP
Hi Everyone!
I know this topic will not be entirely Coda oriented, but I wanted to
have your opinion before starting really using Coda. I develop
WordPress websites and I would need to set up Coda to be able to
develop quickly and without wasting tweaking details instead of
actually being coding something!
So how shall I set up Coda, MAMP and WordPress to be able to develop
locally and update on my FTP in a few clicks.
I figure that I will have to have as many copies of WordPress as sites
in Coda, if I want to be able to upload all WordPress folder content
without problems.
I think I should be making good use of my hosts file to be able to
work locally and being able to simply comment my hosts file in order
to see how it looks online.
Any thoughts on that? Experiences? Ideas? I really don't know much
about Coda (yet!) so I am really waiting for your ideas and your own
expreience!
Do yourself a favor and splurge for MAMP Pro. Makes setting up and
maintaining multiple sites an absolute breeze. While you're at it, and
this really goes for anyone using MAMP/MAMP Pro/other server package,
grab a license for MailServe (http://cutedgesystems.com), which sets
up a Postfix mail server on your computer. If you do a lot of email
forms or notifications testing in your programming, actually receiving
the emails from your local dev server helps out more than you'd
believe!
Now, that doesn't specifically address your WP workflow, so let's look
at that.
Since you'll be working with fresh copies of WP (and whatever
additional WP plugins or themes that you find yourself adding in by
default), grab a copy of the CreateProject plugin for Coda, and set it
up with whatever your default install of WP is. Speeds up initial
setup like you wouldn't believe.
So far, here's your initial workflow:
1) Create a new Site within Coda
2) Run Coda's CreateProject plugin to generate a default site within
your MAMP Pro's httpdocs directory. I actually have MAMP Pro pointed
at the Sites directory in my user's home directory (i.e., /Users/bob/
Sites/ ), but to each his/her own...
3) Set up a new virtual site in MAMP Pro and point it at the new site.
You're done with initial setup!
Also, with MAMP Pro, you can set up actual domains for your sites. I
use ".dev" as my TLD, so I don't have to go to http://localhost:80/~sitename or whatever... I can type http://mydomain.dev and access the local
site.
Anyway.... that's a start. Hope this helps you and anyone else looking
for a Coda/MAMP (Pro) workflow.
-Bob
On Jun 3, 4:27 pm, Adam Warner <awarne...@yahoo.com> wrote:
> I am in the same situation with developing WordPress sites with MAMP and Coda and would also like to know the best (step-by-step) process in this kind of workflow.
> Adam W. Warner
> ________________________________
> ________________________________
> From: Jeremy <jehe...@gmail.com>
> To: Coda Users <coda-users@googlegroups.com>
> Sent: Wednesday, June 3, 2009 4:15:43 PM
> Subject: [Coda-Users] Coda - WordPress - MAMP
> Hi Everyone!
> I know this topic will not be entirely Coda oriented, but I wanted to
> have your opinion before starting really using Coda. I develop
> WordPress websites and I would need to set up Coda to be able to
> develop quickly and without wasting tweaking details instead of
> actually being coding something!
> So how shall I set up Coda, MAMP and WordPress to be able to develop
> locally and update on my FTP in a few clicks.
> I figure that I will have to have as many copies of WordPress as sites
> in Coda, if I want to be able to upload all WordPress folder content
> without problems.
> I think I should be making good use of my hosts file to be able to
> work locally and being able to simply comment my hosts file in order
> to see how it looks online.
> Any thoughts on that? Experiences? Ideas? I really don't know much
> about Coda (yet!) so I am really waiting for your ideas and your own
> expreience!
Excellent step by step, Bob. I pretty much use the same workflow,
right down to MAMP Pro (though I set up my domains as
local.domain.com) and couldn't be happier. It really works quite well.
> Do yourself a favor and splurge for MAMP Pro. Makes setting up and
> maintaining multiple sites an absolute breeze. While you're at it, and
> this really goes for anyone using MAMP/MAMP Pro/other server package,
> grab a license for MailServe (http://cutedgesystems.com), which sets
> up a Postfix mail server on your computer. If you do a lot of email
> forms or notifications testing in your programming, actually receiving
> the emails from your local dev server helps out more than you'd
> believe!
> Now, that doesn't specifically address your WP workflow, so let's look
> at that.
> Since you'll be working with fresh copies of WP (and whatever
> additional WP plugins or themes that you find yourself adding in by
> default), grab a copy of the CreateProject plugin for Coda, and set it
> up with whatever your default install of WP is. Speeds up initial
> setup like you wouldn't believe.
> So far, here's your initial workflow:
> 1) Create a new Site within Coda
> 2) Run Coda's CreateProject plugin to generate a default site within
> your MAMP Pro's httpdocs directory. I actually have MAMP Pro pointed
> at the Sites directory in my user's home directory (i.e., /Users/bob/
> Sites/ ), but to each his/her own...
> 3) Set up a new virtual site in MAMP Pro and point it at the new site.
> You're done with initial setup!
> Also, with MAMP Pro, you can set up actual domains for your sites. I
> use ".dev" as my TLD, so I don't have to go to http://localhost:80/~sitename > or whatever... I can type http://mydomain.dev and access the local
> site.
> Anyway.... that's a start. Hope this helps you and anyone else looking
> for a Coda/MAMP (Pro) workflow.
> -Bob
> On Jun 3, 4:27 pm, Adam Warner <awarne...@yahoo.com> wrote:
>> I am in the same situation with developing WordPress sites with
>> MAMP and Coda and would also like to know the best (step-by-step)
>> process in this kind of workflow.
>> Adam W. Warner
>> ________________________________
>> ________________________________
>> From: Jeremy <jehe...@gmail.com>
>> To: Coda Users <coda-users@googlegroups.com>
>> Sent: Wednesday, June 3, 2009 4:15:43 PM
>> Subject: [Coda-Users] Coda - WordPress - MAMP
>> Hi Everyone!
>> I know this topic will not be entirely Coda oriented, but I wanted to
>> have your opinion before starting really using Coda. I develop
>> WordPress websites and I would need to set up Coda to be able to
>> develop quickly and without wasting tweaking details instead of
>> actually being coding something!
>> So how shall I set up Coda, MAMP and WordPress to be able to develop
>> locally and update on my FTP in a few clicks.
>> I figure that I will have to have as many copies of WordPress as
>> sites
>> in Coda, if I want to be able to upload all WordPress folder content
>> without problems.
>> I think I should be making good use of my hosts file to be able to
>> work locally and being able to simply comment my hosts file in order
>> to see how it looks online.
>> Any thoughts on that? Experiences? Ideas? I really don't know much
>> about Coda (yet!) so I am really waiting for your ideas and your own
>> expreience!
I never liked the MAMP package supplied by the folks at Living-e AG -
I found free version to be useless and this completely put me off even
considering the pro version. It also irks me that the name MAMP (as in
LAMP or WAMP to identify the stack of open source apps running on a
partucular platform) is appropriated by MAMP the Living-e AG
distribution. But I'm a grumpy sort! Please forgive me!
If you don't mind rolling your sleeves up even the tiniest bit - (and
I guess not) - I'd highly recommend these steps to getting you own
development environment:
1. Swap the Apple package of PHP for Marc Liyanage's package (get it
here:http://www.entropy.ch/software/macosx/php/). RTFM - takes a
minute. His version has useful "extras" like the mcrypt extension that
Apple doesn't include: you'll want that for phpMyAdmin. (If you've
already started Apple's version - you'll know how to stop it.)
2. Get yourself virtualhost.sh from Patrick Gibson.
http://patrickgibson.com/utilities/virtualhost/ .
This little shell script will make the process of setting up proper
virtual domains a cinch. I also use ".dev" or ".live" as the TLD. (But
now I've started with GIT I may just drop the separation between live
and development branches. Git is GREAT! ). I still put all my sites in
my ~/Sites folder though.
4. Give your MySQL root user a password; type the following in
terminal:
/usr/local/mysql/bin/mysqladmin -u root password sniggle
...if you like sniggle as a passowrd that is.
5. Now you can administer your MySQL server with phpMyAdmin and the
root user you've defined in step 4. Download from here:
http://www.phpmyadmin.net/home_page/index.php. (There are other tools
too - eg MySQL Administrator - but I'm used to phpMyAdmin from the
hosting packeges I use). You may want to virtualhost phpMyAdmin to,
for example, "http://mysql/". Love virtualhost.sh.
6. Then for each [WP] site you'll want to add a user and then
associate a DB with that user. Do this in phpMyAdmin in one step using
the Privileges pane (you may know this already...): Fill in "Add a new
User"/then select "Create database with same name and grant all
privileges". Job done innit.
Done. Not long-winded at all!
{At last the readable and hopefully usable / accurate MAMP howto I've
been meaning to write up...}
It's taken me a while to get this right for myself - I hope it can
help you (or anybody!). And respect to the MAMP-Pro folks - just that
I can be a stubborn sort - and I wanted to get a proper .AMP stack
working on the Mac!
There's certaily nothing wrong with rolling your own 'MAMP'
installation. I just find that a single app with a unified GUI
interface for most of the services is far easier to manage and is more
Mac like.
Need a new site? Click add, type the address, select your folder and
you're done. MAMP pro isn't free and its by no means perfect but it
works for me.
On Jun 4, 2009, at 5:55 PM, lazydada <gdek...@gmail.com> wrote:
> I never liked the MAMP package supplied by the folks at Living-e AG -
> I found free version to be useless and this completely put me off even
> considering the pro version. It also irks me that the name MAMP (as in
> LAMP or WAMP to identify the stack of open source apps running on a
> partucular platform) is appropriated by MAMP the Living-e AG
> distribution. But I'm a grumpy sort! Please forgive me!
> If you don't mind rolling your sleeves up even the tiniest bit - (and
> I guess not) - I'd highly recommend these steps to getting you own
> development environment:
> 1. Swap the Apple package of PHP for Marc Liyanage's package (get it
> here:http://www.entropy.ch/software/macosx/php/). RTFM - takes a
> minute. His version has useful "extras" like the mcrypt extension that
> Apple doesn't include: you'll want that for phpMyAdmin. (If you've
> already started Apple's version - you'll know how to stop it.)
> 2. Get yourself virtualhost.sh from Patrick Gibson.
> http://patrickgibson.com/utilities/virtualhost/ .
> This little shell script will make the process of setting up proper
> virtual domains a cinch. I also use ".dev" or ".live" as the TLD. (But
> now I've started with GIT I may just drop the separation between live
> and development branches. Git is GREAT! ). I still put all my sites in
> my ~/Sites folder though.
> 4. Give your MySQL root user a password; type the following in
> terminal:
> /usr/local/mysql/bin/mysqladmin -u root password sniggle
> ...if you like sniggle as a passowrd that is.
> 5. Now you can administer your MySQL server with phpMyAdmin and the
> root user you've defined in step 4. Download from here:
> http://www.phpmyadmin.net/home_page/index.php. (There are other tools
> too - eg MySQL Administrator - but I'm used to phpMyAdmin from the
> hosting packeges I use). You may want to virtualhost phpMyAdmin to,
> for example, "http://mysql/". Love virtualhost.sh.
> 6. Then for each [WP] site you'll want to add a user and then
> associate a DB with that user. Do this in phpMyAdmin in one step using
> the Privileges pane (you may know this already...): Fill in "Add a new
> User"/then select "Create database with same name and grant all
> privileges". Job done innit.
> Done. Not long-winded at all!
> {At last the readable and hopefully usable / accurate MAMP howto I've
> been meaning to write up...}
> It's taken me a while to get this right for myself - I hope it can
> help you (or anybody!). And respect to the MAMP-Pro folks - just that
> I can be a stubborn sort - and I wanted to get a proper .AMP stack
> working on the Mac!
At the point where you're installing packages from all over the place
getting this to work, I recommend you instead start treading the
waters of Unix neckbeardism and look into MacPorts: http://www.macports.org/
Once you get the commands down, it's not that difficult to use, and
more importantly, it's very easy to upgrade and delete installed
software as well - definitely much easier than downloading a PHP
package from here and a MySQL package from there and an Apache package
from over there, in my opinion.
I've been happily using MacPorts for quite a while and can help answer
any questions others might have with using it.
On Wed, Jun 3, 2009 at 4:15 PM, Jeremy<jehe...@gmail.com> wrote: > I know this topic will not be entirely Coda oriented, but I wanted to > have your opinion before starting really using Coda. I develop > WordPress websites and I would need to set up Coda to be able to > develop quickly and without wasting tweaking details instead of > actually being coding something!
> So how shall I set up Coda, MAMP and WordPress to be able to develop > locally and update on my FTP in a few clicks.
> I figure that I will have to have as many copies of WordPress as sites > in Coda, if I want to be able to upload all WordPress folder content > without problems.
> I think I should be making good use of my hosts file to be able to > work locally and being able to simply comment my hosts file in order > to see how it looks online.
> Any thoughts on that? Experiences? Ideas? I really don't know much > about Coda (yet!) so I am really waiting for your ideas and your own > expreience!
> I found this question interesting enough to do a screencast on it. Let > me know here or in the comments on the post if it answers your > question. Enjoy!
Hi guys - the point about ease of use - is taken! ()
Garrett - I've stumbled across MacPorts before and heard only good
things about it. Perhaps now is the time to get beardy-wid-it. Its
like a linux package manager right? Just there to make life easier?
Mmm perhaps I shall reconsider my (not actually that)long-winded
ways... time to delve.
Bob - I missed your point about the CreateProject plug-in (although
Its now called Coda Project v1.2) - looks good - must give it a whirl.
David - good luck with the site - screencasts are a great resource.
On Jun 3, 10:15 pm, Jeremy <jehe...@gmail.com> wrote:
> I know this topic will not be entirely Coda oriented, but I wanted to
> have your opinion before starting really using Coda. I develop
> WordPress websites and I would need to set up Coda to be able to
> develop quickly and without wasting tweaking details instead of
> actually being coding something!
> So how shall I set up Coda, MAMP and WordPress to be able to develop
> locally and update on my FTP in a few clicks.
> I figure that I will have to have as many copies of WordPress as sites
> in Coda, if I want to be able to upload all WordPress folder content
> without problems.
> I think I should be making good use of my hosts file to be able to
> work locally and being able to simply comment my hosts file in order
> to see how it looks online.
> Any thoughts on that? Experiences? Ideas? I really don't know much
> about Coda (yet!) so I am really waiting for your ideas and your own
> expreience!
I use about the same workflow as Bob. Most times I do not use
the .dev. prefix for the domain.
I use the same as the domain that will be in production. I work all
locally and when done I upload
the files and import the db to the production server. By doing this I
do not need to change the
the domain settings in the database. Sometime I work semi locally. The
files are local but the
database is the production, when done with my files I just upload
them. Keep in mind that
I only work with personal stuff, no big corporate important things....
Cheers,
Jens
On Jun 4, 4:03 pm, Bob Sawyer <bobsaw...@gmail.com> wrote:
> Do yourself a favor and splurge for MAMP Pro. Makes setting up and
> maintaining multiple sites an absolute breeze. While you're at it, and
> this really goes for anyone using MAMP/MAMP Pro/other server package,
> grab a license for MailServe (http://cutedgesystems.com), which sets
> up a Postfix mail server on your computer. If you do a lot of email
> forms or notifications testing in your programming, actually receiving
> the emails from your local dev server helps out more than you'd
> believe!
> Now, that doesn't specifically address your WP workflow, so let's look
> at that.
> Since you'll be working with fresh copies of WP (and whatever
> additional WP plugins or themes that you find yourself adding in by
> default), grab a copy of the CreateProject plugin for Coda, and set it
> up with whatever your default install of WP is. Speeds up initial
> setup like you wouldn't believe.
> So far, here's your initial workflow:
> 1) Create a new Site within Coda
> 2) Run Coda's CreateProject plugin to generate a default site within
> your MAMP Pro's httpdocs directory. I actually have MAMP Pro pointed
> at the Sites directory in my user's home directory (i.e., /Users/bob/
> Sites/ ), but to each his/her own...
> 3) Set up a new virtual site in MAMP Pro and point it at the new site.
> You're done with initial setup!
> Also, with MAMP Pro, you can set up actual domains for your sites. I
> use ".dev" as my TLD, so I don't have to go tohttp://localhost:80/~sitename > or whatever... I can typehttp://mydomain.devand access the local
> site.
> Anyway.... that's a start. Hope this helps you and anyone else looking
> for a Coda/MAMP (Pro) workflow.
> -Bob
> On Jun 3, 4:27 pm, Adam Warner <awarne...@yahoo.com> wrote:
> > I am in the same situation with developing WordPress sites with MAMP and Coda and would also like to know the best (step-by-step) process in this kind of workflow.
> > I know this topic will not be entirely Coda oriented, but I wanted to
> > have your opinion before starting really using Coda. I develop
> > WordPress websites and I would need to set up Coda to be able to
> > develop quickly and without wasting tweaking details instead of
> > actually being coding something!
> > So how shall I set up Coda, MAMP and WordPress to be able to develop
> > locally and update on my FTP in a few clicks.
> > I figure that I will have to have as many copies of WordPress as sites
> > in Coda, if I want to be able to upload all WordPress folder content
> > without problems.
> > I think I should be making good use of my hosts file to be able to
> > work locally and being able to simply comment my hosts file in order
> > to see how it looks online.
> > Any thoughts on that? Experiences? Ideas? I really don't know much
> > about Coda (yet!) so I am really waiting for your ideas and your own
> > expreience!
On Jun 5, 2:09 am, lazydada <gdek...@gmail.com> wrote:
> Garrett - I've stumbled across MacPorts before and heard only good
> things about it. Perhaps now is the time to get beardy-wid-it. Its
> like a linux package manager right? Just there to make life easier?
Short answer: Yes.
Long answer: In the neckbeard realm, there's a crucial difference
between a "package" and a "port." When you install a package, the
package manager downloads and installs pre-compiled software. When you
install a port, the port system downloads the original source code for
that software, plus some patches to apply to the source code to make
it run properly/better on your system, and then compiles the software
for you and installs it when finished. Generally speaking, the former
is more popular in the Linux world and the latter is more popular in
the Unix/BSD world (of which OS X is a part).
The trade-off to using ports instead of packages is that it takes some
time for the software to compile on your system (and occasionally
compilation will out-and-out fail), but on modern computers it's not
so bad - just start the process in the Terminal, switch to your web
browser and totter around the web for a bit, and it will be done
before you know it. The benefit is that there's more flexibility in
how the software is built. In MacPorts, this is achieved through
"variant" options. For example, if you just install the PHP 5 port by
itself, it won't have support for any DBMSes; you have to add the
MySQL/SQLite/etc variants when you build it. It might be a pain if you
go through the process of building the whole thing just to realize
it's missing functionality that you need, but it's good in that you
end up with a slimmer system because you're not installing
functionality you don't need.
On my computer back home, I've installed the PHP 5 port with support
for both MySQL and SQLite (Drupal 7 will support SQLite out-of-the-
box, after which I will use MySQL only when necessary!), and it
interacts with Lighttpd via FastCGI, so to install it, I ran a command
something like:
Thank you all guys! I honestly did not expect such great level of
answer. I will have a look at all your propositions, because they all
seem to be pretty good and I believe any of them would fit my needs
(apart maybe from lazydada's alternative maybe: sorry but that sounds
a bit too complicated for me! :) ). I will just try to find out what's
best for me.
I will consider buying MAMP Pro as well. I did not even look at this
opportunity until now, having a Free version available kind of dragged
me away from the paid alternative at first I guess.
So thank you again! Dicovering the Coda community seems as great as
discovering Coda software itself! :)
Great intro into the world of Mac Ports. Thanks for outlining the
packages/ports thing too.
Thanks but I'll never change anything ever again. Guess who updated
MySQL for the first time to find his databases gone. Luckily nothing
important there - only dupes for development purposes. Easily
reinstated. Even so, who'd of thunk.
I think I'll go and blow the 40 bucks on a night of sherry fuelled
debauchery in the campo with the goats under a star filled sky.
I'm growing a neckbeardo estilo rustico now.
See you on the other side.
; )
On Jun 5, 6:16 pm, Garrett Albright <spearbr...@gmail.com> wrote:
> On Jun 5, 2:09 am, lazydada <gdek...@gmail.com> wrote:
> > Garrett - I've stumbled across MacPorts before and heard only good
> > things about it. Perhaps now is the time to get beardy-wid-it. Its
> > like a linux package manager right? Just there to make life easier?
> Short answer: Yes.
> Long answer: In the neckbeard realm, there's a crucial difference
> between a "package" and a "port." When you install a package, the
> package manager downloads and installs pre-compiled software. When you
> install a port, the port system downloads the original source code for
> that software, plus some patches to apply to the source code to make
> it run properly/better on your system, and then compiles the software
> for you and installs it when finished. Generally speaking, the former
> is more popular in the Linux world and the latter is more popular in
> the Unix/BSD world (of which OS X is a part).
> The trade-off to using ports instead of packages is that it takes some
> time for the software to compile on your system (and occasionally
> compilation will out-and-out fail), but on modern computers it's not
> so bad - just start the process in the Terminal, switch to your web
> browser and totter around the web for a bit, and it will be done
> before you know it. The benefit is that there's more flexibility in
> how the software is built. In MacPorts, this is achieved through
> "variant" options. For example, if you just install the PHP 5 port by
> itself, it won't have support for any DBMSes; you have to add the
> MySQL/SQLite/etc variants when you build it. It might be a pain if you
> go through the process of building the whole thing just to realize
> it's missing functionality that you need, but it's good in that you
> end up with a slimmer system because you're not installing
> functionality you don't need.
> On my computer back home, I've installed the PHP 5 port with support
> for both MySQL and SQLite (Drupal 7 will support SQLite out-of-the-
> box, after which I will use MySQL only when necessary!), and it
> interacts with Lighttpd via FastCGI, so to install it, I ran a command
> something like:
|
