Download the PHP package az-digital/az_quickstart without Composer

On this page you can find all versions of the php package az-digital/az_quickstart. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of az-digital/az_quickstart

Informations about the package az_quickstart

Arizona Quickstart

Demonstration/starter Drupal distribution and installation profile that packages various features consistent with community best practices and University of Arizona brand strategy.

A Complete Customized Drupal

AZ Quickstart is a complete customized version of the popular Drupal content management system, not an add-on to an existing Drupal-based web site. Previously, to start a new Drupal site you would prepare a web server and database, then install the core software following the instructions in its Installing Drupal document and the installation chapter in its user guide. This would produce a minimally functional web site with no content, which you could then customize by adding themes and modules to fit it to your needs. Increasingly, however, you can install Drupal distributions, which not only contain the core, but also complete sets of additions to make it almost immediately useful for a particular purpose, such as an online storefront. AZ Quickstart is the distribution that provides many of the features specific to the University of Arizona, and rather than an empty site, can include some demonstration content (which can nevertheless be turned off instantly).

How to Contribute

See our contributing document for detailed instructions on how to contribute including:

Where to Install Your Quickstart Site

The university's Campus Web Services group provides ready-to-use sites based on Quickstart for anyone who isn't comfortable with web development or system administration. Behind the scenes, a web hosting service called Pantheon hosts these sites, so in cases where people require more control and flexibility in a Quickstart site than these can provide, there are ways they can also host it independently on Pantheon, and many important university sites are already there. However, there are many other options for hosting web sites based on Arizona Quickstart; the only caveat is that anyone following one of these has to maintain their responsibility for keeping the system and web site secure and up-to-date. A generic hosting option that has been around for many years is known as LAMP: the combination of the Linux operating system, Apache web server, MySQL database, and PHP scripting language, so it is worth giving a more extensive example of using this, but many variations are common (for example, substituting Nginx for the Apache web server software).

System Requirements

Arizona Quickstart's system requirements are almost identical to Drupal's own requirements, in particular the requirements for Drupal 9. Some additional things that need emphasized or checked are:

Web Server Configuration

If your Quickstart site will be exposed to public view, and is anything more than an ephemeral development site, you should use TLS (SSL, the https:// rather than http:// in the URLs). There are now several easy and cheap ways to do this, from getting InCommon certicates through the University, the certificates available in AWS environments, or the free automatically renewable Let's Encrypt certificates. The Apache default settings will generally need some hardening (at least disabling obsolete protocols), but there are many guides on how to do this and online tools that can help. It's a good practice to wrap the configuration of the Quickstart site in Apache's <VirtualHost> directive, even if there will only be one on the server. There are options to add security-related headers from within the Quickstart site itself, but it doesn't hurt to set these in advance, using the Apache configuration, with things like

The more general Drupal web server requirements are not particularly demanding. Make sure the web server is functioning properly with a trivial static site before trying the Quickstart installation (an index.html file stuck somewhere), but note that you should change Apache's DocumentRoot directive for a new location after the initial test: Quickstart's DocumentRoot will be a directory created during installation (which can't already exist).

Database Server Configuration

The main point of Drupal's database requirements is that it does not support old versions of the server software, but does support several different variations in the software itself. Quickstart requires configuration with a MySQL or similar database, and a user set up within the database server with full rights to access this. In several recent Linux distributions the ultimate system administration account (root) has full administrative access to the database server without needing a password, but there is no sane way to pass these privileges into Quickstart's configuration, and in any case it is a best practice to create a dedicated administrative user for this purpose. A typical setup would look like:

Some old code examples combine the CREATE USER and GRANT in a single command, but MySQL 8 no longer supports this. WITH GRANT OPTION might be unnecessary in practice, but is not implied by ALL.

Install Using Composer

It's a good idea to make a directory where the non-privileged system user can write, but where the web server can also access. So for example

It should then be possible to install Quickstart directly in this directory:

This should produce a long list of messages, looking something like

This will have created a top-level directory (azqs in this example), within which there is a web subdirectory serving as the actual DocumentRoot for the web server. It's important to update the Apache configuration at this point to reflect this, so in the example there would be a DocumentRoot /var/www/drupalsites/azqs/web directive, and a corresponding <Directory /var/www/drupalsites/azqs/web> (to set things like AllowOverride All there). Once Apache has restarted with the new configuration, there are two ways to complete the installation. The web site itself will display a variation on the usual initial Drupal installation form (headed “Arizona Quickstart”), allowing you to fill in various fields with details such as the database user and password; but the initial build includes the popular drush utility (down in the vendor subdirectory), so a purely command-line installation is possible with something like

In this example, note that the database credentials match those set previously (other details shown here should also be customized with your own settings). One messy detail at the moment is that you may have to manually create a top-level config/sync directory (so /var/www/drupalsites/azqs/config/sync in this example). If all goes well, you will be able log in to the new site with the username and password you have set. One thing that will need immediate attention is the report at /admin/reports/status#error once you have logged in. There will probably be a Trusted Host Settings error, needing a manual change to your settings file, and notice of some directory permissions that need relaxed to allow the web server to write there.

Using Xdebug with Lando and VSCode

This repository contains the necessary config to run Xdebug inside a lando application container.

To start a debugging session, perform the following steps:

  1. In VSCode, go to the extensions tab.
  2. Type @recommended in the search bar.
  3. Install all workspace recommended extensions.
  4. Start lando with lando start.
  5. Start Xdebug with lando xdebug-on.
  6. At the bottom left of your VSCode window, click the little green icon.
  7. Choose Attach to Running Container... and select the appserver for your running lando instance.
  8. Once the new VScode window pops up, go back to the extensions tab.
  9. Type @recommended in the search bar.
  10. Install all workspace recommended extensions.
  11. In VSCode, go to the debugging tab.
  12. Click the green triangle next to Listen for XDebug at the top right.
  13. In VSCode, go back to the code tab.
  14. Set any desired breakpoints.
  15. You may now proceed with debugging.

Distribution update

When updating your codebase on an existing site, you should always check if there are distribution updates that need to be applied.

This can be done by users with the administrator role on your website at this path: /admin/config/development/distro

You should be able to see the upstream updates to be applied, after updating your codebase by employing the "Merge" strategy available under the "Advanced" accordion on that page.

All versions of az_quickstart with dependencies

PHP Build Version
Package Version
Requires php Version >=8.1
az-digital/arizona-bootstrap Version 2.0.27
az-digital/az-icons Version 1.0.2
citation-style-language/locales Version 0.0.22
citation-style-language/styles Version 0.0.561
composer/installers Version ^2.0
cweagans/composer-patches Version ^1.7
drupal/access_unpublished Version 1.6.0
drupal/antibot Version 2.0.4
drupal/asset_injector Version 2.21.0
drupal/auto_entitylabel Version 3.3.0
drupal/better_exposed_filters Version 7.0.2
drupal/blazy Version 3.0.12
drupal/block_class Version 4.0.0
drupal/block_field Version 1.0.0-rc5
drupal/bootstrap_barrio Version 5.1.12
drupal/bootstrap_utilities Version 3.0.1
drupal/cas Version 2.3.2
drupal/chosen Version 4.0.3
drupal/ckeditor_bs_grid Version 2.0.12
drupal/ckeditor_indentblock Version 1.0
drupal/coffee Version 1.4.0
drupal/config_distro Version 2.0.0-alpha2
drupal/config_ignore Version 3.3.0
drupal/config_ignore_readonly Version 2.2.0
drupal/config_provider Version 3.0.0-alpha1
drupal/config_readonly Version 1.0.0
drupal/config_snapshot Version 2.0.0-alpha1
drupal/config_split Version 2.0.1
drupal/config_sync Version 3.0.0-alpha3
drupal/config_update Version 2.0.0-alpha3
drupal/core-recommended Version 10.3.9
drupal/crop Version 2.4.0
drupal/ctools Version *
drupal/date_ap_style Version 2.0.2
drupal/draggableviews Version 2.1.4
drupal/easy_breadcrumb Version 2.0.8
drupal/embed Version 1.9.0
drupal/entity_embed Version 1.6.0
drupal/environment_indicator Version 4.0.10
drupal/exclude_node_title Version 1.4.0
drupal/externalauth Version 2.0.6
drupal/extlink Version 2.0.2
drupal/field_group Version 3.6.0
drupal/field_group_link Version 3.1.0
drupal/flag Version 4.0.0-beta5
drupal/google_tag Version 2.0.6
drupal/honeypot Version 2.1.4
drupal/image_widget_crop Version 2.4.0
drupal/imagemagick Version 4.0.2
drupal/inline_entity_form Version 3.0.0-rc20
drupal/intelligencebank Version 4.1.1
drupal/jquery_ui Version 1.7.0
drupal/jquery_ui_datepicker Version 2.1.0
drupal/jquery_ui_slider Version *
drupal/jquery_ui_touch_punch Version *
drupal/link_class Version 2.1.0
drupal/linkit Version 6.1.6
drupal/masquerade Version 2.0.0
drupal/media_entity_file_replace Version 1.3.0
drupal/media_library_edit Version 3.0.4
drupal/media_library_form_element Version 2.1.1
drupal/media_migration Version 1.0.0-alpha16
drupal/menu_block Version 1.13.0
drupal/menu_link_attributes Version 1.5.0
drupal/metatag Version 2.0.2
drupal/migrate_plus Version 6.0.4
drupal/migrate_queue_importer Version 2.1.1
drupal/migrate_tools Version 6.0.4
drupal/optional_end_date Version 1.4.0
drupal/paragraphs Version 1.18.0
drupal/paragraphs_admin Version 1.6.0
drupal/pathauto Version 1.13.0
drupal/quick_node_clone Version 1.17.0
drupal/redirect Version 1.10.0
drupal/role_delegation Version 1.3.0
drupal/search_exclude Version 3.0.0-beta1
drupal/seckit Version 2.0.3
drupal/slick Version 3.0.4
drupal/slick_views Version 3.0.3
drupal/smart_date Version 4.2.1
drupal/smart_title Version 1.0.0
drupal/smtp Version 1.4.0
drupal/token Version 1.15.0
drupal/views_bootstrap Version 5.4.1
drupal/views_bulk_operations Version 4.3.0
drupal/views_remote_data Version 1.0.3
drupal/viewsreference Version 2.0.0-beta10
drupal/webform Version 6.2.7
drupal/workbench_access Version 2.0.3
drupal/xmlsitemap Version 1.5.0
jjj/chosen Version 2.2.1
kevinrob/guzzle-cache-middleware Version 5.1.0
npm-asset/blazy Version 1.8.2
npm-asset/bootstrap-datepicker Version 1.10.0
npm-asset/easepick--bundle Version 1.2.1
npm-asset/jquery-ui-touch-punch Version *
npm-asset/slick-carousel Version 1.8.0
renanbr/bibtex-parser Version 2.2.0
seboettg/citeproc-php Version 2.6.2
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package az-digital/az_quickstart contains the following files

Loading the files please wait ....