I don't want to edit in a specific project in cloudshell, but it automatically directs me to one. How can I exit out of it and just not edit in a specific project?
You can just unset the project with the Cloud SDK command:
gcloud config unset project
then you can validate if there is no project associated with it:
gcloud config get-value project
Related
I am following the instructions here to add Firebase to my Flutter project. I want to use Firebase Analytics so I added it in pubspec.yaml
The package page for Firebase Analytics does not mention anything about adding Analytics as a dependency in android/app/build.gradle
No such thing is mentioned in Firebase for Flutter page either which I linked earlier. Now when registering the app in Firebase Console, it asks to add implementation of Firebase Analytics in app level build.gradle
So do I need to add it or not as it looks like only Firebase Console wants me to add it but couldn't find any mention of it on any official Flutter page.
I had the same question as well. Is seems obvious, that you should add the dependency on com.google.firebase:firebase-analytics to your project.
But… You actually don't need it.
It's easy to test! Just set up the Firebase Analytics like it is described in the docs:
google-services.json
apply plugin: 'com.google.gms.google-services' (and related things)
Configure multidex
firebase_analytics: ^X.Y.Z in pubspec.yaml
Don't add any Firebase dependencies to you app/build.gradle!
Now, enable the DebugView in Firebase Analytics: adb shell setprop debug.firebase.analytics.app your.package.
Run the app and send some events. Open the DebugView in Firebase Analytics console and you'll see them all!
Probably, all the magic happens in the Google Services Gradle Plugin:
The google-services plugin has two main functions:
Add dependencies for basic libraries required for the services you have enabled. …
You can see the result of this step by running ./gradlew :app:dependencies.
So, the plugin seems to add them for you!
You could also check what dependencies will be autoconfigured, by running ./gradlew :projects from your android dir. Mine is:
Root project 'android'
+--- Project ':app'
+--- Project ':firebase_analytics'
\--- Project ':firebase_core'
Now, after I add firebase_auth to my pubspec.yml and run flutter pub get, this command indeed lists one extra project:
Root project 'android'
+--- Project ':app'
+--- Project ':firebase_analytics'
+--- Project ':firebase_auth'
\--- Project ':firebase_core'
Adding the Google Analytics for Firebase SDK in your app and enabling analytics settings in the Firebase console is optional. It depends on what Firebase product you will be using. If Firebase suggests you add the Analytics SDK, it means that the Firebase product has integration with Analytics. See this documentation for your reference.
I am new to Artifactory and just going through the guides and trying out some sample code.
I am trying to publish a maven artifact to my artifactory server. I have followed the following steps to do it:
Through the "Set me up" tool, get the settings.xml file for maven.
Download and place the settings.xml file to the ~/.m2 folder
Clone the maven example repo from the artifactory examples available on git.
Update the pom.xml file and add the distributionManagement tag provided in the "Set me up" window.
Publish the code using mvn deploy
The binaries are published to the artifactory server and are available in the Artifact Repository Browser window. But I do not see any corresponding builds in the Build Browser. I also do not get any builds if I try to fetch them using the REST API
What am I missing? I followed the above steps because I saw it on the Introduction to Artifactory webinar video. Is there any setting that I need to change to see the builds in the Build Browser window?
I am using Artifactory Version 5.10.3 (OSS)
I think there is a misunderstanding, the maven example plugin is used for publishing artifacts to Artifactory, however, it doesn't publish Build Info.
In order for you to publish build info to Artifactory, you will either need to use CI server with Artifactory plugin (for example, Jenkins, Bamboo, Teamcity) or use the Maven Artifactory plugin:
https://www.jfrog.com/confluence/display/RTF/Maven+Artifactory+Plugin
That have the build information publish step inside.
Required to get all required Adobe plugin from Adobe public repository through Artifactory
For this Under Set Me Up -> Adobe Public in Artifactory home page.
Now click it provide the password it gives resolution.
curl -u: -O "http://10.32.23.108:8081/artifactory/Adobe-Public/"
However when I try to execute the resolution in a Unix box it fails to download any plugin or jar files though it connects do not give any error but only 0% download.
Is there any other setting needed for this Adobe Public.
To proxy the Adobe Maven repository you need to perform the following steps:
Create a new remote repository in Artifactory - Admin -> Remote -> New
Choose maven as the repository type
Set a repository key, for example Adobe
Set the following as the repository URL - https://repo.adobe.com/nexus/content/groups/public
Click the "Test" button to make sure Artifactory can connect to the Adobe repository
Click Save & Finish
Make sure you can see the new repository in the Artifact Repository Browser. You can expand the tree to see the content of the remote repository.
Add the new repository to the libs-release virtual repository. This will allow to resolve Adobe artifacts using the libs-release repository.
If you have not done it already, generate a Maven settings.xml file using Set Me Up. Configure Maven with the generate settings.xml file. For more info see Maven Repositories
The above steps should allow you to resolve arifacts from the Adobe repository.
You should not use the Maven settings.xml from the adobe web site. This one is intended to be used when you resolve artifacts directly from their repository and not via Artifactory. There is no need to add the adobe-public profile.
This does not affect you distributionManagement settings in the pom file. Those are required for deploying your build artifacts.
Is there a settings or config file I can create that will permanently set a project to a specific version of meteor? It can be challenging to remember for each project.
I believe that information is in the release file located at /yourproject/.meteor/release
I'm using Microsoft Web Deploy to publish and update my site. (script is generated with Visual Studio). This tool removes auto-generated files and folders on update, as they are not included into install package. How to make it keep these files?
The Web Deploy command line tool has two switches that may be useful: -skip and -enableRule:DoNotDeleteRule. For information on -skip, see Web Deploy Operation Settings, and for DoNotDeleteRule, see Web Deploy Rules.
In Visual Studio, you may be able to tweak the deploy.cmd file to use these to achieve what you want. For more information, see How to: Install a Deployment Package Using the deploy.cmd File.
Having to edit the deploy.cmd files each time you generate them is a pain. I am using VS2017 and found I can set an environment variable on the server and deploy.cmd will use it. The deploy readme file says it:
Alternatively, you can specify additional flags by setting the
"_MsDeployAdditionalFlags" environment variable. These settings are
used by this batch file.
So on the server I created the environment variable:
_MsDeployAdditionalFlags=-enableRule:DoNotDeleteRule
And that did it. It now adds the rule each deploy on the server.