How I can set for example Path to urlGenerator.php if I using deployment connection to my project, and this file is generated on virtual machine. I don't want to synchronize that files to my local computer...
The connection to deployment is through sftp.
Symfony plugin configuration:
Deployment configuration:
I have added a remote action button and also multiple routing files in a new menu entry. you can now add remote files. just update to 0.11.111
https://github.com/Haehnchen/idea-php-symfony2-plugin/issues/685
Related
I have an O-jet application and need to deploy it to Nginx.
I have installed Nginx in windows and have it working successfully.
From my understanding, I just need to modify the nginx.conf file and re-load the config file, the application will be available in the specified url.
How to change the nginx.conf since I want to deploy it to specified http://host:port?
Simply copy your OJET project into nginx's web root.
OJET is a JS toolkit, not a web application, so usually, your project files are static content.
We are using DropWizard to create java applications running as a server inside a docker container.
Command to create such applications is as below -
java -jar service-name.jar server service-name.yml
service-name.yml is a file that holds all configuration settings.
Can you suggest how do we configure application insights inside this yml file?
I don't know how DropWizard configuration reading works. But if there are hooks in the code to read the configuration, you can read all the configuration required for ApplicationInsights and manually configure in your code using TelemetryInitializers.
I already created a website "MyWebsite" on IIS on Windows server 2012, the physical path is C:\builds\MyWebsite\wwwroot, there are 1 other folders approot under directory C:\builds\MyWebsite, which is also necessary to make the website run. What I want to do is:
create a new folder C:\builds\MyWebsiteNewBuild in remote server which will be used to put my new build;
dump my new build D:\Release\PublishOutput from my local machine to the remote server, the publish output has 2 sub folders: wwwroot and approot;
change the physical path of "MyWebsite" to the new created folder C:\builds\MyWebsiteNewBuild\wwwroot, and restart the service.
I am new to the msdeploy, I searched and it seems that I can use
msdeploy.exe -verb:dump-source:contentPath="D:\Release\PublishOutput" -dest:contentPath="C:\builds\MyWebsiteNewBuild",computerName="https://**.**.**.**/MsDeploy.axd",userName='administrator',password="*****",authType='Basic' -allowUntrusted
to dump my new build to remote server's destination folder, but the other requirements, such as change the physical path of my existing website, I don't know how to do.
You could change the website path using the appcmd through WebDeploy by using a manifest.
<runcommand path="%windir%\system32\inetsrv\appcmd set app /app.name:"Default Web Site/app12" /[path='/'].physicalPath:C:\temp\app12" waitInterval="5000"/>
http://www.dotnetcatch.com/2016/06/28/webdeploymsdeploy-quick-tip-change-iis-siteapp-physical-path-with-msdeploy/
The following post describes how to create a custom WebDeploy package based on a manifest:
http://www.dotnetcatch.com/2016/06/23/deploy-an-asp-net-website-not-web-application-with-msdeploy/
How to configure WildFly 8.2.1 to:
Not auto-deploy from "deployments" folder when server running
Always deploy from "deployments" whent starting up, ignoring previous deploy result
If I set scan-enabled="false" for deployment-scanner, WildFly didnt deploy at startup even new files.
When scan-enabled="true", WildFly didn't deploy files that failed to deploy at previous start up, but not changed.
To avoid auto deploy set auto-deploy-zipped="false" auto-deploy-exploded="false" for deployment-scanner in standalone.xml.
But whenever you want to deploy another file then you have to add MARKER FILES for it.
For example, the marker file to indicate the HelloWorld.war file should be deployed named HelloWorld.war.dodeploy in deployments folder and file should have content - HelloWorld.war.
Then only it will deploy your new file automatically.
Refer this and this link for some more info.
If scan-enabled="false" then WildFly will ignore marker files at startup and at runtime. Alsow WildFly will ignore all deployments in deploy folder, even if that deployments was successfully deployed before.
Left only 2 ways:
Set scan-interval less than 1 (with scan-enabled="true"). It will
enable only one scan at startup. After that WildFly also will ignore
any changes in deploy folder
Deploy through admin console
Currently, I am deploying both "share.war" and "alfresco.war" on same tomcat server.
So, how can I separately deploy "share.war" and "alfresco.war" on different tomcat servers?
I want to deploy "share.war" on tomcat server 1, deploy "alfresco.war" on tomcat server 2.
If you're looking for a way to embed Alfresco in your application, you should check this old but still mostly valid webinar.
If you want to have a quick start at running Alfresco outside any application container (i.e. directly bootstrapping the Spring context) the FirstFoundationClient sample in the Alfresco SDK is what you need.
This is really much more simple than it seems. Deploy the wars on separate tomcats, and then configure share-config-custom.xml inside /shared/alfresco/web-extension on the Share deployment to point to the Alfresco repository. It's that easy.
From a copy-paste of the official documentation :
You can run the Share application in a separate Tomcat instance from
the instance running the Alfresco WAR. This additional instance can be
installed on the same server as the original Tomcat instance, or it
can be installed on a separate server.
Install a new Tomcat instance on the same server at the original Tomcat instance.
Modify the /conf/server.xml file for the new Tomcat instance:
Change the port number (for example, to 8006) in this line:
<Server port="8005" shutdown="SHUTDOWN">
Change the port number (for example, to 8180) in this line:
<!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
<Connector port="8080" ....
Move the share.war file from the original Tomcat /webapps directory to the new Tomcat /webapps directory.
(Optional) Configure the original Alfresco Tomcat deployment.
Start the original Tomcat.
You can use Alfresco supplied batch files.
If you are running the Share Tomcat instance on a separate machine, you must modify the override file in the Share Tomcat web-extension directory:
Open the share-config-custom.xml file.
Change any instance of the server and port to the correct name or IP address of the Alfresco server.
http://yourserver:8080
Save the file.
Start the new Share Tomcat instance.