What info do i need to provide a freelancer?

[redlizard]

Hello Everyone,

I have hired a freelancer to implement some changes in my OSC shop. Since I have been doing everything myself thus far (going at a snailspace) I've never had to give out any passwords before.

 

Now I need to give my FTP and Shop password. Naturally I can reset these after the work is done, but is there anything else I should watch out for?

Also, am i going about this naively, or is this standard procedure?

 

Thanks in advance for your advice!

Lukas

[web-project]

all passwords you can reset later on.

[Jack_mcs]

If you are going to have someone work on your shop, depending upon the changes, you pretty much have to allow him full access. If no database changes will be needed, then you can limit his access but someone that knows what he is doing can get around that, if that was his intention.

 

Jack

[redlizard]

Jack, Alex,

Thanks for the quick feedback. Ok. I just wanted to know if there was a way around that.

I hired the person through elance and he has a good reputation, but at the end of the day it's still all just trust.

 

Cheers, Lukas

[redlizard]

Sorry, one more question:

 

How do I change the password for the Store Administration?

 

I am searching the forum but can not find an answer to this.

 

Thanks,

Lukas

[Guest]

Depending on how much you are going to have this freelancer work on your site, you may want to have him set up a staging site on his own server. If you are only having him change a few things, this is more work than he will probably want to do (or he will charge you for it). It frustrates me to have to create a test site on my server for implementing a couple of reports but for big projects, it is what I prefer, especially if it is a live site.

[♥geoffreywalton]

You either have to provide a copy of your site and the db for the developer to create a working copy locally that they can work on or give them access to your site.

 

Even when given access to their site I personally take a copy of both. Then create a repository of the code and a new database. Then as I work on the site I can take snapshots after every contribution/feature is completed. Thus am able to go back to any checkpoint. (lindsayanng eat your heart out)

 

Then when I have tested it on my copy, I can upload any changed files to the client's and run any sql required.

 

That way the "working" site is secure during the development phase.

 

But really it is a trust thing. Even if you do trust them take your own copy of your site and data and store it locally. Then you can always recover to that position even if they mess up.

 

Enjoy