Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Requirements tests before setup #49

Open
wuuti opened this issue Feb 5, 2015 · 3 comments
Open

Requirements tests before setup #49

wuuti opened this issue Feb 5, 2015 · 3 comments

Comments

@wuuti
Copy link

wuuti commented Feb 5, 2015

The setup script should test the modx requirements in advance and print out missing ones (like "you need curl for package management to work") together with solutions (on ubuntu apt-get install... ) tailored for your system and an explanation why you need it.

This would make installing for unexperienced users anytime or for experienced users in unknown environments much easier. And as an addon the setup could give you hints for better adjusted settings (e.g. for better performance, change memory_limit to XXX or change db-setting xy to abc...).

@mindeffects
Copy link
Contributor

I used this for my fresh Ubuntu server (taken from the shell history):

apt-get install apache2
service apache2 restart
a2enmod rewrite
service apache2 restart
apt-get install php5 libapache2-mod-php5
service apache2 restart
apt-get install mysql-server php5-mysql mysql-client
service mysql restart
## apt-get install libapache2-mod-auth-mysql phpmyadmin
apt-get install php5-json php5-curl php5-gd php5-imagick
service apache2 restart
cd /var/www/html
wget https://raw.githubusercontent.com/craftsmancoding/modx_utils/master/modx_ready.php

Could need some love and compression. ;-)

@Mark-H
Copy link

Mark-H commented Feb 6, 2015

How would this be different from the tests screen it shows now?

@wuuti
Copy link
Author

wuuti commented Feb 6, 2015

It could give you adcive how and why to solve problems, not only the information that problems exist. May help for #45 and #57. And the timezone setting is not part of the existing tests screen, you won't even see it if your timezone is not set.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants