How FirePublish Works

FirePublish Enforces a Workflow With Your Web Applications

With FirePublish in place, sending files to a production web server is no longer an ad hoc process. Files are accounted for from the minute they are committed to the version control repository. From that point, the only way they can reach the production server is through a defined workflow, which among other things requires that the files pass through a testing environment.

FirePublish handles files that are added, updated, and deleted from your Subversion repository. So if you need to delete a series of files from your website, those modifications can be "published" to your test and production web servers the same as any other change.

FirePublish Makes Your Job Easier

When multiple developers are involved in a project, keeping track of changes can be difficult. Version control was created just for this purpose. However, while version control will keep you from overwriting another developer's changes locally, it cannot help you maintain that level of control through the full lifecyle. This is where FirePublish comes in.

	FirePublish Queue FirePublish manages a queue of files checked into your repository. From there you can easily push individual files, or entire groups, to the production web server. No longer do you need to guess at what files have changed since your last update.
	Logical Grouping of Files FirePublish also allows you to collect those files into groups that are part of the same update. For example, if you have a new section that you are preparing for a new product offering, grouping those files together will ensure that nothing is lost when those file sare ready to go live, no matter how many updates are made to them.