05-16-2021, 06:36 PM
I'm trying to find a really quality tutorial providing all of the steps that will finally lead to installing a WordPress site without a panel. The OS has to be Debian 10 with Nginx. I've worked my way through loads of tutorials from Google but haven't had success yet. They must be missing steps that are taken as "given" and "for granted" by those creating WP in a non-panel environment.
My issue is not with installing WP from the command line. My issue is with setting permissions. It may also have to do with my VPS security settings with SELinux and requirement for having the correct side script language in an .htaccess page. And also having more than one .htaccess in more than one location. Preferably I don't want to use .htaccess at all, as like the SELinux cop out for disabling it, I think .htaccess is also an overrider of security.
I've done basically everything with the permissions. Like I always disable SELinux as standard. I've learned how to open all of the ports. How to check how to listen to them. How to set up users and CHOWN them. How to set up the right permissions for the folders and files. Yet I've been unsuccesful with setting up WP. I must be doing something wrong.
I'm comfortable with how VestaCP set up its filing system. I have success with WP every time with VestaCP. I can do it with eyes closed. I install WP with VestaCP from the command line and basically only use the database and file setup and server of VestaCP. I only need to add the command below at the end of the installation so I can install plugins and themes in WP directly from the WP Dashboard.
chown admin -R *
However when I install WP from the command line in a non-panel environment in Apache and use the above chown command for admin, it says no such user. When I try to create a user admin in a non-panel environment I can't do so. I can create non-admin name users, but not admin. I get it that the file path to the domain in apache and nginx is /var/www/html and the virtual host .conf files in etc/conf. I've worked through tons of step to set up permissions for those folders. I get how they are set up but am obviously missing something as in most cases I can't get WP admin set up right. Even when I nano the content of index.html, it fetches the generic Apache index.html from somewhere else. When I delete index.html from the root of the domain apache still gets another index.html that is the generic Apache page. I know about cache and deleting it everywhere including in your OS. Whatever I do the index.html stays with the default original Apache index file, and if I fiddle too much everything breaks and it goes to 404 or cannot find.
I need a really good tutorial for getting the folder and file structure, and permissions as well as users right. There has to be something that one does to for example create one's own folder structure like VestaCP does under home/admin/web/domain.com/public_html/ and then get it pointed to the var/www/html direction (where in VestaCP there are no sub-folders and files) but where Apache wants it to be, and ditto with the dot.conf virtual host files, of getting the permissions and users right. A step by step tutorial with no steps missed. I get it how to create .htaccess. But the standard wording provided does not make any difference. Looks like .htaccess has to be copied to other Web folders and not only the root folder of the domain.
Installation of php is also an issue. There are millions of ways of doing it. But I think that may be an issue too. I know how to do the initial installation to set it up for a specific version of php before one installs php. But I'd like to get a simpler way of doing it. I don't feel as in control with php as i do with MariaDB.
Until I get the above right, I'm sticking with the Debian Fork by dpeca of myVestaCP as it works OK for me. But I'd be really happy with myself if I could find a simple minimalist way of getting to use WordPress with no panel at all from the command line. I know how to use MariaDB, I can create a database and user from the command line. I can give the database a user and permissions. I know my way into phpmyadmin. I can do some edits in phpmyadmin, import databases, create new one. I can create WP from the command line. I can create a static Website from the command line. But the permissions of the Administrator of WP as well as where Apache fetches everything has me at a loss. I don't get it when I delete index.html why and where Apache fetches its default page. Even when cache and everything associated with cache has been removed.
My issue is not with installing WP from the command line. My issue is with setting permissions. It may also have to do with my VPS security settings with SELinux and requirement for having the correct side script language in an .htaccess page. And also having more than one .htaccess in more than one location. Preferably I don't want to use .htaccess at all, as like the SELinux cop out for disabling it, I think .htaccess is also an overrider of security.
I've done basically everything with the permissions. Like I always disable SELinux as standard. I've learned how to open all of the ports. How to check how to listen to them. How to set up users and CHOWN them. How to set up the right permissions for the folders and files. Yet I've been unsuccesful with setting up WP. I must be doing something wrong.
I'm comfortable with how VestaCP set up its filing system. I have success with WP every time with VestaCP. I can do it with eyes closed. I install WP with VestaCP from the command line and basically only use the database and file setup and server of VestaCP. I only need to add the command below at the end of the installation so I can install plugins and themes in WP directly from the WP Dashboard.
chown admin -R *
However when I install WP from the command line in a non-panel environment in Apache and use the above chown command for admin, it says no such user. When I try to create a user admin in a non-panel environment I can't do so. I can create non-admin name users, but not admin. I get it that the file path to the domain in apache and nginx is /var/www/html and the virtual host .conf files in etc/conf. I've worked through tons of step to set up permissions for those folders. I get how they are set up but am obviously missing something as in most cases I can't get WP admin set up right. Even when I nano the content of index.html, it fetches the generic Apache index.html from somewhere else. When I delete index.html from the root of the domain apache still gets another index.html that is the generic Apache page. I know about cache and deleting it everywhere including in your OS. Whatever I do the index.html stays with the default original Apache index file, and if I fiddle too much everything breaks and it goes to 404 or cannot find.
I need a really good tutorial for getting the folder and file structure, and permissions as well as users right. There has to be something that one does to for example create one's own folder structure like VestaCP does under home/admin/web/domain.com/public_html/ and then get it pointed to the var/www/html direction (where in VestaCP there are no sub-folders and files) but where Apache wants it to be, and ditto with the dot.conf virtual host files, of getting the permissions and users right. A step by step tutorial with no steps missed. I get it how to create .htaccess. But the standard wording provided does not make any difference. Looks like .htaccess has to be copied to other Web folders and not only the root folder of the domain.
Installation of php is also an issue. There are millions of ways of doing it. But I think that may be an issue too. I know how to do the initial installation to set it up for a specific version of php before one installs php. But I'd like to get a simpler way of doing it. I don't feel as in control with php as i do with MariaDB.
Until I get the above right, I'm sticking with the Debian Fork by dpeca of myVestaCP as it works OK for me. But I'd be really happy with myself if I could find a simple minimalist way of getting to use WordPress with no panel at all from the command line. I know how to use MariaDB, I can create a database and user from the command line. I can give the database a user and permissions. I know my way into phpmyadmin. I can do some edits in phpmyadmin, import databases, create new one. I can create WP from the command line. I can create a static Website from the command line. But the permissions of the Administrator of WP as well as where Apache fetches everything has me at a loss. I don't get it when I delete index.html why and where Apache fetches its default page. Even when cache and everything associated with cache has been removed.
