- What technologies can I use with Tugboat?
- Does Tugboat work with Acquia Cloud?
- Does Tugboat work with Pantheon?
- Do you provide production level hosting?
- Do you support self-hosted git repositories?
- How many repositories can I add to a project?
- I don't see a prebuilt service image that I need. Do you support it?
- Can I use my own images in Tugboat?
- Can I import an existing database into a preview?
- Can I have SSH access to a preview?
- How does Tugboat deal with sending email?
- If I merge a pull request into a base preview's branch, will the base preview automatically update?
- If a base preview is updated, will previews built from it automatically update with those changes?
- Why are Docker volumes not supported on Tugboat?
Tugboat supports pretty much anything that runs on Linux. Look through our prebuilt service images to see what we currently have available. If something that you need is missing, let us know, and we will work with you to get it added to the list.
Yes. Quite a few projects using Acquia Cloud have used Tugboat quite successfully.
Yes. We even have a tutorial to show you how.
No. Tugboat previews are intended to be short-lived, and do not come with the sort of stability or support guarantees needed to host a production application.
Yes. You can connect to a generic Git provider from the project creation page.
There is no limit to the number of repositories you can add to a Tugboat project. Limits are imposed on the number of previews that can be created in a project at any given time, based on the disk quota of the project and how big each preview is.
We add new prebuilt service images as users
need them. If there is something you need that we have not yet added,
let us know, and we will work with you to try to
get it added to the list. Alternatively, you are free to choose a generic
service image, such as
ubuntu and install any packages you might
We do support pulling Docker images from any registry that is internet-accessible. If your registry requires authentication, you can set that up in your Tugboat repository settings.
There are a couple of caveats to using your own images:
- We do not support images that define volumes
- We assume
shis available in the path, because Tugboat executes commands directly in the container with it
- If you want your git repository cloned to your service container, we assume
Yes. In order seed a database, you will need to be able to access a copy of it from your Tugboat previews. We generally recommend using SSH, but you could accomplish this however works for you. We generate unique SSH keys for each repository that is linked to Tugboat, which you can use to safely access remote assets. See this example for how you might do this with MySQL.
No. Direct SSH access to a preview is not possible. However, shell access is provided in both the web interface and the command line tool.
Tugboat makes a best effort to capture outbound email. Using the local
sendmail or the SMTP server at
$TUGBOAT_SMTP will result in email being
captured by Tugboat. These captured emails are only saved for as long as the
Preview that sent them exists.
Tugboat does not attempt to capture any other outbound SMTP server connections, so if you are concerned with sending emails to customers from a QA environment, be sure to update your application configuration to use Tugboat's SMTP server.
Yes. Base previews are automatically updated daily at 12am ET. This frequency and time of day can be changed in a repository's settings. It can also be disabled if you prefer to update your base preview manually.
By default, no. However, there are two repo configuration options that will enable this functionality.
Tugboat has a concept of Base Previews. Base Previews provide Tugboat with a starting point, from where it can build new previews. The advantage of Base Previews is they drastically reduce preview build times as well as the amount of space a preview occupies on disk. This is because under the hood Tugboat is committing the entire state of the container (including files, databases, etc), so all the new Preview needs to do is run the build steps without importing a database or other required assets.
If you'd like to use your own Docker images, here's the repo we use to make an image Tugboat compatible: https://github.com/TugboatQA/images