Le 02/12/2017 à 16:25, Brian Mathis a écrit :
> You could write a script to open the permissions, apply updates using
> something like http://wp-cli.org/, then close the permissions again. Run
> it through cron so you get updates in a timely manner.
I just published a detailed blog post about upg
Le 04/12/2017 à 13:58, Nicolas Kovacs a écrit :
> find $WPDIR -type f -exec chmod 0664 {} \;
Oops. 644, not 664.
:o)
--
Microlinux - Solutions informatiques durables
7, place de l'église - 30730 Montpezat
Site : https://www.microlinux.fr
Blog : https://blog.microlinux.fr
Mail : i...@microlinu
Le 02/12/2017 à 16:25, Brian Mathis a écrit :
> You could write a script to open the permissions, apply updates using
> something like http://wp-cli.org/, then close the permissions again. Run
> it through cron so you get updates in a timely manner.
Here's a little script I wrote to automatically
Le 03/12/2017 à 23:59, Pete Travis a écrit :
> TL;DR my process is:
> - Make a list of real humans that need to work on the site
> - Assume the web server user should have at least read access on all
> files in the site documentroot, or we'd put them somewhere else.
> - Make a list of directories (
Hi Niki,
The principle to work by here is 'least required access'. There's two
functional types of users we care about, the one executing the PHP
code (probably apache or php-fpm) and admins like yourself with
FTP/shell access. Upstream wordpress documents application write
requirements at
https
Le 02/12/2017 à 16:25, Brian Mathis a écrit :
> You could write a script to open the permissions, apply updates using
> something like http://wp-cli.org/, then close the permissions again. Run
> it through cron so you get updates in a timely manner.
This is EXACTLY what I've been looking for. I'v
> Am 02.12.2017 um 22:14 schrieb Nicolas Kovacs :
>
> Le 02/12/2017 à 10:30, Nicolas Kovacs a écrit :
>
> ==> Reminder: this is actually the question I'm asking in my post.
Oh, we all read (only) what we want :-)
> So I'm finally coming to my question. How problematic is it really to
>> have
> Date: Saturday, December 02, 2017 22:14:19 +0100
> From: Nicolas Kovacs
>
> Le 02/12/2017 à 10:30, Nicolas Kovacs a écrit :
>
> ==> Reminder: this is actually the question I'm asking in my post.
>
>> So I'm finally coming to my question. How problematic is it really
>> to have the apache use
Le 02/12/2017 à 10:30, Nicolas Kovacs a écrit :
==> Reminder: this is actually the question I'm asking in my post.
> So I'm finally coming to my question. How problematic is it really to
> have the apache user and group owning the stuff under /var/www?
:o)
--
Microlinux - Solutions informatiqu
Am 02.12.2017 um 14:27 schrieb Nicolas Kovacs :
>
> Le 02/12/2017 à 14:19, Leon Fauster a écrit :
>> I would build a rpm package of wordpress (everything can be defined
>> there like permissions etc)
>
> The initial question was: WHAT permissions?
The application design should have considered
You could write a script to open the permissions, apply updates using
something like http://wp-cli.org/, then close the permissions again. Run
it through cron so you get updates in a timely manner.
~ Brian Mathis
@orev
On Sat, Dec 2, 2017 at 8:27 AM, Nicolas Kovacs wrote:
> Le 02/12/2017 à 14:
Le 02/12/2017 à 14:19, Leon Fauster a écrit :
> I would build a rpm package of wordpress (everything can be defined
> there like permissions etc)
The initial question was: WHAT permissions?
> and disabling the automatic update
> function in wordpress. Build once it can be installed on all (two
>
> Am 02.12.2017 um 10:30 schrieb Nicolas Kovacs :
>
> Hi,
>
> Until a few months ago, when I had to setup a web server under CentOS, I
> assigned (I'm not sure about the correct english verb for "chown"ing)
> all the web pages to the apache user and group. To give you an example,
> let's say I h
Hi,
Until a few months ago, when I had to setup a web server under CentOS, I
assigned (I'm not sure about the correct english verb for "chown"ing)
all the web pages to the apache user and group. To give you an example,
let's say I have a static website under /var/www/myserver on a CentOS
server ru
14 matches
Mail list logo
