I have output folder structure as:
assets
- images
views
- index.html
Assets and Views are siblings and entry point of web-server (browser sync) is views folder, so if it's root, it can't see level up folders, how to resolve it? (Config or folder structure?)
Start your web server or gulp task one parent directory above where you are currently starting it. A web server cannot go above its current directory other wise it would have access to your full system
Related
Am following:
https://www.jetbrains.com/help/phpstorm/2016.3/comparing-deployed-files-and-folders-with-their-local-versions.html
I have my server setup in the remote host, and can see my directory, folders and files.
I would like to compare a whole folder on my local machine with what is on the server.
It works for individual files, but my developer has changed a whole load of files in the directory.
Please see screenshots.
I try and compare a directory from Remote host to the local server (see screenshot)
Says I failed to download the content of the file (...name of folder) - see screenshot
I try and compare one file (screenshot)
Works fine
How do I compare an entire folder, and see what has been changed?
As per official documentation from the link you have provided:
https://www.jetbrains.com/help/phpstorm/2016.3/comparing-deployed-files-and-folders-with-their-local-versions.html#d30440e104
Comparing a remote folder with its local version
Open the Remote Host tool window.
Select the folder in question. Then choose Tools | Deployment | Sync with Local on the main menu or Sync with local on the context menu of the selection.
In the Differences Viewer for Folders that opens, explore the differences and synchronize the files, where applicable.
The same but when invoked from Project View panel:
https://www.jetbrains.com/help/phpstorm/2016.3/comparing-deployed-files-and-folders-with-their-local-versions.html#d30440e154
Comparing a local folder with its remote version
This action is available only if you have a default server access configuration appointed.
Select the folder in question in the Project tool window, and then choose Tools | Deployment | Sync with Deployed to on the main menu.
In the Differences Viewer for Folders that opens, explore the differences and synchronize the files, where applicable.
In that Differences Viewer for Folders screen you can:
See a list of files with differences (or that do not exist of one of the sides) -- top part;
Choose any file and see the actual difference/compare them -- bottom part;
Also choose to upload/download such file(s) or merge them manually.
(screenshot from JetBrains website)
css is not working after uploading the file on server with filezilla i added file permission 755 on server and even after that it's not working.
I have changed /web/assets/d01711d6/css/bootstrap.css.
css is not working after uploading the file on server with filezilla i added file permission 755 on server after that it's not working.
This may depend on several factors.
Cache
If the application is hosted it may be that it is a problem of the server cache so the new CSS file is read to the cache expiration (sometimes several days). In some cases the provider it provides configurations for enabling a temporary mode that disables this mode and promptly update the files.
Asset Management
Another factor is related to the fact that the directory where content assets are dynamically generated so not always the name of the directory in the development environment and the production server match. It is in these cases to find (looking for it) the actual directory used by the server and replace the file in the right place.
If, as the practice, changes to css file was made in the original directory and not on the copy of the file created by dynamically from asset management, one usually proceeds by eliminating the directory containing the assets of interest and the first subsequent invocation of the application (the URL / link) a new directory of assets is created for these files
I'm starting a new web app with Openshift (jboss, mysql). It's the first time I use openshift and after reading through some doc and experimenting a bit with it, I'm having one question regarding best practices for the architecture of my app.
There will be some files generated by- or uploaded to the application (resources). I'd like those files to be outside the deployment folder so they are not erased/overwritten when the app deploys again. I have browsed through the directories and I was wondering:
is it ok to use the /var/lib/openshift/[openshift-id]/app-root/data folder for these files?
Yes, you should use your ~/app-root/data folder for any files that you want to not be erased when you do a git push, there is also an environment variable that you can use that points to that folder called OPENSHIFT_DATA_DIR. Please note that if you are using a scaled application, that folder is not shared among your gears.
I have some PHP and HTML pages that need to access some files (images files for example) and display them.
Where should I put these files? As I know that it is not recommended (for security reasons) to let the web pages access files in the file system of the server (like in the home directory for example).
I need to put the files (the images) in a folder where I have the rights to create new files.
You need to put files in virtual directory of your server, for example if you are using XAMPP then put your files in "htdocs" folder. if you are using WAMP then put your files in "www".
Add a directory inside of your www folder and put your web pages there.
Then you can access the pages as
localhost/foldername/page
I have this structure for my project:
Root Directory
|-css folder
|-style.css
|
|-it folder
|-index.html
If I try to include css file with:
<link href="/css/style.css" rel="stylesheet" type="text/css"/>
from index.html, aptana preview and also internal server can not find style.css.
Why is this?
In my remote server it works perfectly and I do not want to use a relative path.
In terms of the "why", the problem you are having is related to how your development server is setup versus your production server.
Assuming a standard setup, your production server will receive requests for a domain (i.e., http://mysite.com) that is, for lack of a better word, mapped to a folder on your server (i.e, a request to http://mysite.com will be mapped to a folder, /var/www/mysite, on your server).
So, when you link to a style sheet with /css/style.css, your (production) sever immediately goes to the /var/www/mysite folder and starts looking for the css folder, file and so on. No problems with that, as you point out.
Your development machine, however, is serving up pages locally and has a different directory structure for mapping to files and folders.
When I open an HTML page in my Aptana project and hit the preview button, Studio loads http://127.0.0.1:8020/mysite/public/404.html (note how the first folder after the IP and port is mysite). To load the absolutely pathed CSS file, the local server is actually looking for http://127.0.0.1:8020/css/styles.css but it needs to get to http://127.0.0.1:8020/mysite/css/styles.css.
The initial "/" in your link (/css/styles.css) tells the server to go to the root directory of the server and start looking for the folder and files from that point ... but there is no css folder in the local server's root directory. It lives in /mysite/css/styles.css and that's why fskreuz suggests relative paths and using "../css/styles.css" instead.
Personally, I prefer absolute links (but that's just a personal preference and not in any way a challenge to or comment upon fskreuz's response). However, my local development setup is conducive to using them because I setup virtual hosts for the sites I work on. Using Apache, I setup a virtual host for each of my projects. With this, I can load something like http://dev.mysite.com in any browser on my computer and test my site/app in a way that makes it mirror my production setup.