So I'm trying out Slackware, I like it, I have old computers and it's faster than Debian 8. I currently operate a Debian 8 VPS but I'm working on a local machine at the moment.

After following the instructions here:

http://www.slackwiki.com/PhpMyAdmin

I kept running into problems with Forbidden, access to /phpmyadmin denied... There was some confusion since I'm used to /var/www/html not /var/www/htdocs, regardless I switched those around, but I was not able to get around this problem.

Looking at the symbolic links, when clicking on them, I was told "Broken link" so I suspect that could be a problem.

The phpmyadmin folder was in /usr/src/source/phpmyadmin where the symbolic link was set by:

ln -sf phpMyAdmin-XXX phpMyAdmin

While in the /var/www directory.

I don't know if it's obviously a bad idea to have phpmyadmin publicly accessible. Probably is.

I have the phpMyAdmin.conf in the /etc/httpd/conf.d directory

This is what I have in the phpMyAdmin.conf file

Alias /phpmyadmin /var/www/html/phpmyadmin

<Location /var/www/html/phpmyadmin>
Options Indexes FollowSymLinks
Require all granted
</Location>

I added the line

Include /etc/httpd/conf.d/phpMyAdmin.conf at the bottom of httpd.conf

After copying the folder to /var/www/html directly, I am able to get into phpmyadmin, but now I'm being prompted to install php5.5+ not what I have now which is 5.4.20 this came default with 14.1

Anyway, man I miss apt-get install

I'm not sure if my VPS provider uses Slackware as an OS I've seen Debian and CentOS on there. I'll probably stick to Debian 8 at the moment for the live server, but on these old computers, I wouldn't mind running Slackware for being faster.

So is it bad to do what I did? If so, how should I fix it?

Looking at my configuration for Debian phpmyadmin is in the /usr/share directory and there's an alias to it. So this is probably not good. I'm going to see about importing the debian phpmyadmin conf settings into the phpmyadmin conf file for slackware.

Why didn't you just use the SlackBuild? SlackBuilds are kinda like apt-get install, except the it is just a shell script that will download, compile (if needed), and install the programs. The SlackBuild maintainers will even let you know if there's any dependencies (for phpmyadmin, there aren't any). If you really want it to be in /var/www/html instead of the Slackware (and apache) default of /var/www/htdocs, you can adjust the DOCROOT variable before you run the SlackBuild. Or you can just symlink the two directories if it is just a habit to use /var/www/html.

https://slackbuilds.org/repository/1...rk/phpmyadmin/

Hey thanks for your help, I see the slack builds and I wasn't quite sure how to use them.

I will try that, thanks.

They're pretty straightforward Just download the SlackBuild tar.gz archive. This contains everything but the source that you'll need. Unpack that in any directory. Then go into that directory and download the source of the program. Once completed, as root, run the SlackBuild (generally called the program-name.SlackBuild, so in your case, phpmyadmin.SlackBuild). When everything is done, install (or upgrade) the resulting package.

Further details can be found on their site's howto page https://slackbuilds.org/howto/

Once you understand the process and are a bit more familiar with it, have a look at a more automated solution like sbopkg

That was great, I had to open up the SlackBuild file to change the version. Everything went well. I'll have to implement this on future installs. I'm actually working on re-installing PHP7 at the moment, I just removed the old on.

Thanks a lot for your help, now I'm going to see if I have that problem of access.

Glad it helped. Good luck with everything and feel free to ask any other questions.

As I said before, once you get more familiar with the process slackbuilds.org (SBo, as it is commonly referred to on here) uses for their SlackBuilds, have a look into something like sbopkg to better simplify your usage. But, I would wait until you have a decent understanding of how things are supposed to work, so if something goes wrong, or you need to change something, you'll better understand what you need to do

Yeah thanks a lot for your help.

I am currently developing websites on a Debian LAMP server and since my machines are old, every bit of performance I could squeeze out... Although with a single core, 4GB of RAM, I can have like 50 tabs open at once before I start running out of memory. Everything is snappy thanks to Linux. If it was Windows 7 or Vista, this computer could barely run.

The other one running slack is meant for Windows XP.

So far I have a LAMP server on slack so thanks for that.

I'd definitely like to look at the faster method so that I can easily "drop in a new server" so to speak.

I'm wondering if NGINX and Slackware would make a fast server.

Under normal circumcantes, you will have no benefit from nginx. Files are not faster served,
if your server is under heavy load by http-accesses nginx might do better.

By the way, you might be interested in Adminer for mysql/pgsql/sqlite ... access, instead of phpmyadmin. You just need to put a single php-file in an http-accessable folder, that's it.

Franzen

Hi franzen,thank you for the information. It might be bad that I've gotten used to PHPMyAdmin for working with my database.

I had it in mind that my next server setup would be LEMP, with NGINX and Postgresql.

I haven't had a use for asynchronous servers yet.

At this point I'm working on freelancing.