I've tried spacemacs and really like their helm configuration.
I'd like to copy helm configuration but can't find how.
Where is their helm configuration located?
Related
I have an issues with few latest version of Intellij with kubernetes plugin.
I am using helm, so typically my chart looks like below:
helm
templates
deployment.yaml
...
Chart.yaml
values.yaml
I installed kubernetes plugin, go template as required, added File pattern *.yaml to fily type - helm.
When I am opening deployment.yaml I have there references like
{{.Values.strategy.type}}
or
{{.Values.strategy.rollingUpdate.maxSurge}}
However, I see that those references are marked as 'Unknown identifier' and I can not go to that actual value by clicking ctrl+click as it was few versions ago. So it does not recognize the values by references.
I used to see in deployment that Intellij shows me value as a hint instead of pure reference and it was pretty nice to see.
Could someone help me with this? What I am missing.
Go Template plugin: 213.5744.190
Kubernetes plugin: 213.6461.19
IntelliJ: 2021.3.1
I want to use a babel plugin (babel-plugin-module-resolver) in a project created using create-react-app.
I know how to change babel configuration using npm run eject, but I would like to avoid it.
I was going to use react-app-rewired but I heard that there is the possibility to configure babel without ejecting and without additional libraries.
(if possible), how can I do it?
I am using TYPO3 SURF to deploy my application. I added "LocalConfiguration.php" to my .gitignore. So everytime I push and deploy, the config file is missing from the live server and I have to go through the install tool again.
What is the best way to fix this ?
Include your LocalConfiguration.php in your versioning and deployment. Use a configuration switch to have different configuration values on different systems (e.g. development vs production). Here are some ways how to do it: Good practices in TYPO3 projects #3 Use a configuration switch mechanism
You might want to copy the LocalConfiguration.php file into your shared folder and create a symlink from your release folder to that file.
https://docs.typo3.org/other/typo3/surf/2.0/en-us/Examples/TYPO3/Index.html
Problem: I can't seem to successfully install the mercurial plugin to jenkins using the Dockerfile and plugins.txt combination.
What I've done so far:
I have a Dockerfile that's loading Jenkins. It has the following lines:
FROM jenkins:1.642.1
COPY plugins.txt /usr/share/jenkins/plugins.txt
RUN /usr/local/bin/plugins.sh /usr/share/jenkins/plugins.txt
My plugins.txt has this line:
mercurial:1.54
When I build the image and run the container, everything seems to work, there are no errors or complaints. But the Mercurial plugin isn't marked as installed when I go to Manage Plugins, and if I try to make a build, Mercurial isn't an option under Source Code Management.
I've tried going to:
<jenkins ip address>:8080/reload
As well as the "Reload Configuration from Disk" option in Manage Jenkins. Mercurial still isn't visibly installed after either of these.
I've also done this on the command line:
docker exec -i -t container bash
ls /var/jenkins_home/plugins/
And at this point I'm totally confused, because there's mercurial, mercurial.jpi and mercurial.jpi.pinned right there in the list. Does anyone have any ideas on this? I would like to have Mercurial installed on Jenkins as soon as it's loaded from the Dockerfile without having to do it manually...
Also, I tried doing this with git-changelog as well to see if another plugin would work better, and had the same result.
As you can see on the Mercurial Plugin wiki page, the plugin currently has four mandatory dependencies, and one optional:
credentials
matrix-project
multiple-scms (optional)
ssh-credentials
scm-api
The plugin installation mechanism that you're using with the Jenkins Docker image does not automatically install dependent plugins for you, as mentioned in the documentation for the jenkins image:
All plugins need to be listed as there is no transitive dependency resolution.
Therefore you need to additionally list those plugins, and any of their transitive dependencies, in your plugins.txt file.
At the moment, the simplest way to get the full list would be to start your container (potentially without plugins.txt), and then install the Mercurial plugin via the Plugin Manager, which will be installed along with all of its dependencies. Then you can see a list of which plugins are required via $JENKINS_HOME/plugins.
I'm trying to reinstall a package on CentOS: yum reinstall packagename however I can still see the changes that I made in the config files from this package.
Is there a way to force the re-load of the package and its config files?
Check to see whether the reinstall of the package also created the config files with filenames ending with ".rpmnew". If such files exist, they will be the unmodified versions of the files.
If that is not the case, can you perform the package reinstallation in the two steps instead of one? That is, first do yum remove packagename and then do yum install packagename.
If neither of the above will do the trick, the simplest way to solve the problem is to rename or remove the config files and then do the yum reinstall.