Skip to main content

Processes and tools Agaric uses to develop

We have a number of processes and tools we use as we develop:

  • Local development: we all develop locally on our own computers and push each change to a common code repository which we maintain.

  • Each task including new features, bugs or changes are kept track of as an issue ticket. These tickets will be accessible to Urban Edge staff as well as ourselves. Here is where we can track progress in code changes, elaborate on details and generally where we keep track of the hundreds of small issues that will come up.

  • Resources allowing, we use automated tests which emulate a human's interaction with a browser to make sure new work we does not unknowingly break site functionality. This ensures a solidly functioning site even as major changes take place.

  • We have experience managing a wide range of servers, server environments, or specialized hosting environments, and related technologies:

    • We have written our own battle-tested server deployment code, which securely pushes changes in code to any target location.
    • Deployments can run manually or to a desired level of automation, such as always deploying to a staging website automatically on a successful build, and then manually progressing to live after review.
    • Our existing deployment tools can handle configuring a virtual (or physical) server from the ground up, or else function within a variety of PHP-based website hosting providers.
    • Additionally, we can support container-based environments by providing docker container configurations for running the required services.
    • Dependent upon the hosting platform, we also manage additional security and reliability features, such as sites having automated system updates, virus scans of uploaded files, custom backup schedules, additional firewall protections, monitoring services, or other customized needs.
    • We can also work alongside existing IT service providers with recommendations regarding things you may already manage, such as CDN (content delivery networks), email, or DNS (domain name) changes that may be needed.

Read more about our tools for environment management and development.

Comments

Add new comment

The content of this field is kept private and will not be shown publicly.

Markdown

The comment language code.
CAPTCHA
Please help us focus on people and not spambots by answering this question.