I've followed some tutorials about cakePHP and now it's done, the "mvc" is ready.
What should I do next?
Meaning: I was working locally, can I simply upload the complete app online and it is secured as 'they' meant it to be?
I've downloaded the 1.3.6 package from https://github.com/cakephp/cakephp/archives/1.3, and deployed it as is in a folder named as my domain.
Edit:
I have win-xp with wamp.
I created the app by simply unzipping the file to a folder and then renamed it to 'domain_name'.
Then I made the db connection and set the configuration files.
At that point I created the models, views and controllers.
Now the application is working, locally.
My question is: can I simply upload everything to my server, to the html root folder and say that "I am done"?
As long as your app isn't already in production, putting it online can tell you more about how it's working. For instance, you'll learn if there are missing modules or dependencies that must be installed on the live server.
If it's an already live system, you may want to use an online staging server to understand what needs to be modified on the production server in order to have a smooth deployment.
There are three ways that you can deploy your cake app (Development, Production and Advanced), and all of them are secure:
http://book.cakephp.org/view/912/Installation
I would recommended the Production install if you aren't going to run any other apps on this server.
Related
I'm trying to publish a NextJS website on IIS, I've already installed URL Rewrite and IIS Node on the server, I tried following this guide to set up a reverse proxy, but that didn't seem to work, as even though I was running the project on the server, it wasn't redirecting to it.
I then tried hosting with a custom server, this works when running locally, but when run next build, copy the generated .next folder, package.json, web.config, and server.js onto the server where IIS is being hosted, running node server.js doesn't seem to work, as it simply stops after:
info - SWC minify release candidate enabled. https://nextjs.link/swcmin
No other question or blog I see seems to cover hosting on a different computer than the one used to develop, so I'm not clear on whether or not I'm simply supposed to copy the entire source code to the production server, and run next start there, that would not seem ideal.
I'm trying to run the simplest node/express app which has a single get request that sends hello world as response. Works on local.
I followed this tutorial for deploying it on A2 hosting shared plan, but I'm getting default a2 hosting page and not my app.
Tutorial followed: https://medium.com/#pampas93/host-your-node-js-app-on-shared-hosting-go-beyond-localhost-73ab923e6691
I tried contacting support. They responded:
App is on a different location and website is looking at different location.
To make it use the path that you need may require custom coding or alterations to the .htaccess file to change the document root for the primary domain.
I'm not able to understand what changes to make/how to fix this. Any help would be appreciated.
The .htaccess file in my cpanel is empty right now. No code is written inside it.
I know this is a long shot but I'm going to ask anyway.
I have a project I'm working on for a company that hosts their application from a server running Microsoft Server 2012. I've found the folder where the web app's files are stored and I want to deploy my own version with updated code - would I just replace those files and restart the server to deploy? (after backing that folder up, of course)
This is super out of my wheelhouse as I've only used Github, Heroku, etc for deploying applications. Please let me know if I need to provide any more information to help you help me.
Thanks in advance!
you host multiple websites on the same server. Use IIS to point to another website and start it on a different port number for your web app. Let me know if this isn't clear enough
If you only update HTML, CSS, JS these files, it will be updated after you restart the iis server, but if you change the cs file code you need to rebuild the project and republish it or just copy the bin folder.
I've just finished developing my Node app that uses node-watch to actively monitor a specific folder on my intranet network and parse CSV data into a database table as soon as someone drops a CSV file in the monitored folder.
I could test it successfully in my machine (I didn't need to install this package globally) and it's working just fine. Now is time to deploy it to the production server on the Intranet and due to information protection standards, this server has no access to the internet.
I've copied my entire app folder including node_modules to the server. The application successfully started and is running but nothing happens (neither errors) when I drop files into the monitored folder. Maybe node-watch is not a pure JS module but I can't run NPM Install on this server as it has no access to internet.
Any Ideas?
Could not find an easy solution to overcome this problem. It was easier working with the server team to open internet access to the service account that is running the node process. Once we do that I executed NPM INSTALL and re-installed all dependencies on the server. It's working now.
We have a Node.js application with a pretty big codebase that we're trying to deploy to an Azure Web Site. My problem is that when I deploy the app and try to access it, I just get a message saying "The page cannot be displayed because an internal server error has occurred".
According to http://azure.microsoft.com/en-us/documentation/articles/web-sites-nodejs-debug/ I should be able to configure some settings and have my standard out be logged to a file - well, it's not working. in /LogFiles I can see /git, /html, and /DetailedErrors, but none of these folders contain the stdout logs.
I have deployed the app using Visual Studio. I created a blank Azure project, and manually added all the folders and files I need. I also created an iisnode.yml file that contains the following config:
loggingEnabled: true
devErrorsEnabled: true
logDirectory: ./logs
debugHeaderEnabled: true
The last two lines I added later, the first ones are from the tutorial. I also have a web.config file, the contents of which I haven't really touched.
I've attempted to configure the settings that are available in the Web Sites UI, but I haven't really been able to make any headway. I think currently they are pretty much default.
I'm sorry that I can't provide you with more information. I'm really kind of banging my head against the wall here, since all the tutorials I've found basically state that if I do this and that, everything should work. The problem is, it doesn't. Sad face.
Edit: I should probably add that my server.js is in a folder called /NodeServer. It's not in the root as Azure seems to presume.
Edit2: I deployed a Hello World example and got it to work, but when I try to move the server.js file from the root I can't get it to work anymore.
I've added a tag to the web.config, so that the structure is basically
configuration
location path="NodeServer"
system.webServer
I've also edited my package.json so that it says
"main":"NodeServer/server.js",
"scripts":{
"start":"cd NodeServer && node server.js"
}
If the app is started successfully, you should be able to find the stdout at
D:\home\LogFiles\Application
in Azure Websites, without configuring anything.
But here it looks like an error related to incorrect/missing web.config. The node app may not get launched. You can try:
Publishing your app using git to Azure Websites.
Or if you are familiar with IIS and iisnode, make sure your app works locally with IIS and iisnode. See http://tomasz.janczuk.org/2011/08/hosting-nodejs-applications-in-iis-on.html
Or try publishing an "hello world" node.js app to Azure Websites, take the generated web.config and modify it for your app.
Edit: When you change the location of server.js, you have to change web.config too. The change in web.config is not correct. And package.json is only used as hints to generate web.config during git deployment. To get your "hello world" to work, you can either
In your web.config, replace all "server.js" with "NodeServer/server.js".
Or deploy the modified app using git. Make sure it does not contain the wrong web.config.
Then you can try to get your larger app to work.