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 your logs using the boxfuse logs command. We strongly recommend configuring your application for AWS CloudWatch Logs as this gives you many essential features like log aggregation, live tailing, filtering and more. Also if you are on the JVM, make sure to integrate our Logback or Log4J2 appender.
CloudCaptain instances come with no SSH on board by design. Instead we provide alternative more scalable and secure ways to accomplish common tasks such as accessing logs, remote debugging, or monitoring.
CloudCaptain offers you two different ways to accomplish this as documented on our database page.
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 CloudCaptain application that hasn't been explicitly created in the CloudCaptain Console, CloudCaptain will automatically create that application for you. To do so, CloudCaptain 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 CloudCaptain's autodetection anymore.
To use CloudCaptain's database auto-provisioning anyway, simply delete your application in the CloudCaptain Console and recreate it with the correct database type or fuse a new image based on a payload that contains a compatible JDBC driver.