Download the PHP package crazedsanity/webdbupgrade without Composer

On this page you can find all versions of the php package crazedsanity/webdbupgrade. 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 crazedsanity/webdbupgrade

Informations about the package webdbupgrade

CS Web DB Upgrade

NOTE: this documentation is a work in progress, so take it as more guideline than rule. If you find something wrong with it, fix it and let me know through a pull request or however you'd like... or tell me about it. Or deal with it... whatever you prefer.

Preconceptions

CS Web DB Upgrade is built with a few preconceptions about your web application.

  1. there is a concept of a "production" application
  2. there is a test environment in which changes are tested
  3. upgrades are scripted (schema, database values, filesystem things, etc)

The system can be configured to automatically upgrade every time a page is viewed, via a custom shell script, or... however you want. It's your application.

What It Does

CS Web DB Upgrade is built to make upgrading a database-driven web application seamless. Instead of manually changing things in a certain sequence, automate that process by scripting it!

The Old Way:

  1. Manually "mark" the site as being in maintenance (replacing the site with one that responds to all requests with "down for maintenance" or some such)
  2. Manually update the code (overwrite it by extracting a zip, or using an SCM command-- or )
  3. Manually run schema changes
  4. Manually update existing records
  5. Manually fix existing configuration files
  6. Manually fix existing misc files (eg. paths for images)
  7. Hope things worked so far... if not, fix them, maybe do some praying and sweating
  8. Manually "unmark" the site as beinig in maintenance mode (see #1)

Did you see a pattern?

Meet your savior! This system adds the ability to allow your system to upgrade itself. Whenever you increment the version in your VERSION file, it can run a custom script that will do everything you need AND keep others out until it is done. Once the system is updated, the next thing to touch the code containing the upgrade system will cause it to run.

The New Way:

  1. Manually (or automatically) update application
  2. Run the upgrade script (generally runs automatically when the application is used)

That's it! If the upgrade breaks for any reason, a special "lock file" will automatically put your application into "maintenance mode", preventing users from hitting the database. And this frees you from having to do anything special in order to turn on that "maintenance mode." Yay!

How to Work With CS Web DB Upgrade

These steps help you get going with as little fuss as possible. Once you're familiar with the system, you'll be able to do just about anything you like.

Create a file, . The "main" section is the most important. Here's a sample:

The flow should be somewhat obvious. Each index (excluding "main") is parsed as a version. So the upgrade path is:

0.0.1 -> 0.0.2 -> 0.0.2 -> 0.1.0 -> 0.3.5-ALPHA1 -> 0.3.6 -> 1.0.0

So, if there's an existing installation that has a version in the database of 0.2.0, all scripts from 0.3.5-ALPHA1 and beyond are run, to get it to the current version, which is probably at least 1.0.0 (though it could easily be 1.0.1 or higher; not all upgrades require scripted changes).

All versions of webdbupgrade with dependencies

PHP Build Version
Package Version
Requires php Version >=5.3.0
crazedsanity/lockfile Version ^0.1
crazedsanity/database Version ^0.4
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 crazedsanity/webdbupgrade contains the following files

Loading the files please wait ....