Is there a way to store tmuxconfig in project repo instead of ~/.tmuxinator directory?
If it possible then how I can start session with this config?
Related
Visual Studio now generates Dockerfile for dotnet projects, and we are using it (with slight tweaks) for our continuous integration.
However that Dockerfile does not have any provision for configuring nuget. It even only copies the .csproj file from context before running dotnet restore to avoid re-running that step during development.
But our project requires some modules from internal, password-protected repository, so I need to provide package sources and credentials to the dotnet restore command inside.
What is the best current practice for injecting a (environment-specific) nuget configuration?
This is documented here: https://github.com/dotnet/dotnet-docker/blob/main/documentation/scenarios/nuget-credentials.md.
To summarize, there are a variety of ways in which this can be done:
Use a multi-stage build to protect nuget.config that contains hard-coded credentials. Only recommended if you ensure that credentials are kept out of source code control and the nuget.config file is ephemeral.
Passing secrets by file with BuildKit. This is similar to the previous option but makes use of Dockerfile secrets to provide access to the nuget.config file.
Use environment variables in nuget.config. In this scenario, the nuget.config file would reference environment variables for its credential values. The environment variables would then be set by the build machine when executing a docker build.
Use the Azure Artifact Credential Provider. This is only possible if you make use of Azure Artifacts for your package feed.
No matter which option you choose, be sure that credentials are never stored within an image layer that is published.
My .NET Core application is using Config Server which is referencing the configuration values which are stored in .yml at Git repo.
Do we need to restart the application once the configuration value updated in Git to get the value to be reflected?
I wanted to understand is this the expected scenario or am I missing something else?
Yes, this is how it works by default. You can configure whether the cofiguration will be fetched from git, or from the cloned config in the config-server's memory with the 'refreshRate' configuration.
See documentation for more informationt:
https://docs.pivotal.io/spring-cloud-services/2-0/common/config-server/configuring-with-git.html
How I can set for example Path to urlGenerator.php if I using deployment connection to my project, and this file is generated on virtual machine. I don't want to synchronize that files to my local computer...
The connection to deployment is through sftp.
Symfony plugin configuration:
Deployment configuration:
I have added a remote action button and also multiple routing files in a new menu entry. you can now add remote files. just update to 0.11.111
https://github.com/Haehnchen/idea-php-symfony2-plugin/issues/685
I have a question about flyway migration folder . Does sql's have to reside in project folder Application/foo/bar/main/resources/db/migration. Could it reside outside of the application cource folder?
We are using Maven.
By default Flyway will look for migrations on the classpath under db/migration, which on a Maven project means src/main/resources/db/migration.
You can however also use a location starting with the filesystem: prefix that can be anywhere on your disk.
See the ”Location and discovery“ section of the SQL-based migrations documentation page.
For command-line use, see the locations option on the migrate command reference page.
I'm using VS 2010 to build the deployment package for a web application. I manually deploy it to the IIS 6.0 server using the deployment ccommand script it generates. All the stuff gets copied under the Inetpub default website properly. The only issue I have is that the folder permissions keep getting reset once I deploy.
Say my website is under the folder "Mywebsite". I grant certain user XYS full control to this folder. All is well. The next time I deploy, user XYZ no longer has full control and the permissions gets reset.
If you want to skip ACL operations then you need to set a property in your build. You can do this in two ways
Edit your project file
Create a .wpp.targets file
I would recommend #2. For this case create a new file in the same directory as your project file with the name {ProjectName}.wpp.targets where {ProjectName} is the name of your project. Then inside of this file you should place the following contents.
<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003"
ToolsVersion="4.0">
<PropertyGroup>
<IncludeSetAclProviderOnDestination>False</IncludeSetAclProviderOnDestination>
</PropertyGroup>
</Project>
Here you are setting the property IncludeSetAclProviderOnDestination which will signal the Web Publishing Pipeline to not include ACL providers in the manifest that is created for the package/publish.
If you want to take approach #1 just throw in the entire under the elment.