I would like to be able to update the latest tag when building/publishing the image locally, but not when publishing it publicly.
I added this setting:
Docker / publishLocal / dockerUpdateLatest := true
But when running sbt docker:publishLocal the latest image is still not present.
How to achieve this?
Related
Suddenly some of my css variable names on SSR build on server are being changed to something else and not working.
For example i have
.color-black-75 {
color: var(--black-75-color);
}
in my styles.css but when i build project on server in browser it turns to:
i checked out to older commits from 1 month and 2 month ago but this is still happening.
everything works fine when i build project on local ( with docker ) but on server this is preventing some css classes from working.
First find and replace corrupted classes in *.css with correct classes in dist folder so the project will work fine on server until we find the real issue.
Then if project is being built fine on your local then the issue should be about Package.json package versions or your Dockerfile installed application versions so you can copy your local package-lock.json file to server via scp and then push your local docker image and then pull on server so these issues would be fixed.
The real issue in this case was a package version update which you could find with comparing local package-lock.json with server package-lock.json and then removing ^version and ~versions from package.json and use exact version so over time your packages won't be updated and won't cause any issue.
I've been getting to drupal and recently found out about composer. I use the following command to create a dev drupal instance:
composer create-project drupal-composer/drupal-project:~8.x-dev <folder-name> --stability dev --no-interaction
I was wondering what the package name is for the stable release of drupal.
Thank you.
You shouldn't need to change anything about your core build, both development and production will be running the current build of drupal/core. But modules like Devel or Stage File Proxy can be added to the require-dev section in your composer.json and installed while doing development and kept out of the build on production.
Hopefully this link will help: https://www.drupal.org/docs/8/update/update-core-via-composer#update-drupal-8-core
The very last part about Production environments says to run composer install --no-dev to remove any dev dependencies from the build.
Is there a way to bypass the auto update feature of Meteor?
I'm stuck with
Downloading meteor-tool#1.3.0_3... \
When I try to run existing project, or create a new one or simply run "meteor list",..It starts updating, downloads meteor-tool#1.3.0_3... which completes 100% and then countdown vanishes & it remains like that with the spindle rotating.
I tried waiting like mentioned at this link
However, nothing happens even after an hour.
I've same error. I resolve by following steps, please try
Download meteor installation from https://github.com/meteor/meteor/wiki/Meteor-on-Windows:-Alternate-installation
Extract zip & Copy all tool from .meteor/packages/meteor-tool directory
Go To %AppData%/../Local/.meteor/packages/meteor-tool or C:\Users\<your_user_name>\AppData\Local\.meteor\packages\meteor-tool
Paste inside folder (Note: If you can't copy or gives error of long path, use RoboCopy)
Now, you can create new Meteor app.
Go to project > .meteor > release
Change the meteor version to the current one that is installed on your system.
Consider my scenario:
1) System have the Meteor version 1.4.3.1 installed
2) Downloaded the todos(meteor project), developed on version 1.4.2.1
3) On running it gives similar problem
4) Changed the release version to 1.4.3.1
5) Run with command 'meteor'
Considering latest Meteor 1.6 you can use below commands for your best needs
meteor create . --release 1.5 --full to create a scaffolded app.
meteor create . --release 1.5 --bare to create an empty app.
NOTE: Instead of --release 1.5 you could use your version which actually exists.
I'm trying to create a SBT build that can publish a Docker container either to DockerHub or to our internal Docker repository. I'm using sbt-native-packager 1.0.3 to build the Docker image.
Here's an excerpt from my build.sbt:
dockerRepository in dockerInternal := Some("thomaso"),
packageName in dockerInternal := "externalname",
sbt docker:publish now successfully publishes to thomaso/externalname on DockerHub.
To add the option to publish to our internal Docker repo I added a configuration called dockerInternal:
val dockerInternal = config("dockerInternal") extend Docker
I then added these two settings to override the defaults:
dockerRepository in Docker := Some("docker.nrk.no/project"),
packageName in Docker := "internalname",
My expectation was that sbt dockerInternal:publish should publish a Docker image to docker.nrk.no/project/internalname. Instead, I get this error message:
delivering ivy file to /home/n06944/repos/nrk.recommendations/api/target/scala-2.10/ivy-0.1- SNAPSHOT.xml
java.lang.RuntimeException: Repository for publishing is not specified.
It seems to me SBT tried to publish to Ivy, not to Docker - when I hardcode the values to the internal repo the publishing works fine and there is no mention of Ivy in the logs. The Docker configuration modifies the publish task, and I hoped that by letting dockerInternal extend Docker I would inherit the Docker-specific publish behavior. Is that an incorrect assumption? Am I missing some incantations, or is there another approach that would be better?
You forgot to import all the necessary task to your new config. sbt-native-packager recommends generating submodules for different packaging configurations.
If you want to fiddle around with configuration scopes (which gets pretty messy very fast) here is another SO answer I gave.
cheers,
Muki
I am running JBoss Fuse 6.2.0.
I built a small camel application that just writes to the log every 5 seconds.
I built it and installed the SNAPSHOT bundle jar in my local Maven repository.
In the Karaf console I did the following:
fabric:profile-create --parent feature-camel logdemo
fabric:profile-edit --bundle mvn:com.company.project/logdemo logdemo
fabric:container-create-child --profile logdemo root child1
The camel application now worked as intended.
I then made a small change to the application, rebuilt it and installed the new SNAPSHOT bundle jar in my local Maven repo.
In the Karaf console I then did the following to get Karaf to load the new jar:
fabric:profile-refresh logdemo
But the loaded application is still the old version.
How do I get Karaf to look for the updated jar in my local maven repo? It seems like it has some internal cache it looks in instead.
Note: We're not using Maven to build the application, so all answers about using Maven plugins like the fabric8 plugin will be rejected.
You should use the fabric:watch * command for that. This will update all containers that run a snapshot version of an artifact that is updated in the local maven repo. If you want only a specific container to watch for updates use dev:watch * on the shell of that container.
See http://fabric8.io/gitbook/developer.html