We have a public issue tracker on GitHub, where you can easily report any issues you may find.
You can use any external database. For optimal integration, we recommend using our automatically provisioned Amazon RDS PostgreSQL instances for your relational database needs.
You can access instance boot logs using the boxfuse logs command. For your application logs you should use a central log server. Great hosted solutions include Loggly, Logentries and Papertrail. You can read more about this in our blog post.
A health check timeout typically occurs for one of two reasons:
The first problem can be solved by either moving to a larger and faster instance, increasing
healthcheck.timeout or optimizing the application startup.
The second problem can be due to either the
healthcheck.path being incorrect,
healthcheck.port being incorrect or the ports configuration simply not matching the ports
opened up by the application. Example: the http port is configured to be 80, yet the application listens on 8080.
The solution for all of these is the same, carefully review your configuration and check the logs
to make sure everything matches.
When you first fuse an image for a Boxfuse application that hasn't been explicitly created in the Boxfuse Console, Boxfuse will automatically create that application for you. To do so, Boxfuse detects the any compatible JDBC drivers you have included and configures the application to use the correct type of database
Once the application has been created, the type of database it uses cannot be changed anymore.
This means that if you initially created the application without a database, or fused an image when it did not contain a JDBC driver, even adding a JDBC driver later will not trigger Boxfuse's autodetection anymore.
To use Boxfuse's database auto-provisioning anyway, simply delete your application in the Boxfuse Console and recreate it with the correct database type or fuse a new image based on a payload that contains a compatible JDBC driver.