I'm thinking of hosting WordPress on my Dropbox folder for development work. Has anyone tried this?
I'm wondering if there's a way to keep XAMPP on your local machine but direct the root to the Dropbox folder.
First of all, both WordPress and XAMPP produces a lot of garbage files (logs, PIDs, configs, sessions) etc. that will simply trashout your Dropbox. I'm pretty sure about that, because I tried to version XAMPP on SVN, which is pretty the same as SVN, and got really tired on searching more and more folders that should be ignored (non-versioned) because of containing data and other temp files.
And for answering your question. Sure thing, you can. After installing XAMPP (preferably outside Dropbox), go to "xampp\apache\conf" folder, edit "httpd.conf" file and change the value "DocumentRoot" variable (around line 90) to whatever you need. You may need to use ".." for specifying parent folder many times, if your Dropbox is outside XAMPP folder.
I won't discuss security matters here, as you should know, that such solution is highly risky and on the other side of security topics.
Related
I used to use Dreamweaver. I've a huge Classic ASP website. I edit the files on my local system, and when done, I can upload the file(s) via ftp to the remote webserver. Now, I try to switch to VSCode. I've installed ftp-simple, ftp-sync and deploy. But can't find the set-up to get a Dreamweaver like behaviour. Eg, I have to locate for each file I want to upload/deploy, the exact location in the remote file tree.
I really feel like deploy deserves more attention. I spent the past 4 days or so to find an extension that does just that. Auto-upload to an ftp-folder from a local folder. I wanted to make git work for my website, but couldn't get that to work on the server with ftp-simple or ftp-sync because those extensions only download the opened files or open in a different temporary folder each time. I set up deploy now and got exactly what I wanted thanks to your tiny comment, thank you!
(I'm sorry if this post is too old to comment on, but I browsed Stack overflow for days to find this, so I thought it might help others in the future to point this out.)
it sounds like your just missing your mapping configuration. Most text editor FTP packages include a configuration file where you specify the server, your credentials, and the root folder of your ftp server. Have you specified this?
I've got an issue where if I upgrade MAMP, it generates a new folder in my Applications folder. So far this has occurred three times now and I'm no closer to finding out why it's happening.
Here's a screenshot of the Finder window showing all MAMP folders. The ones that got created after updating MAMP all have the dates and times they were created.
I've tried deleting the new folders and leaving the original one but that prevents MAMP from opening ("These files are in the trash") but the path for the document root still points to the original folder. Here's a screenshot of that:
Can anyone advise on how best to remove these duplicates and prevent this from happening again? Each duplicated folder adds at least 10GB to my storage and I'm running low! I can't find any reference to this in MAMP's documentation, or even on this site.
Any ideas?
Thanks!
As Peter pointed out that is normal behaviour. The folders containing dates (MAMP_2018-0....) are the backups of the previous installations/versions. The following named folders always contain the latest updated installation files:
MAMP
MAMP Pro
It is advisable NOT to store development sites in the MAMP/htdocs directory. It is advisable to set the Document Root to a separate development directory (not within the MAMP program folder) e.g. DevServer under My Docs.
Before MAMP/MAMP Pro is upgraded record the preference settings. Next upgrade the software and recheck the settings match after the upgrade. Then launch and check your development website(s).
I've experienced this when upgrading in the past. I believe this is normal behaviour.
I have just gotten into the habit of deleting the old ones and haven't had any problems.
So I have been given the task of upgrading one of our companies' old websites that is based on 1.5 to something newer (because a second site of ours on the same version just got hacked).
I know some php and some other web stuff, but I'd never used Joomla.
I have setup a lamp server on a local VM (ubuntu) for me to test it all out on, then upload the upgraded version as is suggested. My problem now is that I know the permissions are not correct because when I tried installing Akeeba Backup, it kept throwing errors such as "could not copy to /var/www/components and /var/www/administrator etc. I went in and chmod'd those 2 (and then the rest of www because of more errors) to 757 (from 755 for the most part) - which i know at that point might as well be 777. Then when I've tried to use Kickstart to restore from the JPA file I have, it just right away throws an error "could not create j_backup/ folder".
I know this slackening of all permissions on the root folder is wrong, but it was the only way to get it to 'work', which it's not even now, so my question is what did I do wrong in the setup and how do i fix it? I'm not great with Linux, but I'm thinking I have to make PHP owner of www? is that right? or terrible practice?
The other issue I see now is that I just installed the latest php and everything and I see Akeepa says not to use php 5.4... not sure how much of a problem that's going to be....
Some direction would be great because I'm more than a little lost.
Thanks!
This is certainly a headache. Most often, as you stated, the issue is the ownership of the files on your server. Files uploaded via FTP will be owned by your FTP user and may not be editable by the Apache/PHP user. Similarly, files created by installing extensions in Joomla! will be owned by the Apache/PHP user and your FTP user will not be able to modify them. Here is an article discussing the problem with a couple of possible solutions:
http://docs.joomla.org/Why_can%27t_you_install_any_extensions%3F#File_ownership_advice_from_ianmac
In the past, I have used an Apache Module called suPHP (http://www.suphp.org/Home.html) to solve this problem and keep it from reoccurring. suPHP executes PHP scripts with the permissions of their owners.
As for file permissions other than ownership, please refer to the Joomla! documentation for the correct settings: http://docs.joomla.org/Verifying_permissions. One quick way to handle this (if you can install extensions after correcting the ownership issue) is to use the AdminTools extension (http://extensions.joomla.org/extensions/access-a-security/site-security/site-protection/14087). One of its tools ‘fixes’ the file permissions on your server by resetting them to the Joomla! default.
Good luck!
Say i have a Magento installation which i've configured and developed on a WAMP server (perhaps also adding products, etc.), what is the correct way to migrate this to an online domain.
I had pretty good luck with this approach when I did it. The WAMP install was on my own box so I didn't use SSH on that side.
http://www.magentocommerce.com/wiki/groups/227/moving_magento_to_another_server
I did have a couple errors related to the new domain that their help desk were able to resolve by modifying a couple entries in my .htaccess file. But other than that it was pretty seemless.
I've also done a full backup/restore by simply copying the entire contents from one box to the other. Copying up the MySQL DB, and then I reran the install procedure by simply deleting the app/etc/local.xml file (which forces Magento to run re-install scripts).
The script asks you for the location of the DB, passwords, etc... all the data, products, order history etc, survives a reinstall.
Oh, and make sure to clear your cache/cache folders before you move everything. That saves a lot of head-aches later and reduces the size of files you have to copy.
For reasons that we won't discuss, I have determined that MAMP is a pile of crap that haunts my system, and unless I remove it fully, I will live in shame.
I've done the obvious thing and removed the MAMP directory from my Applications folder, however, I don't like wandering files, and I have an itching feeling that MAMP put some .sock files somewhere, or otherwise made a mess in my file system.
What files does MAMP add to a system when it's installed, and where are they?
If you have proof that MAMP doesn't actually put files anywhere (besides the /MAMP dir), then that's as good an answer as any!
From their help page:
To "uninstall" MAMP, you only have to
delete the MAMP directory and
everything returns to the original
state (MAMP does not alter anything on
the "normal" OS X).
When you download MAMP, you get a MAMP Pro trial, also. In the MAMP Pro folder, there is an 'uninstaller'. When you open the uninstaller, it asks you if you would like to remove all traces (preferences, etc.)
When I used it, it appeared to delete absolutely everything for MAMP and MAMP Pro.
MAMP does alter one system file: /etc/hosts (it adds any virtual hosts you may have created under the "hosts" tab here).
You may want to delete those entries.
To do so, go to Finder, select "Go"-"Folder" from the menu, and enter "/etc". Then you need to temporarily change permissions on both the host file and the directory it's in, by right clicking and chosing "Get info" and changing the permissions.
You can then edit the hosts file in Textedit.
After you're done, you should put the permissions back to what they were to be on the safe side.
AppZapper is a great tool that solves this problem. Search Google for it, it's free for the first 5 time you use it.
To fully uninstall any application. Try installing AppTrap. + it's free
Each time you move an application to Trash, AppTrap would find the preference files in your library and let you delete them as well.