I just signed up for a Meteor developer account and deployed my first app. I have searched and seen the blog post on the develop account but I have not found any information on how to login and view a list of all apps deployed to your account.
So for example after
meteor login
you could type
meteor list
and it would list all the apps deployed to this account
but I have not found any such command and I am wondering if it exists?
Update
The command has since been added use:
meteor list-sites
Make sure you're logged in first. Use meteor login to login, if you're not already.
At the moment this feature is not yet available. It should be available soon, according to the discussions on meteor-talk, with an API call and a meteor command like 'list'.
The apps listed on your Meteor Developer account are not the same as your deployed apps. The apps listed there are the ones that have access to your meteor developer account via OAuth.
More Info:
https://groups.google.com/forum/#!topic/meteor-talk/QPlmTfYf5gM
https://groups.google.com/forum/#!topic/meteor-talk/xFmGbAsmIck
You can view your Developer Account Apps from the Meteor Account settings page
Once you log in, you will see all of your apps listed under "Your Developer Account Apps"
The command has been added. Use
meteor list-sites
To show all apps deployed to your account.
Related
As per the Firebase documentation, the contents of google-services.json are considered public. These can be easily retrieved by decompiling the apk.
If so, is there a way to prevent apps from registering with my Firebase project?
I understand that the registration works on the basis of package name. While it's not possible to publish an app with a duplicate package name, for development it is very much possible.
I created a dummy app, and my dummy app successfully registered with my production project. So, looking for a way to prevent that from happening.
You should be connecting your app to Firebase Emulator for local development.
You can go to Firebase console -> Authentication tab -> Sign-in Method tab, and remove localhost from Authorized domain, that way your app will never connect to production DB.
Background: I'm creating a website that will deploy websites using firebase. The one-liner is that they fill out information and the web app deploys a website with that information. It's a Node app with react frontend and express backend. I plan to deploy this on firebase too but I'm not attached to this idea. I wrote an npm script that will create a project and deploy a site on the firebase project but it only works because I'm already logged in on my machine. Currently, it logs in through the web interface using OAuth2.0 and my google account. I cant find anything online on this. All my search results bring me to firebase's authentication feature.
Question: Are there alternative programmatic ways to login to firebase? If not, do you have any guidance on how I can accomplish this otherwise?
I think you're confused about what it means to be "logged in to firebase".
If you asking how to automate deployment with the Firebase CLI, without needing to sign in using a browser to authenticate your identity, then you should read the documentation about using the CLI with CI systems. You can sign in once manaully and get a token, then use that token on the command line to perform you deployment without having to manually sign in again.
For logging purposes I´d like to print to console or even display the current deploy ID (or message) of my firebase web app that is being accessed by the browser.
Firebase Hosting recently released a new REST API. You can use sites.releases.list to see what version is currently deployed.
Old answer:
Firebase deploy IDs don't appear to be available anywhere via programmatic access. The CLI doesn't support listing current or previous deploys.
My recommendation would be to go in the other direction. Have your source code in a vcs like git. When you build and deploy a new version set the vcs hash or version in the deployed code and as the message for firebase deploy. You can then log the log the source version in your code and you can manually associate that back to a release in the Firebase UI.
I found this post Is there a way to use Firebase Legacy console from new account where it states that
It is no longer possible to sign up in the legacy console.
But if I have been added as a collaborator on a project in the legacy console, is there any way I can access that project?
I don't think there is. The owner of the legacy project can add you via email, but if you don't have a preexisting legacy console account the auth workflow won't work. You'll just end up cycling through google logins and back to the new console.
https://groups.google.com/forum/#!topic/firebase-talk/6stRgevwkBk
I had been developing the app a couple weeks ago and went back to it to make a few changes and I see the changes on my local version but I can't get them to app.meteor.com
I found this blog post: http://docs.meteor.com/#deploying. I have created my account, logged in from the command line and claimed the app. I am listed when I type "meteor authorized appname" from the terminal.
However, when I go to https://www.meteor.com/account-settings it says: "You haven't authorized any apps to access your developer account."
When I type "meteor deploy appname" everything looks fine on the command line but the site is not reflecting any changes.
Thanks
Have a look at the "Claiming legacy sites" section of this blog post:
If you have existing apps deployed with meteor deploy, you'll be prompted to claim them with the new meteor claim command when you try to deploy them with the new Meteor release.
Once you are logged in on the command line, use meteor claim to associate these legacy apps with your new developer account. If the old app was password-protected, you'll be prompted for the site password one last time before you'll be able to claim the app. Once you've claimed it, you'll be able to deploy to it, run meteor mongo and meteor logs, and manage authorized users with meteor authorized, as long as you are logged in on the command line.
Make sure you are running the latest version of meteor by running meteor update, and the next deploy attempt should prompt you to claim the old app.