nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Poll: Should Developers Have Root Access?

System

I am trying to find out 2 things:
1) Does your company allow TeamSite Developers to have root access (or at least sudo access to TeamSite functions)?

2) Should TeamSite Developers have root access and why?

- Jason

Find more posts tagged with

Comments

gzevin

IMO, some do need have such an access.. just to be able to set the directories properly, run the scripts as root, etc, etc,

however this needs to be done in the way that the system policy and security is not comromised. ideally, this should be allowed on the dev boxes only.

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Adam Stoller

In my case - yes [sudo] and yes [developers - me - and our TS Admin]

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Lozza

Not on my site, and it's very problematic. Any changes to a configuration file on the production box has to be done by an already overworked UNIX sysadmin team, which not only slows down development to a crawl but also the resolution of problems.

A solution I've implemented is a workflow that deploys key configuration files (e.g. templating.cfg, odnodes.xml etc) from a config branch in TeamSite itself. This works well, and carries the added bonus of a full version history of config changes.

However even with something like this in place, I think at least one member of a content management team (and one for backup) should have root or pseudo-root access for speedy resolution of issues. I don't expect a sysadmin to know how to interpret TeamSite's often bizarre inner workings as much as he wouldn't expect me to put the box together.

Adam Stoller

We've managed to get all (I hope) of our configuration and customization files in a TS branch (for versioning) and use OD to deploy those files to the local disk - we use a DNR script from the deployment to restart services, run make_toolkit, etc. - as long as you have OD running as 'root' - it facilitates *not* being 'root' (or having sudo) for such tasks -- however, I still think it hampers productivity if the developers and TS Admin do not have root or sudo priveleges - especially in the DEV environment (ideally developers should *only* be working in DEV - so that's the only place they *should* need it - however, for debugging problems that come up once the code has been released to TEST and/or PROD environments, it still *helps* for them to have sudo priveleges there)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

jbonifaci

Where I am at:

1) No.

2) Not as long as there is an administrator or team of administrators for the environment(s) that have a decent turn around time.

Migrateduser

A common arrangement I've seen is for developers to have root on the development server but not on the production server. This can be a pain when it comes to resolving mystery problems that pop up in prod but not in the dev environment, but it keeps those problems from popping up as frequently.

nipper

tsadmin has sudo access (me)

no one else can touch my servers under penalty of ticking me off.

Balu110

In our case NO. We need to work with different teams to implement a config change and some cases it is taking longer to time to resolve issues, especially in production environment.

After a long battle we are able to sudo access only to development box.