Jón Borgþórsson wrote:
Wy not the just put /etc under subversion control?
People do… (not me)
Yeah I get that FTP access can be useful in some cases. But I honestly
think that it is a minor issue for minoroty of people. I think I have
seen 3 people complaining about the lack of FTP.
I’m truly curious how people work - install
ruby/rails/mysql/postgresql/lighty/etc. locally, dev and edit locally,
then svn ci, svn update on server with identical setup. I’m definitely
not interested in replicating my server setup on my notebook - I’ll just
create a separate dev rails dir on my server, if really necessary.
Otherwise I’d like to work on remote files as if they’re local, which
should be a piece of cake, except TextMate has some stupid polling
feature which causes it to freeze for tens of seconds when using NFS and
you switch from TM to another app and back again.
Joe
Note to the “just use Cyberduck” crowd - it doesn’t work with projects.
Only single files. Yuck.
Joe
Yeah I get that FTP access can be useful in some cases. But I honestly
think that it is a minor issue for minoroty of people. I think I have
seen 3 people complaining about the lack of FTP.
Pshaw! Put / under version control! 
I agree that it’s a minor issue. I use it infrequently enough that
Cyberduck + Textmate does the job for me. Then, there’s always ssh +
vi, too.
-TJ
I’ve just sent back my second MacBook and don’t know at this stage
whether I
will get another.
The first had a video defect which was causing a block of pixels to
display
incorrect colours. Sent this back and they sent out a replacement
which
had a defective trackpad button (also had a dead pixel but I could have
lived with that).
I didn’t have overheating or other issues and the machines sure were
fast. I think the factory QC is appalling for a machine to leave with
something as obvious as a defective trackpad button. After two faulty
machines, I’ve opted to receive a refund. Might buy one from a
reseller
next time - at least then I won’t have to go without a machine for 10
days
every time I get a faulty one!
Joe
Joe R. (if that is your real name),
I use Locomotive + MAMP under OS X, which means I have rails/lighty(I
think)/mysql/phpmyadmin. I think this is a great alternative to
spending a good chunk of time building and configuring server software
on your laptop. I’d rather have someone else tinker with the
configuration. Besides, if some server software configuration gets
hosed somehow, then it’s really easy to wipe out and reinstall.
I don’t see the motivation for editing files on the server during the
development process. I’d much rather keep as much stuff local as
possible to keep development cycles short. And besides, that way my
development environment is totally portable (as in I can work on the
train). I use TextMate for editing locally, and commit to svn directly
through TextMate, then use capistrano to deploy into a test environment
when I reach a small development milestone (at least several times a
week). From a configuration management standpoint, editing files on a
server is a Bad Idea, but I won’t get into that now.
I would strongly recommend you take a serious look at using svn and
capistrano for deployment. The svn ci method is ok, but it makes me
uneasy to have version control-related files in my production
environment. Capistrano gives you a lot more control over deployment of
your app onto your server. It is super easy to roll back to a previous
deployed version, and it has hooks for running migrations and executing
commands on the server, and you can deploy without even logging into
your server. It’s as simple as “rake deploy” to deploy and “rake
rollback” to go back to the previously deployed version, including
running migrations.
It really only took me about an hour to read the documentation and set
it up.
Ken
On 6/15/06, Joe R. [email protected] wrote:
I’m truly curious how people work - install
ruby/rails/mysql/postgresql/lighty/etc. locally, dev and edit locally,
then svn ci, svn update on server with identical setup. I’m definitely
not interested in replicating my server setup on my notebook - I’ll just
create a separate dev rails dir on my server, if really necessary.
Otherwise I’d like to work on remote files as if they’re local, which
should be a piece of cake, except TextMate has some stupid polling
feature which causes it to freeze for tens of seconds when using NFS and
you switch from TM to another app and back again.
Only ruby/rails at my notebook. Use the servers MySQL.
Then I just use script/server at my notebook to start a local server.
No need for apache/lighty etc.
Then I create a SVN server. work on my application locally and when
I’m happy with the changes I do the command “svn update” on my server
and thats all.
I think it’s the most common setup. And the only way to work if you
have more than one developer.
–