lamp-install-script icon indicating copy to clipboard operation
lamp-install-script copied to clipboard

Update for ubuntu 13.10

Open mhlavac opened this issue 11 years ago • 6 comments

mhlavac avatar Dec 17 '13 18:12 mhlavac

In Ubuntu 13.10 Apache is upgraded to 2.4. The configuration is not compatible. Have a look at Upgrading Apache to 2.4 from 2.2.

tomas-pecserke avatar Dec 17 '13 19:12 tomas-pecserke

Good point, I've already had to change few things because of new Apache 2.4, this is going to be another one.

I should also check this http://httpd.apache.org/docs/current/mod/mod_unixd.html as we are currently using mpm_itk to use AssignUserId, but with mod_unixd we should be able to use User and Group and that should work with original mpm.

mhlavac avatar Dec 17 '13 19:12 mhlavac

It seems that with mpm_itk everything still works as before. I've just created test domain with new Ubuntu 1310 and it works again :+1:

mhlavac avatar Dec 17 '13 19:12 mhlavac

Is it really needed to run each vhost under different user? I was looking into how mpm_itk works, and and it basically forks the process (in order to run under different user) and then work exactly as mpm_prefork, resulting into additional form per request.

Since lamp is not production environment, I would consider running whole Apache under lamp user, and use mpm_prefork (cannot use pmp_worker, since PHP is not thread-safe).

tomas-pecserke avatar Dec 18 '13 10:12 tomas-pecserke

Yes, you are actually correct. We can run everything under LAMP as that is most common use case, I would say even on developer machines in general, everyone runs all projects as one user.

Not only that, additional users would actually make everything harder for everyone as you would have to setup ACLs correctly.

To be honest I still see developers delete their cache, log, tmp with sudo rm -rf every day.

We can look into this. I am going to create 0.2.0-dev branch, with these changes in it and we can iterate on that. The road is not so long before releasing something more usable. I would also like to introduce a way how to define which things should be installed and which not. For example if you are developing in a team which has dedicated machine t o do CI you don't need Jenkins at your local machine at all.

mhlavac avatar Dec 18 '13 21:12 mhlavac

You are correct. For lamp everyone is going to use just lamp usrr anyway so ee can change this behaviour.

I am going to create new branch for version 0.2-dev of lamp and we can do this change there.

Makes sense. I would also like to introduce way how to include/exclude part of lamp installation. Looks as a good time to look into puppet, chef, juju again. Would make a lot of sense.

Tomáš Pecsérke [email protected]/a:

Is it really needed to run each vhost under different user? I was looking into how mpm_itk works, and and it basically forks the process (in order to run under different user) and then work exactly as mpm_prefork, resulting into additional form per request.

Since lamp is not production environment, I would consider running whole Apache under lamp user, and use mpm_prefork (cannot use pmp_worker, since PHP is not thread-safe).


Reply to this email directly or view it on GitHub: https://github.com/mhlavac/lamp-install-script/pull/50#issuecomment-30830365

mhlavac avatar Jan 03 '14 11:01 mhlavac