Deploy4Me - a service that deployed itself

What happened is what we have been waiting for. Our idea was embodied in the stone online service.
Having made a long way from the idea to the service, through the mountain of code, the walls of tickets and the sea of ​​tests, one can say with confidence - we started.

Our service puts software in the cloud. Mostly large server products, but there is also room for small programmer environments.
')

What is Deploy4Me?

Deploy4Me is a service for installing business software in the cloud without coding, reading manuals, using tambourines and other shaman devices. According to the principle of Next, Next, Next.

How did the service idea come about? When the phrase “Now we will quickly install and ...” was heard again, and a long experience in IT suggested that “now” is an indefinite concept, and sometimes tending to infinity. Here we thought, why not make the installation service so that, in the foreseeable time and without blunders, put the software in the cloud. This is how the idea of ​​Deploy4Me was born.

Of course, I had to sweat, the project dates were shifted a couple of times, at one time they even succumbed to thoughts about finding investments and tried to find them. But still - succeeded. Implemented everything they wanted. Without investment and in a reasonable time.

How does the service work?

Deploy4Me works with the Amazon cloud (currently only with it). The main feature was access to the user's own cloud. It is in the cloud of the user that we install the software. So, this is not a hosting that resells the power of Amazon. The advantage is that you have full control over your virtual machines . Wanted - removed the connection to Deploy4Me, and all - you're in the house. Added connection - and again you can continue the installation.



The number of cloud connections is unlimited. This is convenient if you need to install something in the customer's cloud.



A large amount of time and effort was spent on implementing the interface of working with software. I wanted to make it as clear and convenient as possible. So there was a copy, merge, split, add and delete servers in the interface. Each function was thought out and tried. For example, the combination takes into account compatibility with the operating system and the possibility of sharing ports.

How did the service unroll itself?

When we were preparing for release, it was time to deploy the combat infrastructure , wiki, ticket system and blog. Everything is good, but, having tried to use our own service for this, we came across various restrictions. We are IThniki ... and the infrastructure is such a thing. I wanted to put a separate database. We want it all. Really we did a service, and we can’t install our servers through it. This is ridiculous. As they say, if you do not use your product yourself, others will not use it either.

After long debates whether to add functions now or postpone, emotions prevailed and for another 2 months we sat down for coding and testing. So the ability to separate the database from the frontend has been implemented!
As an example of WordPress with a separate database:



Our happiness did not know the end, until the thought crept in. The problem is this: there are 2 farms, each farm has a front and a database. And why ... not to combine the bases on one server and also on one port =) It is said - done.
This is how the database Jira and Confluence look like:

What's next?

Plans for the development of many. We will continue to communicate with customers. Develop partnerships with software manufacturers that can be installed through our service. Improve and add tasty. There are a couple of unrealized aces in the sleeve =)
Write reviews and suggestions, use Deploy4Me .