dw_dev_training | Fetching updates on Dreamhack?

Entry tags:

Fetching updates on Dreamhack?

How does one update their repos on their hack now? The 'old' script no longer pulls anything for me (what used to be on http://wiki.dwscoalition.org/wiki/index.php/Dev_Maintenance) and I don't understand how I can keep up with changes. :/

(Context: I'm on Windows; I use PuTTY and WinSCP).

Edit: ok, if anybody else wonders, short answer is you can no longer update your hack using old methods. :/

Edit 2: long answer is you can switch to the new system. See comments for detailed instructions. :)

Flat | Top-Level Comments Only | Expand All

I think if you can use Github's instructions for creating a new development environment on your local machine

This is the easy part.

and use our wiki instructions for updating your Dreamhack, you should be able to get up and running

This is the part that makes no sense to me because 1) instructions are all over the place 2) it's not 100% clear to me what are the parts for hacks and what aren't 3) don't tell me where or how to do this. I feel like I'm back when I got into dev work since there were zero instructions for newbies on windows.

Edited 2012-08-23 16:37 (UTC)

The most recent post in

dw_wiki is where Fey and Fu have been coordinating efforts to update the documentation - maybe that would be a good place to brainstorm how best to address your concerns.

(I hope that doesn't come across as dismissive! I am just crap at documentation and I am happy other people are working on it who are not me.)

I saw that earlier today and I know they plan to update my newbie guide but, well, this doesn't really help. I just wish we had been told some stuff like what you said above instead of leaving us in the dark about them. Not you fault so it's unfair to unload this on you (and you don't come across as dismissive at all). Also I'm very cranky today for other reasons and would have liked to cheer me up with some DW so not being able to makes me extra cranky. My apologies.

Hey 90d--you're totally right about this and I'm sorry. I'm going to make a post to

dw_dev about this so nobody else ends up in the dark. If you want somebody to help walk you through anything in real time, I am happy to do so--I'm working on getting myself up to the level I need to be to write good documentation on this.

Pretty much all of the directions here are for Dreamhack moving over while logged in through PuTTy, but I think what is lacking is what happens AFTER that for trying to develop anything. I will make that my top documentation priority now.

I can't do real time because I'm a bad typist in these circumstances and IM is extremely stressful for me (and believe me I know how stupid that sounds) but if email's or commenting's ok for you I would like that, please. I know this isn't ideal for you guys so I would understand if you said no.

Also thank you very much. I'm sorry I commented on the dw_wiki entry before I saw your comment.

No, no, that is fine! Commenting is fine! We don't want to stress you out. And I think we commented around the same time in our respective places. We love you, we love the work that you do, we've fallen down on how to best manage this transition, and we want to make it right in however you think is best!

Probably the first thing is to transfer over your development environment to Git. Fortunately, it is very forgiving--since you just move the old one out of the way, if it ends up messed up, or you want to go back to the old one for whatever reason, you could just move it back and everything would be okay.

We can work on improving this document as we go along:

http://wiki.dwscoalition.org/wiki/index.php/Moving_your_Dreamwidth_installation_to_use_Github

The first time you run into a question, just comment, and I or

afuna will answer. I'll be tracking all comments to this entry, so you don't even have to make them all into a big thread, just any comment here, I will see it.

Thank you.

So the the first git clone command gives me an error:

fatal: https://github.com/ninetyd/dw-free.git/info/refs not found: did you run git update-server-info on the server?

Also I used my username on github (ninetyd) as my username. Should I have used something else?

ninetyd is a great github username.

Okay, when I go to your page here:

https://github.com/ninetyd

I see that you forked dw-free and dw-nonfree a while ago, but when I try to go to the repository they link to, I get a 404:

https://github.com/ninetyd/dw-free

Is this the case for you while you are logged in? It also says that "ninetyd doesn’t have any public repositories yet".

Oh no I did fork then but then I deleted them because I thought I wasn't supposed to do that since newer instructions didn't seem to mention it. I'll fork them again.

Edit: forgot to say: I'm going to take notes to make sure I remember every step so my apologies if I'm slow to answer.

Edited 2012-08-23 17:33 (UTC)

Sweet, back on the tracks--and don't worry about being slow. I'm sure you'll understand if I get pulled away and have delayed responses from work, too!

Hmm, just realized that the instructions weren't explicit wrt forking, so I've added a sentence

I actually totally missed that sentence. If I may I think it would be better to tell people to do that first then do all the steps on the server. I didn't expect the back and forth thing. See what I mean?

Good point. How do the transition instructions look now?

Much better imo because you know in advance what you're going to do and why. Can I ask what this means?

Contents of $LJHOME will be live when you start the server
Contents of $LJHOME/ext will be used automatically (no syncing)

It looks like it speaks of the same thing but I don't understand what the difference is, if there is one.

Ahhh yes, both $LJHOME and $LJHOME/ext are used as-is, as compared to before when the contens of $LJHOME/cvs/* had to be synced over to $LJHOME first.

So the two are the same thing; the differences only relevant if you're comparing against the old way of doing things. Hmm, I'm not quite sure how to explain.

Maybe take out those two points and instead say:

* all code from dw-free ($LJHOME) and the additional repos under $LJHOME/ext are live. There's no need to run any additional syncing steps

(no subject)

ninetydegrees - 2012-08-23 18:27 (UTC) - Expand

(no subject)

foxfirefey - 2012-08-23 18:32 (UTC) - Expand

I think you are right in that they are both the same thing. They are both talking about how you don't have to run bin/cvsreport.pl. I think they end up as two separate things because before, dw-nonfree and dw-free both had to be synced; now dw-free is the base directory and dw-nonfree is in the ext directory, automatically overrides things in dw-free, and neither need syncing.

I'll try to figure out some alternative wording.

Hey--

I was reading over the instructions and realized that they don't have the authenticated versions of the Github URLs, so I have edited them to be like:

git clone https://USERNAME@github.com/USERNAME/dw-free.git $LJHOME

Same with nonfree.

I remember having troubles when it came to actually trying to push anything to my repository without this. I have changed the documentation to reflect the correct things. I'm pretty sure you have already cloned and everything though, but you can change it by being in $LJHOME or $LJHOME/ext/dw-nonfree and going:

git remote set-url origin NEWURL

(you are free to make me explain that some more)

I went through all the steps and everything worked fine except I didn't need to create /ext because it already existed and running checkconfig gave me an odd message although it looks like this is normal:

Missing optional secret 'invite_img_auth': Auth code for invite code status images

Re: the URLs thing. I don't understand if I'm supposed to do something or not.

Yeah, I'm not really sure that is an important error from checkconfig.

So, if you end up trying to push from your Dreamhack, and you used this URL to clone:

git clone https://github.com/USERNAME/dw-free.git $LJHOME

Instead of one that has an authentication added to it:

git clone https://USERNAME@github.com/USERNAME/dw-free.git $LJHOME

It won't know what to do to authenticate when you try and push changes back--although cloning will have worked just fine! But, you can change the URLs in dw-free and dw-nonfree without having to reclone things by using the remote set-url command:

cd $LJHOME
git remote set-url origin https://ninetyd@github.com/ninetyd/dw-free.git $LJHOME
cd $LJHOME/ext/dw-nonfree
git remote set-url origin https://ninetyd@github.com/ninetyd/dw-nonfree.git $LJHOME

That way, when you go to push something, it will ask you for a password and you can provide it.

Thanks for the clear explanation. However, the git remote command gave me an error:

fatal: No such URL found: /dreamhack/home/8174-ninetydegrees/dw

My fault, $LJHOME should not be on the end of those, it is confusing it to bits, these are better:

cd $LJHOME
git remote set-url origin https://ninetyd@github.com/ninetyd/dw-free.git
cd $LJHOME/ext/dw-nonfree
git remote set-url origin https://ninetyd@github.com/ninetyd/dw-nonfree.git

(no subject)

ninetydegrees - 2012-08-23 18:38 (UTC) - Expand

Fey has already said everything that I want to say -- just seconding that comments are excellent (both for you, and for making it easy for others to see what's going on).

I'll be lurking around in case you run into any issues; I may have to head to bed soon, but fey is around, and I will be checking in first thing in my morning!

Thank you. I don't know if I should say this but... I've always felt it wasn't really ok actually. Not from you, just in general. It's obvious it's not a favoured way of communication in lots of areas so, er, well.

I'm sorry you've gotten that impression. Thinking back on it, I don't think we've made it obvious that discussion in comments is something we encourage, so we'll have to figure out how to push for it more.

It's not your fault. I think it also comes from the fact that some (many?) of you guys knew each other before either via LJ or pre-beta days and there are... traditions I guess. And personal preferences too, of course. So it's like an automatism if that makes sense.

Edit: reread your comment as the page reloaded it and I wanted to clarify something. It's no so much 'encourage' as 'welcome': discussion wherever it takes place is welcome and will get a response, even if it can take some time depending on the mode of communication. Also related, it feels like some info bypasses (edit: not the right word but at least correct grammar) official DW comms entirely, which I've always found odd, and thus preventing comments from happening there because there isn't simply anything to comment on.

Edited 2012-08-23 18:23 (UTC)

Flat | Top-Level Comments Only | Expand All