As developers ourselves, we wanted to create a central system flexible enough to work with any Git provider or SaaS system we chose. Our goal was to build a product that worked with any development environment our users have set up, and could also securely and quickly deploy to any Linux server while handling optional post-build commands.
We never recommend running your application or website as the root user. Instead, set up your servers with the restricted user that has only read/write permissions for the applications being deployed. This can be done by installing your Stackahoy SSH key in that user's home directory on the server, or by simply using the user's SSH password.
On the server-side of Stackahoy, we take every precaution to provide the most up-to-date and industry standard practices to secure your information. Stackahoy uses cryptographic SSL and SSH protocols to handle all connections - from the browser to the database. Stackahoy implements NSA-approved 256 bit cryptographic algorithms to encrypt and ultimately store all corresponding private keys and passwords.
Stackahoy currently only supports Git. Depending on feedback we may implement support for Subversion or Mercurial in the future. Please let us know if you're interested!
Stackahoy uses the encrypted Secure Shell protocol for every aspect of a migration. Once a secure connection is made, Stackahoy analyzes the head of the branch being deployed with what's currently on the server and only updates files that have changed (which are then reported to you in real-time).
Stackahoy interprets the
.gitignore file(s) in the codebase to determine which
files and directories should be ignored or negated during a deployment.
Yes! Authorization with either SSH keys or passwords works great.
We do not support Microsoft products at this time.
Post deployment command are executed as [bash] commands as the user which is
set up for the server it's being deployed to. The applications should either be
in the user's
PATH or in the