Transferring the site for revision to the wrong hands

A

And2015-09-30 08:45:21

CMS

And, 2015-09-30 08:45:21

Transferring the site for revision to the wrong hands - how not to "get"?

After certain thoughts about the design, we decided to refine it a bit. The work is quite small - copy the CSS design from one site to our site. But since no one has done this with us and will not do it, we need to give this work to freelancers, the previous site developer is no longer involved in support - he went offline business. So - how can you protect the site from various "bookmarks" or viruses or referrals to other sites that can be thrown into the source code by an unscrupulous freelancer?
I thought that it is possible to give him the page addresses without the admin panel and then just put the finished css in the right place. But over time, you need to finish the site engine a little, so you won’t be able to do without issuing an admin panel. How to be in that case?

Reply

Answer the question

In order to leave comments, you need to log in

7 answer(s)

S

Stalker_darkway, 2015-09-30
@wiggy

See reviews. More reviews - less risk. Well, by and large, the risk is always present. You can find a freelancer from your city and transfer the data to him in person, you can even conclude an agreement.

P

Pavel Chesnokov, 2015-09-30
@cesnokov

Some of my clients prefer to work with GIT repositories/version control (eg Bitbucket ). For small projects, it's free and safe. I make corrections, and the customer sees what exactly I changed and in which files. In your case, a third-party developer will pick only CSS, and will not make edits in other files - because he knows that you see every change. And you yourself place the already debugged code on the main site. Yes, and many questions disappear, did it work, did it, who exactly did it, and of course "who is to blame" :)

V

Vladimir Io, 2015-09-30
@vawsan

See reputation. A dude making 250k a month won't paste a link that pays 2 cents per click.

K

kstyle, 2015-09-30
@kstyle

You can also compare files before and after. And see the differences - what kind of code is there.

P

Puma Thailand, 2015-09-30
@opium

studio agreement.

C

CrewCut, 2015-09-30
@CrewCut

They say right - look at the reviews and trust. Otherwise, it doesn't matter.
There is a paranoid option - to make a complete copy of the site, give access to it - let him do everything there. Then find a security specialist and ask him to test the site for changes.

I

Igor Vorotnev, 2015-10-01
@HeadOnFire

Yolki are sticks. No one in their right mind gives access to production to just anyone. For such tasks, there are version control systems and staging. If it's super complicated - you give the freelancer a database dump and a copy of the site (or a link and rights to a Git turnip), he deploys a development copy, makes edits, commits to Git / sends you an archive / shows it on his server. After the work is approved, transfer the edits to yourself.