View Single Post
  #2  
Old 24th May 2013, 01:07
monkfish monkfish is offline
HowtoForge Supporter
 
Join Date: Mar 2013
Posts: 106
Thanks: 9
Thanked 15 Times in 14 Posts
Default

Do you mean building an aps compliant package?

http://www.apsstandard.org/

Or do you mean deploying a package to a site on your server? in which case...

- update package list
- select the package you want to deploy
- pay some attention to the "settings" tab - required dependencies and compatibilty is listed there
- hit the big button that says "install this package"

- you will be given a choice of which site to install it on, optionally a subfolder in there. You might like to ensure you have "cleaned" necessary web folders first.
- each package has its own "predefined" settings for you to complete, eg username/password for any web admin, site title and other settings.
- the package will be installed to the required location in its "virgin" state
- log in to the package and begin configuring.

Most updates if provided would occur inside the package you installed. eg. Wordpress updates are handled when you log in as your wordpress admin. A reinstall from within ispconfig will redeploy the basic shell again, and *may* wipe out any database settings etc.

- if the package to be installed required a SQL database, the database name seems to be chosen automatically based upon client number and instance number, eg. c0aps1, c0aps2 etc.

- once the base package is installed, its up to you to check security, patches, updates etc.

- If you have a test config, eg vmware box or similar, you might like to play with that - install/reinstall/remove, configure etc to see exactly what the capabilities are and what to expect from the installer. The functionality is a big leap forward and well worth using ispconfig. For aps compatibilty alone I thank the developers!

- structure-wise, my understanding is that the aps package files are downloaded to and parsed from the ispconfig folder interface/web/sites/aps_meta_packages. When you select a package to install, the package itself is downloaded and deployed from the ispconfig folder server/aps_packages. There are also the tables inside ispconfig database - aps_instances for installed packages and aps_packages for available packages. VERY rarely I have to empty aps_packages table and remove files in aps_meta_packages folder before resyncing the packagelist. There's a separate discussion on glitches seen with the installer interface.

- finally, be aware that *some* packages may not show as current with aps installer. Again, there's a separate thread round here for glitches other users have seen.

Last edited by monkfish; 24th May 2013 at 01:15. Reason: added, and again
Reply With Quote