I have a running dev installation of a dockerized wordpress project( via docker-compose) and was wondering what would be the best approach to deploying it to Azure. Most tutorials assume you are starting from scratch however I already have an installation and was wondering if I just need to integrate the azure-cli to the compose or setup an azure and migrate what was already done.
I have an account but do I invoke a docker VM or a wordpress from azure ??
What about the database?
The easiest path is for you to create a new Azure Container Service, which can host Docker Swarm, and deploy it there. Install the Azure CLI 2.0 on your machine and follow the tutorial to get started.
Related
I have started learning/trying Airflow. Part of my research, I have installed airflow in my local through Docker. I referred official page Airflow Install Docker
I am looking for a (standard) process when I can deploy Airflow to Azure.
Can I directly use same docker-compose file for that ?
Any help will be appreciated.
Likely the easiest way is to use AKS (Azure Kubernetes Service) and use the official Helm Chart of Apache Airflow from the Apache Airflow community to deploy Airflow on it:
https://airflow.apache.org/docs/helm-chart/stable/index.html
I reckon, Installing Airflow through Docker-compose.yml on Azure wouldn't be the right approach. It is probably encouraged for local installations only.
The way we have set this up in Azure is like this:
Database: Azure Database for PostgreSQL server
Webserver + Scheduler: Azure App Service on a Linux App Service Plan
Docker: Azure Container Registry
Build the Docker image (either locally or in CICD pipeline)
Push the Docker image to Azure Container Registry
Setup Postgres server and create airflow database
Setup Azure App Service to pull Docker image from ACR (You can also setup continuous integration). Remember to configure Environment variables.
Obviously, as Jarek mentioned, you could also go with setting up AKS.
You can try the preconfigured images of Kubernertes AirFlow2 packaged by Bitnami. And perform the Deploy in AKS
bitnami.airflow
I am using gitlab ci/cd to deploy my app to google app engine. I already have php instance working properly but when i try build wordpress image using docker-compose, nothing happen.
these are my files:
I have a folder "web" with a files ping.php: https://site-dot-standalone-applications.appspot.com/ping.php
So application is running into /web folder.
wordpress should be deployed into /web folder after:
docker-compose up
UPDATE
Just needed use the following gitlab-ci.yaml:
Unfortunately, you cannot (easily) deploy containers to App Engine Flex this way.
At its simplest, App Engine Flex is a service that combines a load-balancer, an auto-scaler and your docker image. Your image when run as a container is expected to provide an HTTP/S endpoint on port 8080.
There are 2 ways that App Engine could support your deployment but it does neither:
It bundles a WordPress app image and a MySQL image into a single "pod" and exposes WordPress' HTTP port on :8080. This isn't what you want because then each WordPress instance has its own MySQL instance.
It separates the WordPress app into one service and the MySQL app into another service. This is closer to what you want as you could then scale the WordPress instances independently of the MySQL instances. However, databases are the definitive stateful app and you don't want to run these as App Engine services.
The second case suggests some alternative approaches for you to consider:
Deploy your WordPress app to App Engine but use Google Cloud SQL service link.
If you don't want to use Cloud SQL, you could run your MySQL database on Compute Engine link.
You may wish to consider Kubernetes Engine. This would permit both the approaches outlined above and there are tools that help you migrate from docker-compose files to Kubernetes configurations link.
Since you're familiar with App Engine, I recommend you consider using option #1 above (Cloud SQL)
I currently running WordPress installed on a VM's hosted by Azure and looking into migrating from using Virtual servers to hosting a WebApp for our WordPress site rather than having to upgrade the everything on the server when its build gets obsolete.
I am aware of the Azure Marketplace Wordpress Application option, but I was wondering if AWS had something similar or what its closest equivalency would be rather than just creating an EC2 VM.
If you want to run Wordpress on AWS, it means running it on an EC2 instance, which is pretty much the same as you are already doing on a Azure VM.
WordPress is now on Azure Market place and you don't need a VM to host your WordPress.
It will just create a Web Site in Azure and installs WordPress there, then you can make your changes to the WordPress instance if you wish:
use this link to get started:
https://azure.microsoft.com/en-us/marketplace/partners/wordpress/wordpress/
This way you don't need to worry about the VM management and you just use a hosting service and have the benefits of Cloud like Scaling out/up etc.
I'm currently hosting the wordpress using the Azure IIS mysql for my blog and would like to move to the Amazon web services (AWS) windows instance.
Does anyone know how to migrate properly I have read plenty of sites but it seems to be more focused on linux
Regards,
Your Mysql is a cleardb instance. You must connect to it using MySQL Workbench and export data.
You can do the same with wordpress through wp-admin
I have a web application deployed on heroku. I just introduced Neo4j as data structure and, of course, I have to integrate it in production on heroku. I read on this link http://wiki.neo4j.org/content/Neo4j_Heroku_Addon that the heroku addon for neo4j is currently on beta testing. So have looked for alternative ways and I found this link: http://wiki.neo4j.org/content/Neo4j_in_the_Cloud ... do you know if it's possible to include such integration on heroku without the addon ?Tnx
If you are a registered beta tester on heroku you can already use the add-on for free.
Of course if you want to run the Neo4j REST server on your own aws ec2 instances you can do that easily (there are also preconfigured AMI's). Please make sure that your ec2 instances run in the aws us-east region as this is where heroku's machines are located too.