I am currently hosting a website using an azure app service (wordpress) and I want to setup a pipeline that basically pushes a build artifact from my github repo to the themes directory and syncs it with the current one. Is this even possible? Any point in the right direction is massively helpful. Thank you.
Related
I am writing a small thesis about a project where we used JHipster. I am currently trying to explain how the deployment with JHipster works. I already found some great info how the Backend is deployed with Spring Boot as a JAR file.(The JHipster Mini-Book, page 135) But I am not able to find any mentions on how the Frontend is served inside this JAR file, shouldn't there be some embedded Web Server or something similar? Where can I find this info? Thanks for any help in advance.
I have already looked in books like The JHipster Mini-Book and Full Stack Development with JHipster, but they only mention how to deploy, not how the deployment works.
I installed Wordpress for Linux as an Azure WebApp. I set it up and installed a few plugins only to find out later that they were gone. A little investigation revealed that the storage in the container doesn't persist across container restart and hence why my plugins were not persisted. I then enabled WEBSITES_ENABLE_APP_SERVICE_STORAGE, but now my site shows up with the empty Web App Template:
Your App Service app is up and running
It looks like turning the App Service Storage maps the Web Server to Azure Storage and my container is now "useless". How do I retain files and have Wordpress running at the same time? I would imagine that Wordpress is a little useless without being able to persist storage...
I think this one is out of date.if you are using Wordpress for Linux as an Azure WebApp, Below readme.md maybe help.
https://github.com/Azure/app-service-quickstart-docker-images/tree/master/wordpress-alpine-php/0.4
I am looking to stand-up a development/test WordPress website in Azure alongside our production site and am looking for any best practices I can find.
The idea is to keep the environments the same having both sites on the Azure PaaS but having different URL's to be able to access them. And having the databases be separate (to ensure we don't mess up anything in production)
Example...
Production -- http://companywebsite.com
Development -- http://test.companywebsite.com
Has anyone attempted something like this before? It would be fairly simple if the development was being done locally but we need multiple (non-developer) users to be able to access the WordPress admin panel on the test site and be able to install plugins and such to test.
Thanks in advance!
have you tried deployment slot?
When you deploy your web app to App Service, you can deploy to a
separate deployment slot instead of the default production slot when
running in the Standard or Premium App Service plan mode.
https://azure.microsoft.com/en-us/documentation/articles/web-sites-staged-publishing/
Update:
Seems like you can also config wordpress to aware of staging environment.
http://www.wpbeginner.com/wp-tutorials/how-to-create-staging-environment-for-a-wordpress-site/
I need to set up continuous deployment of a WordPress theme that is source controlled on bit-bucket.
An external agency is managing the theme development.
The WordPress install is hosted on the Windows Azure platform.
I can set up continuous deployment from a number of git services, including bit-bucket, but Azure wants to set the deployment from site root, where I need to the deployment on at the themes folder level.
How do I achieve this?
Thanks
It turns out all that is required is a .deployment file in the root of the repository
[config]
DEPLOYMENT_TARGET = D:\home\site\wwwroot\path\to\theme
We are small wordpress focused web development company planning to migrate to OpenShift by RedHat.
My goal is to have production environments (apps) in the cloud and most of the development is done in local laptops using OpenShift origin and then deployed as staging apps to private OpenShift installation and when approved back to cloud replacing original app. It would be extra if all team could be able to edit app simultaneously in the dev version of the app (in the cloud).
The problem I noticed is that web development often requires many edits when tweaking CSS and such and commits to OpenShift takes more than 10 seconds.
Hot deploy (https://www.openshift.com/kb/kb-e1057-how-can-i-deploy-my-application-without-having-to-restart-it) speeds up process a bit, but not enough.
Another option is to SCP/SFTP to local OpenShift installation and edit files bypassing git and build process. That causes git to be off sync, but it can be fixed (http://druss.pp.ua/2013/11/synchronize-openshift-application-after-update/)
How ever, process isn't that smooth as i hoped it to be. Any improvement ideas?
I prefer to keep my plugins & themes in git. That allows me to run a copy of my wordpress site locally for development, then add my changes into git, do a git push, and have the production site updated. This would require a minimal change to your files you have now if you used the OpenShift quickstart. I can provide details if needed.