Thanks to Cloud Foundry’s support of buildpacks it’s very easy to deploy mostly any app of any language to anynines.
This of course includes the Go language.
Derived from Heroku’s Go buildpack Michael Jemala was so nice to create a slightly modified Cloud Foundry buildpack for Go. As all Cloud Foundry buildpacks can also be used on anynines it’s just a matter of minutes to get a Go app running. (more…)
First of all the most obvious question has to be discussed:
Why we can’t just use cron for scheduled jobs?
An essential part of a PaaS is to isolate running application instances from another. Therefore all application instances run in so called Warden containers. Warden is an operating system level virtualization framework shipped with Cloud Foundry, the foundation of anynines.
Most Warden containers will run application instances that will never need a CRON daemon. Running CRON jobs on application servers is generally not a good idea as it creates a coupling between application delivery and background processing. (more…)
Per default every application deployed on anynines is accessible via a subdomain of a9sapp.eu for both HTTP and SSL protected HTTPS.
However, in most cases applications should be accessible via a custom domain and, of course, this should be also possible via HTTP and HTTPS.
Anynines is based on Cloud Foundry, an open source PaaS. Hence, it is pretty easy to import your own domains and let them point to your application using functionality provided by Cloud Foundry. The anynines team has then added the missing link and created support for custom SSL certificates to protect your custom domains.
Running your applications on anynines gives you the possibility to set up an SSL certificate for your custom domains.
This blogpost guides you through the process of mapping your domain to an application running on anynines, getting and importing a SSL certificate to make your application available through the secure HTTPS protocol. (more…)