Currently, for linux operating systems, the cache and index folders for clion are defaulted to /home/.Clion12/. I am on an NFS and want the cache directory and indexing directories to point to my internal ssd. Where can I change this?
I just found the answer to this. In the bin directory where clion.sh is kept, there is an ideas.properties file. You can change the default location there.
As #StevenCombs said, the file idea.properties is in the same bin directory where clion.sh is found, and the variable is idea.system.path.
I set it up like this. First, on the command line I did:
sudo mkdir -p /var/cache/mlakata
sudo chown mlakata /var/cache/mlakata
And then in the ${clioninstall}/bin/idea.properties file, I added
idea.system.path=/var/cache/mlakata/CLion/system
CLion appears to populate the CLion/system directories under my personal cache directory.
The problem was solved for me after I have created an idea.properties file in ~/.Clion2019.2/config then populated it with:
# custom CLion properties
idea.config.path=/someFolder/my_work/clion_ws/.Clion2019.2/caches/trunk-config
idea.system.path=/someFolder/my_work/clion_ws/.Clion2019.2/caches/trunk-system
idea.plugins.path=/someFolder/my_work/clion_ws/.Clion2019.2/caches/trunk-plugins
After this, the cache is build in /someFolder, not flooding my home folder anymore.
Official support page for path parameters
Related
I'm trying to insert the mercurial_keyring file with my username and password in the .hgrc file but it doesn't exist in my user directory on windows. I have tortoise hg installed and even checked if it was installed properly on the command prompt yet I still don't have the .hgrc folder.
Can anyone tell me what might be the reason to it?
Thanks
Because it's %USERPROFILE%\mercurial.ini
Mercurial reads configuration data from several files, if they exist.
These files do not exist by default and you will have to create the
appropriate configuration files yourself:
Local configuration is put into the per-repository /.hg/hgrc
file.
Global configuration like the username setting is typically put into:
%USERPROFILE%\mercurial.ini (on Windows)
The .hgrc files are not created automatically when you install Mercurial or TortoiseHg.
You will need to manually create it at the location you need whether that is within the repository's .hg folder or your own C:\Users\username\ folder.
You will probably need to use the command line to create the file as it's not usually possible to create filenames that start with . in Windows Explorer.
https://www.selenic.com/mercurial/hgrc.5.html
My question is why is there a homestead.yaml file in .homestead folder and in the Homestead/src/stubs folder?
On my internship machine (Mac), I have been making changes to the Homestead/src/stub yaml file. On my home machine (Linux), it doesn't read those changes and I have to edit the .homestead yaml file instead.
The homestead.yml file in ./Homestead/src/stubs is there only as a placeholder before its copied to your home directory during installation. It should not be edited.
Only edit the file in ~/.homestead.
Make sure your ran the bash init.sh script on your Mac from the ./Homestead directory.
http://laravel.com/docs/5.1/homestead#first-steps
Though the Question has been answered but as it appeared while I was searching for homestead.YAML, It would be good to tell newbies that Homestead.YAML holds the whole configurations on windows and macs. It allows you to add sites, manage shared folders and much more. I will recommend this definitive guide for understanding homestead.yaml, The whole post is very long so I can't copy it
https://abbasharoon.me/homestead-yaml-explained-a-z/
Setting up Vagrant for the first time and I'm using the VAGRANT_HOME environment variable to change the location of the ~/.vagrant.d folder to an external drive (I'm paranoid about SSD wear and tear, sue me). This is causing an issue with the vagrant ssh command as it's complaining about not having the right permissions and I can't use chmod to change the permissions for the file it wants on an exFAT volume.
Is there a workaround? I've checked the documentation and there doesn't seem to be a setting where I can specify a different location for the insecure key, but I might be missing something.
Thanks!
The solution is to move the insecure_private_key file located in the external vagrant.d folder to somewhere in your local home directory and then symlink it back.
I am trying to install a package from URL into my local server and I am getting this error:
Error
Archive does not exist
Warning
JFolder: :files: Path is not a folder. Path: C:\xampp\htdocs\Joomla\tmp\install_53170ad5161e0
JFolder: :folder: Path is not a folder. Path: C:\xampp\htdocs\Joomla\tmp\install_53170ad5161e0
JFolder: :files: Path is not a folder. Path: C:\xampp\htdocs\Joomla\tmp\install_53170ad5161e0
JInstaller: :Install: Cannot find Joomla XML setup file
The tmp paths are correct and the remote file URL link is correct too. I've also tried by clearing the tmp folder but still does not help. The package installs correctly when the package file is uploaded.
Does anyone know what's happening?
If you are using Linux
You may need to fix the directory permissions. Check if there is any directory of which CHMOD is not 0777. If there are folders which their CHMOD value is lower than 0777 set them to 0777. After installation you have to change chmod back to 0755
Even though this post is quite old I hope that someone searching for a solution will stumble upon this question and answer:
I had the same problem when installing and updating Joomla on a Windows host, problems were related to directory permissions on various directories like "tmp", "modules" etc not being set. When I used the FTP client's chmod functionality the server responded with 504 Command not implemented for that parameter (showing in green instead of red in my FTP protocol so I ) so permissions were never changed. I had to alter the security settings using the hoster's web interface, after that installing packages worked as expected.
only for this folder:
chmod 777 /opt/lampp/htdocs
OR
project folder -
chmod 777 /opt/lampp/htdocs/project_name
in /var/www/you_site/httpdocs/configuration.php change value:
$ftp_enable = '0'; set 0 from 1
Under config.php I have:
$config['log_threshold'] = 4;
$config['log_path'] = '/home/myaccount/logFilesFolder';
In index.php I have:
error_reporting(E_ALL);
The only way I can seem to get anything to log is if I chmod that directory to rwx (777), which doesn't seem right to me. That and it doesn't see to be logging all the errors.
In my local/dev environment it seems to be working but on my production server nothing is being logged. I can't seem to figure out why.
The log filename in the configuration settings needs a trailing "/" above making sure the webserver process has writeable access to the directory.
Change the logs owner and group to what owner/group your live web server is running, give it write perms and it should work. I take it that in your local/dev server your CI folder is owned by you that is why you need to chmod it to 777 to make it work.
The directory where you want the log files to be saved needs to be writable.
I have tried a lot of solutions and finally what worked for me was this:
Open system/libraries/Log.php
and change the following lines;
set the value of: $this->log_path to a writable directory, preferably home directory so that there are no permission issues. If you want to change the filename also, search for the variable $filepath and change the name.
Example:
$this->log_path = '/log';
touch /log/
restart the webserver.
The logs will start coming.
I have tried a lot of other options, none worked, this is not neat approach but at least I can see my logs now.
I had the same problem with my Codeigniter 4 project. The log was created successfully in my local window machine but was not creating on the remote Linux machine. I was using a custom path to generate log files under the 'app' folder. So what I did is to change the settings in my config/Logger.php file back to
'path' => WRITEPATH.'logs/',
and it created the log files under writeable/logs folder.