|
| [WB22] App Server Success |
| Iniciado por guest, 07,mar. 2018 06:19 - 2 respuestas |
| |
| | | |
|
| |
| Publicado el 07,marzo 2018 - 06:19 |
FINALLY - got a working and reliable WebDev App Server running on a 64 bit Linux VPS. I'm running the newest HFSQL server available in English 22.68 and the newest app server 22.73h.
It required a VPS hosting company that allowed me to upload and install the Turnkey Linux LAMP iso. I have tried a ton of distros, but the only ones that worked were ones that had a complete LAMP stack that was part of the installation. I only found two, BunsenLabs and Turnkey Linux.
They are both Debian 8 (Jessie) derivatives. I tried base Debian 8, but in only installs the web server during the installation. Something in having the complete LAMP install changes the result. So far I have not been able to make the App Server work on anything based on Debian 9.
I also spent about 40 hours getting a custom bash configuration script developed. It automates most of the App Server setup.
So far I have only deployed the 10 user server. But it has successfully deployed on bare metal, a VPS instance and several VirtualBox instances. All the utilities work and I have also been able to deploy several of the Example web sites, both directly and through deployment packages.
I did have to sort through several suggestions on the WebDev boards regarding configurations not in the official documentation and also had to modify some of the PCSoft directions as they were wrong. Finally found a set of configurations that work.
So yes, with the right Linux distro, the current version of the App Server is installable and usable. |
| |
| |
| | | |
|
| | |
| |
| Publicado el 07,marzo 2018 - 06:45 |
Congratulations.. WAS on Linux is good, easy to manage, and without the expense of a MS license. Our setup uses the CentOS 7 distro. It took a bit to figure out the nuances, but now we can spin up a new server in about an hour.
We find that the configuration is simplified by not using a FTP server like vsftp as described in the docs, but just SCP through SSH as WB 21 and up now supports. Its much more secure and simplifies permissions at the WAS account level.
When doing major updates, we just spin up a new server instance, install our app, test, then cut over the IP to the new server.. No down time, and easy roll back if needed. |
| |
| |
| | | |
|
| | |
| |
| Publicado el 07,marzo 2018 - 09:30 |
| I just block port 21 in the firewall and use sftp. Is the production server like the 10 user version, or will I run into additional issues? |
| |
| |
| | | |
|
| | | | |
| | |
|