got a question regarding site

[Knipe]

Okay i am by no means a dev or know anything about it but i have a serious problem.

 

Lets say i buy a custom coded site from 0 with no templates used with a backend panel.

 

the site being launched and after a while i want to hire a dev to add new features to it.

 

The dev needs my admin panel access to add those features but theres nothing stopping him from yoinking my site or just deleting it completely for fun.

 

Is there a way around this? ( dont tell me to learn web dev myself)

[HarleyQuinn]

i don't understand what you mean but you should keep a backup of your site. i think you should considerably give him the main files and ask him to make changes there, then try implementing them yourself and seeing if its working or not

 

like i said i have no idea if this is what u meant

[dalton]

Okay i am by no means a dev or know anything about it but i have a serious problem.

 

Lets say i buy a custom coded site from 0 with no templates used with a backend panel.

 

the site being launched and after a while i want to hire a dev to add new features to it.

 

The dev needs my admin panel access to add those features but theres nothing stopping him from yoinking my site or just deleting it completely for fun.

 

Is there a way around this? ( dont tell me to learn web dev myself)

Backup. Then just give him FTP and DB access. 

[FaithHF]

What the above said.
If you're hiring a dev, you trust them. Take their ID or something for the sake of credibility. Make em sign an NDA or other contract prohibiting anything like that.

If you can't trust your dev, don't hire them.

As an alternative, set them up their own account on the server that only has access to whatever they're working on. Back up your copy. Take logs, do whatever.

Or just send them what you have, tell them to set up their own local environment and review changes yourself before pushing them live, like every other devops system in the world.

[Castiel]

Make a backup of your FTP + Database and create a dev environment with a copy of your FTP.

[tonu96]

I agree with everything said already, especially about not hiring someone you don't trust in the first place. This is probably your best option, though:

 

 

Or just send them what you have, tell them to set up their own local environment and review changes yourself before pushing them live, like every other devops system in the world.

 

Even if the dev is trustworthy, they could always make a mistake that messes up your site or database. Given them their own environment to work in will prevent just about any issue they might cause modifying your site. You'd also be able to protect your users' data by just populating a database with test values for the dev to work with rather than giving full access to potentially sensitive data.

[officialbabyk]

How do I work this?

[Traceback]

make a backup first 200IQ

[notARedTeamer]

You don't need to give an admin access to your developer. You can have a local copy of site from your production environment. Let the developer add those new features to that local copy. Test those features locally. Then when everything is OK and ready, you can upload the local copy to the production environment yourself. Be sure to have a backup of the production environment before uploading so that you can upload the previous version in case the new version didn't work.