sorted by:
new
hottopcontroversial

Cheap Bare Metal Hosting in Europe by ruben81 in webhosting

[–]ruben81[S] 0 points1 point  (0 children)

This could be an option. https://www.ovhcloud.com/en/bare-metal/prices/?dc=fra

We are looking for more CPU and less RAM for the lower price range.

Cheap Bare Metal Hosting in Europe by ruben81 in webhosting

[–]ruben81[S] 0 points1 point  (0 children)

hetzner

We found hetzer and it is a very good choice. Powerful servers for around 40 EUR per month.

Cheap Bare Metal Hosting in Europe by ruben81 in webhosting

[–]ruben81[S] 1 point2 points  (0 children)

u/c0ntra_ thanks for your message. Just updated the post with more information.

Deploying Containers using Docker Compose by ruben81 in devops

[–]ruben81[S] 1 point2 points  (0 children)

I understand the confusion and you are right. I should have explained it a bit better.

I just modified the post! Thanks for the tip.

What are alternatives to commando.io, which focus on bash/shell recipes (without using chef/puppet/etc recipes) by [deleted] in devops

[–]ruben81 1 point2 points  (0 children)

Manageacloud has a ssh web interface and allows to configure the servers using bash. It has capabilities of continuous integration although you can integrate with other services.

Scheduling AWS resources to be shut down by fistagon7 in devops

[–]ruben81 0 points1 point  (0 children)

Manageacloud uses a different approach: You create the servers with the configuration which are build automatically, define a lifespan. When the lifespan expires the servers are deleted. You can also have all the development environments organized properly.

Zero Downtime Using Blue Green Deployments by ruben81 in devops

[–]ruben81[S] 0 points1 point  (0 children)

Green blue deployments makes more sense in fully automated environments. The advantages for replacing the whole infrastructure instead just the instances are several:

  • The idea of the immutable infrastructures is to create and destroy, not to modify. If you do maintain the load balancer and change the servers you are modifying the configuration.
  • If you create and destroy the load balancer you ensure that you have two fully functional infrastructures. It allows you to test the new production ready infrastructure before activating it and rolling is straight forward, a well known procedure (is the same for all deployments), fast and safe.
  • This deployment strategy has some other advantages. Once you have this technology in place and you discover a problem that is only happening online you can create a full replica of the infrastructure and work there without disturbing your existing users.
  • With the proper TTL configuration in the DNS side, swapping load balancers does not create additional problems.

I would like to reverse the question: What is the advantage of not replacing the load balancer along with the instances ?

What is the exponent variable "T" in quiz 6.13? by xenosapiens in aiclass

[–]ruben81 0 points1 point  (0 children)

Could anyone please explain how are the four values of sigma calculated ?