Pål Bergström wrote:
What I like about git is
branching.
Likewise.
But for actual version control I can manage without it. I’ve
used git for a while now and I’ve never needed to use it for going back
in code. Trust me. 
You’ve never had a branch that you wanted to back out of? You’ve never
wanted to not deploy the bleeding-edge version of your codebase until it
stabilizes?
Getting back to the topic, do you understand now how to get Cap
deployment working? It’s really not terribly difficult if you trust
Capistrano to do the right thing in most cases.
Not quite. I don’t think is that clear.
What don’t you understand?
[…]
And sometimes we users are just thick headed.
Sure sounds like it. Give it a try and let me know if you have any
actual problems.
So back to my question, what if I, as I would like that way, have zero
and nada interest of having version control on the server side?
Then you will not get much sympathy from me, nor from many others on
this list, as you are asking for help in implementing a Certified Bad
Idea [TM]. It can be done, but I do not recommend it.
Best,
Marnen Laibow-Koser
http://www.marnen.org
[email protected]
I would say that your life with Capistrano would just be SOO much
easier if you use something like git/svn…
But I don’t understand how. Arrgh. Should I setup a repository on the
server myself? What about my apps, what would be the path for pointers?
Sorry, but I don’t think you see the issue here. How does it work on the
server side? I can’t find any tutorials that talks about that. Like the
otherwise very good “The Absolute Moron’s Guide to Capistrano” (that’s
me). It kind of leaves out big chunk. It states “set :repository,
“http://somesvnrepository/trunk”” What about that somesvnrepository (git
in my case)?
Pål Bergström wrote:
I would say that your life with Capistrano would just be SOO much
easier if you use something like git/svn…
But I don’t understand how. Arrgh. Should I setup a repository on the
server myself?
Yes. Gitosis is a nice way to set up a Git server, or you can use a
hosted service such as Github, Unfuddle, or Gitorious.
What about my apps, what would be the path for pointers?
Whatever you like.
Sorry, but I don’t think you see the issue here. How does it work on the
server side? I can’t find any tutorials that talks about that.
I think it’s assumed in Cap tutorials that you already know how your
version control server works.
Like the
otherwise very good “The Absolute Moron’s Guide to Capistrano” (that’s
me). It kind of leaves out big chunk. It states “set :repository,
“http://somesvnrepository/trunk”” What about that somesvnrepository (git
in my case)?
What about it? The tutorial assumes you already have your source code
repository set up. (I think most developers these days do that as one
of the very first steps in starting a new project – I know I do.) In
any case, Cap is usually set up to communicate with an already
established repository, not to set one up itself.
Best,
Marnen Laibow-Koser
http://www.marnen.org
[email protected]
Marnen Laibow-Koser wrote:
Pål Bergström wrote:
What about my apps, what would be the path for pointers?
Whatever you like.
That will not work. What are you talking about?
I think most developers these days do that as one of the very first steps in starting a new project
Far from it. Are you a web developer?
Marnen Laibow-Koser wrote:
You’ve never had a branch that you wanted to back out of? You’ve never
wanted to not deploy the bleeding-edge version of your codebase until it
stabilizes?
No. But I might if I get into git more. But with my way of working I
know I can manage without it.
What don’t you understand?
The server side.
Then you will not get much sympathy from me, nor from many others on
this list, as you are asking for help in implementing a Certified Bad
Idea [TM]. It can be done, but I do not recommend it.
I doubt that I’m alone on this. What really matters is getting a good
well designed and design oriented site up using solid web standards.
That comes first.
Yes – 10 years’ worth of one. Are you?
Yes. Longer than that. But coming from a design perspective, which
should be the focus in any serious web project.
Pål Bergström wrote:
Yes – 10 years’ worth of one. Are you?
Yes. Longer than that. But coming from a design perspective, which
should be the focus in any serious web project.
I agree with you (I sort of started there too), but one can’t neglect
good coding practice either. Making the two work together harmoniously
is what makes good Web development so challenging.
But we’re losing the topic here…
Best,
Marnen Laibow-Koser
http://www.marnen.org
[email protected]
Pål Bergström wrote:
Marnen Laibow-Koser wrote:
Pål Bergström wrote:
What about my apps, what would be the path for pointers?
Whatever you like.
That will not work. What are you talking about?
Well, you can set your app’s directory to anything you want. What about
that won’t work?
I think most developers these days do that as one of the very first steps in starting a new project
Far from it. Are you a web developer?
Yes – 10 years’ worth of one. Are you?
Best,
Marnen Laibow-Koser
http://www.marnen.org
[email protected]