Yes, that's right: Clinker in the Cloud! Enjoy an exclusive and private Clinker installation with all the advantages of having your ecosystem in the Cloud.
Are you in the process of defining your ecosystem? If you are interested in reducing costs and risks, we encourage you to consider Clinker as one of your options.
Clinker Cloud puts at your fingertips everything you need to focus on the building and evolution of your projects. Creating your own infrastructure may look like a good option because it will be better adapted to your needs, however, you must consider that infrastructures are alive and need attention and care, and that implies that someone must provide those services.
Think about these inconvenients before deciding:
Redundant hardware at all levels (storage, servers, network...). Hassle-free ecosystem with a 99,99% hardware SLA offered by our IaaS provider.
Perimeter firewalls, private dedicated firewalls, IPS and an environment physically protected in a high security datacenter. Your data will always be safe.
Our ecosystem has a fixed cost and you pay what you get, without surprises.
Zero Infrastructure, guaranteed SLAs, backups and data recovery all done for you, work anywhere... Do you like it?
Your ecosystem can grow up as much as you need.
The computing capacity is always ready for your Software Development Ecosystem. The data has an only owner and that would be you.
Read these instructions while you wait for the download to end.
Clinker Virtual Appliance is an easy and simple way to enjoy Clinker. It is a virtual machine based on Debian GNU/Linux 6 (64bits) as operating system.
The closest scenarios to this distribution mechanism have a common denominator: They require a robust and reliable infrastructure. We will need hardware that fulfills the requirements, and if we wish to publish our ecosystem outside of our company or department, an internet connection with an uplink to support the users working from outside of the network.
What are the scenarios we can find out?
Advantages of this distribution mechanism.
Once the hardware is available you will only need to execute the virtual machine with VMWare Player, VMWare Workstation, VMWare vSphere Hypervisor (ESXi) or VirtualBox, and follow some basic configuration steps.
Its design allows the easy configuration of a DMZ, work behind the firewall, proxy or other network elements. Network traffic between users and the ecosystem will be limited to the standard ports HTTP (80) and HTTPS (443).
Storage is managed with LVM.
You can replicate your ecosystem to evaluate plugins, new versions, integrations,...
Hardware requirements depend on the tools used, number of projects and concurrent users working on the tools.